
MCP Checkup MCP server
Which servers in the official MCP registry are MCP Checkup's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry namecom.mcpcheckup/mcpverified in the MCP registry
The registry name sits under mcpcheckup.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools6
- Server calls itselfmcpcheckup
- Server version0.2.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 129 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 3 of the 7 days it takes to judge reliability.
Once connected
- For "Test a remote MCP server against 15 protocol checks", the likely first call is request_check.
- Parameters are untyped or undescribed in 2 of 6 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer923 ms
- Space in an agent's context≈ 3,528 tokensthe definitions of all its tools (6), which an agent carries on every turn
- Tool definitionsA · 94 of 100
- Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 2 of 6
What an agent can do with it
- can do · Test a remote MCP server against 15 protocol checks
- not sure · See what an AI agent would see from an endpoint
- not sure · Monitor a claimed server with checks every 8 hours
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
check_mcpsWhat has been observed about an MCP server — useful when choosing, adding, or debugging one. Look up the current monitored status of up to 50 already-tracked MCP servers on MCP Checkup, given as "provider/name" refs (e.g…
get_mcp_reportThe detailed view of one MCP server: every check with its state, plus the observed tool list. Get the full observed report for one already-tracked MCP server on MCP Checkup, by provider/name — with its full check breakdown and toolset. An…
get_mcp_historyWhether an MCP server's toolset changed recently. Get recent history for one already-tracked MCP server on MCP Checkup, by "provider/name" ref (e.g. "acme/weather-mcp"). Events, newest first, up to `limit` results (default 20, max 50)…
get_attestationThe signed evidence behind a report, for callers that want to inspect it themselves. Get the full signed attestation envelope (DSSE, Ed25519) for one already-tracked MCP server's latest probe run, by "provider/name" ref — the raw envelope…
search_mcpsFind MCP servers by what their tools do. Search already-tracked MCP servers on MCP Checkup by tool name/description text (max 512 chars), with optional transport, protocol_revision, and auth_required filters, up to `limit` results…
request_checkAsk for a one-off public observation of the MCP server at a full endpoint URL — this is the only tool here that contacts a third-party server, and it contacts exactly the host you name. `target` must begin with "http://" or "https://"; to…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"mcpcheckup": {
"type": "http",
"url": "https://mcpcheckup.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http mcpcheckup https://mcpcheckup.com/mcpclaude.ai, ChatGPT and other clients: add https://mcpcheckup.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.