Menu

For MCP maintainers

Paste your MCP server's address. See what an agent would see.

on-demand checks are recorded as tracking requests — inclusion is not guaranteed

Try an example:

Free MCP server health check · 15 protocol checks · results in seconds · no account · result page expires in 24 hours

Claim your server to keep checks running every 8 hours, published as signed evidence →

What we have observed

7,557Servers in the directoryPublic servers with at least one stored tool list.Browse the directory →
580,491Runs completedEvery probe run that finished since we began. Unsigned on-demand checks are not counted.How often we check →
343,127Signed results issuedOne per run whose result carries a signed attestation, since we began. Counts results, not servers.What "observed, unsigned" means →
1,379Servers whose tool set changed, last 30 daysTwo consecutive observations of the same server produced different tool set fingerprints. Each server is counted once.Tool set changes →
Protocol revisionRecorded in each server's latest result, among the 7,060 servers whose latest result is signed.
2025-11-25
3,463
2026-07-28
2,061
2025-06-18
1,199
2025-03-26
185
2024-11-05
150
2025-11-05
2
What two numbers mean →

As of 2026-11-17 00:12 UTC · computed once a day · MCP servers in numbers →

Live

Checking right now

Each row is one check our probe ran, without credentials, shown as observed and without a verdict. Signed results, where there are any, are on each server's report.

11:51:01 UTC · Checks run in rounds every 5 minutes.

12,002
Checks today
since 00:00 UTC
1,008
In the last hour
about one every 4 s

Colour marks the protocol revision and nothing else. Time-taken bars use a log scale from 30 ms to 5 s. Each row opens that server's report.

See all observed servers →
For agents

Your agent can ask us before it connects to an MCP server.

MCP Checkup is listed in Claude's connector directory: in Claude, open Customize → Connectors → Browse and search for MCP Checkup.

See the listing →

Endpoint · Streamable HTTP · no key
https://mcpcheckup.com/mcp

Quickest way: Many agents can set this up themselves. Tell yours:

“Read https://mcpcheckup.com/agents and add the MCP Checkup server.”

Then ask your agent something like:

“Before we add acme/weather-mcp, check what MCP Checkup has observed about it.”

Six tools, limits and an example answer →
Claude Code
claude mcp add --transport http mcpcheckup https://mcpcheckup.com/mcp

Add --scope user to use it in every project.

Other clients: Cursor, VS Code, Muse Code, Claude, ChatGPT · dots, Grok, Hermes Agent, OpenClaw, Muse

Checked against each product's documentation on 2026-10-01.

Four states, never a score

There is no total, no grade, no health percentage. Every check lands in exactly one of four states, and a check that wasn't run is never confused with one that passed.

Verifiedthe assertion was checked and held.
Failedthe assertion was checked and did not hold.
Observed riska signal was observed; it isn't a pass/fail verdict.
Not checkednot checked this run — always with a stated reason.

Troubleshooting

Guides for the errors a client or a check report shows, each with the commands to reproduce it.

Evidence you can check yourself

Each signed run is packaged as an attestation with a digest of the exact check-suite version — you don't have to take our word for a Verified or a Failed. The signature format is a public standard, and the public keys that verify the signatures are published at /keys.

Built for people who maintain, not a team that scores you

It exists to give independent MCP maintainers — the people running one or a handful of servers, usually open source, usually without a dedicated budget — an honest, continuously-updated read on whether their server still does what it claims.

Ready to check your server?

Sign in with your email — there's no password, and no separate sign-up step.

Sign in