Why claim
Listings enter the directory without their owners — curated, or ingested from the official MCP registry. Claiming attaches your account to the listing as its verified owner: a badge on the public page, plus the owner controls — editing the description and homepage, and pushing contract snapshots for servers the anonymous probe cannot record.
Claiming is free. Verification is a proof of control, not an editorial judgement — the directory never reviews listings, it measures them.
How
Start the claim
Sign in, open your server's listing page, and press Claim this
listing. You get a verification value shaped mcpi-verify=<token>.
Publish the proof
Either place works, at your choice:
- **DNS** — a TXT record at `_mcpi.<host>` of the endpoint (the bare
host also works, for DNS interfaces that fight underscores).
- **HTTP** — the same value as a line in the body of
`https://<host>/.well-known/mcpi-verify`, served by the endpoint's own
origin. Redirects are not followed.
Verify
Press verify on the listing page. The check reads DNS over HTTPS and the well-known path directly; the moment the proof is visible, the claim is verified.
The proof is host-scoped on purpose: it demonstrates control of the machine (or DNS) answering at the endpoint's host — the same scope the listing makes claims about. One listing has at most one verified owner.
After claiming
The listing page shows the verified owner badge, and your dashboard lists the server under your account. You can keep the TXT record or delete it — verification is checked at claim time, not continuously.