Your MCP server may already have a report page. You just haven't seen it.

Once it's yours, the page starts working for you

• Checks every 8 hours instead of every 12.
• A README badge. On Free it's a static "tracked" badge; it never shows a status.
• Alert emails for a claimed server: when we can't reach it or a protocol check fails, when it recovers, and a daily digest when there's something to report. One-click unsubscribe in every email.
• A report page that's yours to point people at.

Indie ($49.99 a year, or $5.99 a month) turns the badge live: it shows which of the four states the latest check landed in, with a timestamp, and checks run every 15 minutes. That's the difference between finding out from your users and finding out first.

Three places your server shows up

• The directory, searchable by tool name and description. Sort order is never affected by what anyone pays.
• Agents can ask us directly. Our MCP endpoint exposes tools such as check_mcps and get_mcp_report, so an agent can look up your server before calling it.
• The badge in your README links back to your report page.

We don't have traffic numbers worth quoting yet, so we won't quote any.

What can't be bought here

• A score. 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.
• A better result. Paying changes how often we check and what the badge shows; it never changes what the checks say.
• A higher spot. The directory is a list of matches, not a leaderboard.
• Your credentials, ever. Proving control is a DNS record or a well-known file on your domain.

Claim a server by its address

Paste the 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.