Use MCP Checkup inside Claude before you connect an MCP server

MCP Checkup is now listed in Claude's connector directory. You can add it from inside Claude and ask what we have observed about an MCP server before you connect that server yourself.

Add it

1. In Claude, open Customize → Connectors → Browse.
2. Search for MCP Checkup and connect it.

You do not need an account with us, and the connector asks for no sign-in. The directory listing is at claude.ai/directory/connectors/mcp-checkup.

You can still add it by hand instead: Customize → Connectors → Add custom connector, with the address https://mcpcheckup.com/mcp and no authentication. The agents page has the steps for Claude and for other clients.

What to ask

Ask in your own words. Claude picks the tool. Some examples, with what comes back:

"Before we add acme/weather-mcp, check what MCP Checkup has observed about it." Claude calls check_mcps. You get when we last checked the server, the protocol revision it negotiated, whether it asked for credentials, when its tool list last changed, the checks that recorded an observed risk, and the checks that were not run, each with its reason. You can name a server by provider/name, by its endpoint URL, by its domain or by its name.

"Show me the full report for that server, including its tools." get_mcp_report returns every check with its state, plus the tool list from the most recent stored snapshot and the day that list was recorded.

"Has its tool list changed recently?" get_mcp_history lists recent tool-list changes. For changes in the last 30 days it names the tools that were added, removed, or had their parameters changed.

"Find MCP servers whose tools can read calendar events." search_mcps searches the servers we track by what their tools say they do.

"Get the signed attestation behind that result." get_attestation returns the signed envelope itself. The public keys are published at mcpcheckup.com/.well-known/mcpcheckup-keys.json, so you can verify it yourself instead of relying on our summary.

Every check comes back as VERIFIED, FAILED, OBSERVED_RISK or UNVERIFIED. A check that was not run says so, with a reason.

What it does not do

• It does not score servers. Results are never combined into one number or an overall verdict.
• Five of the six tools answer only from what we have already recorded, and never contact the server you ask about. request_check is the only one that does: it contacts exactly the host in the URL you give it, sends no credentials, and its result is not signed and not stored as a run.
• A server we do not track comes back as unknown, not as a guess.
• Requests are limited to about 20 per minute per IP address.

Listed is not endorsed

Claude's directory labels MCP Checkup a community connector: it went through Anthropic's automated review, and Anthropic has not verified it. The same distinction runs through what we publish. A result tells you what our probe observed and when, with reasons. It is not an endorsement of the server.

If something we report about your own server looks wrong, tell us.