Your MCP server may already have a report page. You just haven't seen it.
We find public MCP servers and check them every 12 hours — nobody has to sign in, and nobody has to ask. The result is a public page for each one. If you run a server, that page exists whether or not you've looked. Claiming makes it yours.
3782 servers in the directory · as of 2026-10-30 00:12 UTC
This is what a report page looks like
An excerpt from our own MCP server's latest report. Every check shown lists its state; open the full page to see every check we track, including why each one that didn't run didn't.
Our own badge (Indie plan). When the latest run is signed, it shows the most serious state among the checks that ran, and how long ago. If the latest run isn't signed, it falls back to a static "claimed" badge, same as Free.
Not observed: the endpoint did not ask for credentials, so there was no auth challenge or metadata to check.
+ 10 more checks on the full page
Open the page →What claiming changes
| Not claimed | Claimed · Free | Claimed · Indie | |
|---|---|---|---|
| How often we check | every 12 hours | every 8 hours | 15 minutes |
| Targets | — | 1 | 10 (subscription quantity adjustable — 2× = 20, 3× = 30) |
| Price | — | $0 | $49.99 / year, or $5.99 / month |
Paying changes how often we check and what the badge shows. It never changes what the checks say. See pricing →
Claiming takes three steps
Paste your endpoint URL
If a record already exists, you go straight to verifying it; if none does, you name it first. You'll need to sign in with your email — there is no password.
Prove you control the domain
Add a DNS TXT record, or serve a .well-known file, containing the token we give you.
Example DNS TXT recordWe verify the address
Verification reads only that record or file. We never ask for credentials. Once it passes, the page is yours and the next check is scheduled right away.
Where agents find you
Agents connected to our MCP endpoint can look your server up before they call it, through the same tools shown on our page for agents. The directory is searchable by server name, address, tool name, or description, and your README badge links back to your report page.
How agents connect →What can't be bought here
There isn't one. Every check lands in one of four states, and a check that wasn't run is never shown as one that passed.
Paying changes how often we check and what the badge shows; it never changes what the checks say.
The directory is a list of matches, not a leaderboard.
Proving control is a DNS record or a well-known file on your domain — never a credential you'd hand us.
Questions maintainers ask
Is my server already listed?
Search the directory by its name, address, or a tool name or description. If it isn't there yet, claiming it by its address creates the record.
My server needs a key. What will the page show?
We never send credentials. When your server answers with a valid authentication challenge, the checks behind it are shown as not checked, with the reason that credentials are required — never as a failure.
Will your probe run my tools?
No business tool is ever called. It reads your tool list, then calls one reserved tool name chosen so it should not exist, to see how your server refuses an unknown call — unless your list already has that name, can't be read in full, or sits behind a credential gate, in which case that call is skipped.
How do I stop the checks?
See “About our probing” — it lists the User-Agent we send, the request budget, and how to opt out. About our probing →
What does the Free badge show?
A static "claimed" badge. It never shows a state. The live badge — a state plus a timestamp — comes with Indie.