Categories › AI & Agents › Multi-agent, orchestration & workflows
Observed facts on public MCP servers: protocol checks, tool changes, signed evidence. No verdicts.
Remote server: your requests and data go to mcpcheckup.com. Claude Code: claude mcp add --transport http mcp-checkup https://mcpcheckup.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
check_mcps — What has been observed about an MCP server — useful when choosing, adding, or debugging one. Look up the current monitored status of up to 5get_mcp_report — The detailed view of one MCP server: every check with its state, plus the observed tool list. Get the full observed report for one already-tget_mcp_history — Whether an MCP server's toolset changed recently. Get recent history for one already-tracked MCP server on MCP Checkup, by "provider/name" rget_attestation — The signed evidence behind a report, for callers that want to inspect it themselves. Get the full signed attestation envelope (DSSE, Ed25519search_mcps — Find MCP servers by what their tools do. Search already-tracked MCP servers on MCP Checkup by tool name/description text (max 512 chars), wirequest_check — Ask 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 serveNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.