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
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.
12:00:44 UTC · Checks run in rounds every 5 minutes.
- 2026-07-28 4
- 2025-11-25 9
- 2025-06-18 1
- 2025-03-26 1
- not negotiated 15
- other revision 0
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 →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.
Quickest way: Many agents can set this up themselves. Tell yours:
“Read https://mcpcheckup.com/agents and add the MCP Checkup server.”
“Before we add acme/weather-mcp, check what MCP Checkup has observed about it.”
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.
Troubleshooting
Guides for the errors a client or a check report shows, each with the commands to reproduce it.
- MCP server returns 406 Not AcceptableWhat the Accept header must say, and how to fix it in the client, the server and the proxy.
- MCP server won't connectWork through the error you get, from 401 and redirects to timeouts and "Connection closed".
- MCP error codes: protocol errors vs tool errorsWhich error a server should send, and what reaches the model in each case.
- Unknown tool: a JSON-RPC error, not isErrorWhat the error_taxonomy check sends and expects, and how to test your server with curl.
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.