← Registry

Developer Tools

mcpcheckup.com

Searches, inspects, and reports on MCP servers, including their tool lists, recent changes, and signed attestations.

1 endpoint6 known toolsFirst detected September 21, 2026Last detected September 21, 2026

ENDPOINT 1

https://mcpcheckup.com/mcp

No auth detected

MCP server metadata

Name
mcpcheckup
Version
0.2.0
Capabilities
tools.listChanged
Server instructions

MCP Checkup publishes observed facts about public MCP servers: reachability, protocol revision, tool and schema fingerprints, 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 one number or a verdict. Typical use: when a user is choosing, adding, or debugging an MCP server, look it up with check_mcps (by "provider/name", endpoint URL, or domain) and read the details with get_mcp_report. search_mcps finds servers by what their tools do, get_mcp_history shows recent toolset changes, and get_attestation returns the signed attestation envelope when there is one. Those five tools only read what is already tracked and never contact the server in question. request_check is the only tool that contacts a third-party server, and it contacts exactly the host in the URL you give it. Rate limit: about 20 requests per minute per client, counted per Cloudflare location; a 429 response carries Retry-After. No authentication and no paid tier for this endpoint.

Known tools 6

check_mcps

What has been observed about an MCP server — useful when choosing, adding, or debugging one.

Inferred read-only
get_mcp_report

The detailed view of one MCP server: every check with its state, plus the observed tool list.

Inferred read-only
get_mcp_history

Whether an MCP server's toolset changed recently.

Inferred read-only
get_attestation

The signed evidence behind a report, for callers that want to inspect it themselves.

Inferred read-only
search_mcps

Find MCP servers by what their tools do.

Inferred read-only
request_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 server, and it contacts exactly the host you name.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mcpcheckup]
url = "https://mcpcheckup.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "mcpcheckup": {
      "type": "http",
      "url": "https://mcpcheckup.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: mcpcheckup
Remote MCP URL: https://mcpcheckup.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mcpcheckup": {
      "url": "https://mcpcheckup.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "mcpcheckup": {
      "type": "http",
      "url": "https://mcpcheckup.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "mcpcheckup",
  "transport": "streamable-http",
  "url": "https://mcpcheckup.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.