MCP Checkup

ClaudeCommunityby MCP Checkup

MCP Checkup watches public remote MCP servers and publishes what it observed: reachability, the protocol handshake and negotiated revision, tool-list and input-schema fingerprints and how they change over time, publicly observable auth metadata, and tool-description hygiene signals. Every check is reported as VERIFIED, FAILED, OBSERVED_RISK or UNVERIFIED. Results are never combined into a score or a verdict, and a check that was not run is never shown as passed. Use it when you are choosing, adding or debugging an MCP server. Ask Claude to look a server up by name, endpoint URL or domain, see its full check breakdown and observed tool list, find out whether its toolset changed recently, or search tracked servers by what their tools do. Results come from scheduled observations and are published as Ed25519-signed DSSE attestations that anyone can verify against https://mcpcheckup.com/.well-known/mcpcheckup-keys.json; get_attestation returns the raw signed envelope. Five of the six tools are read-only and answer only from data MCP Checkup has already recorded; they never contact the server you ask about. request_check is the only tool that contacts a third-party server: it runs one unsigned, on-demand observation of the exact endpoint URL you give it, and it is metered per caller, per site and per host. No account or sign-in is needed. The MCP endpoint is free.