MCP Registry Validator — Check Endpoints Actually Resolve MCP server
Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.
Little public usage data yet
Reviews
Write oneNobody has reviewed MCP Registry Validator — Check Endpoints Actually Resolve yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
MCP Registry Validator — Check Endpoints Actually Resolve tools (4)
write = sends, deletes, buys or postscheck_mcp_endpointFreeProbe an MCP endpoint right now: is it alive, which transport it speaks, how many tools it exposes, and whether its tool schema changed since the last check. Use before depending on a third-party MCP server.
check_schema_driftFreeProbe an MCP endpoint and diff its tool schema against the last stored snapshot: tools added, removed, or whose description/inputSchema changed. Schema drift fails quietly mid-run, which is why it is worth checking.
get_known_toolsFreeThe tool list last observed at an MCP endpoint, with the timestamp of the most recent schema change. Reads stored history; does not probe.
get_uptimeFreeUptime history for an MCP endpoint over the last N days (max 30), with incident windows. Reads stored history; does not probe.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 363ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenanceno repository listed3/15
- Maintainer identityno repository or website to verify2/10
Findings (1)
- lowNo source repository listed
maint.no-repo
Install directly
claude mcp add --transport http mcp-uptime https://mcp-uptime.theopslog.workers.dev/mcp
MCP Registry Validator — Check Endpoints Actually Resolve: common questions
- Is MCP Registry Validator — Check Endpoints Actually Resolve MCP server safe?
- With care: it is graded C, so read the findings first (67/100). Read the MCP Registry Validator — Check Endpoints Actually Resolve safety report
- How do I install MCP Registry Validator — Check Endpoints Actually Resolve?
- It runs remotely at mcp-uptime.theopslog.workers.dev. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does MCP Registry Validator — Check Endpoints Actually Resolve need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is MCP Registry Validator — Check Endpoints Actually Resolve maintained?
- The latest release is v0.2.1.
- Is MCP Registry Validator — Check Endpoints Actually Resolve up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of MCP Registry Validator — Check Endpoints Actually Resolve?
- Servers from other publishers that do the same job: Oh My Posh Validator MCP server, Domain Liveness MCP server and Business Contact Finder MCP server. Compare all MCP Registry Validator — Check Endpoints Actually Resolve alternatives.
Alternatives to MCP Registry Validator — Check Endpoints Actually Resolve
Same job from other publishers: the closest match first, then the best rated.
Oh My Posh ValidatorValidate oh-my-posh configurations and segment snippets against the official schema.not reviewedEstablishedA- Domain LivenessIs this business's website still there? Checks apex and www, and DNS separately from HTTP.not reviewedEstablishedA
- Business Contact FinderCheck how to contact a business website, and whether that contact path actually works.not reviewedEstablishedA
