lookupd

Publish a server

What lookupd measures (health, tools, latency) is never editable. What a publisher declares is labelled as declared.

1. Automatic

Status: available now, free.

lookupd mirrors the Official MCP Registry hourly, probes remote endpoints hourly, and enriches changed entries every 6 hours. Publish your server to the Official MCP Registry with mcp-publisher publish and it appears on lookupd within about an hour. Later crawlers will cover GitHub skills, npm and PyPI, and /.well-known/agent-card.json.

Show your live status in your README: every server page has a badge (https://lookupd.com/badge/<registry name>.svg) with the markdown to paste. It shows up, latency and verified, updates hourly, and links to your page.

2. Submit

Status: coming, free.

npx lookupd submit <repo or url> and POST /v1/submissions will ask the crawler to look sooner. It is a hint only: no control, no ownership, rate-limited.

3. Claim, then publish

Status: claims available now, free; the publish manifest is coming (phase 2).

Claiming a listing is free: prove you control it and it is yours, with no expiry and nothing to pay. Prove you control the listing and your page shows "Verified publisher", with a README badge, analytics and uptime alerts. Nothing about ranking is for sale and placement is not offered. Claim: https://lookupd.com/register. What a claim gives you: https://lookupd.com/publishers.

Coming next, like npm publish: a registered, verified publisher, their agent, or their CI runs npx lookupd publish with a lookupd.json manifest in the repo. The manifest holds the description, capability tags, install notes per runtime, auth, pricing and deprecation or redirect.