mcpbeat

MCP Registry Validator — Check Endpoints Actually Resolve MCP Server

io.github.operatorsheets/mcp-uptime
answering

MCP Registry Validator — Check Endpoints Actually Resolve is answering right now. Last checked moments ago. It exposes 4 tools.

Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
411 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add mcp-uptime --transport http https://mcp-uptime.theopslog.workers.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-uptime": {
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-uptime]
url = "https://mcp-uptime.theopslog.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-uptime": {
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-uptime": {
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

known
get_known_tools
The tool list last observed at an MCP endpoint, with the timestamp of the most recent schema change. Reads stored history; does not probe.
mcp
check_mcp_endpoint
Probe 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.
schema
check_schema_drift
Probe 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.
uptime
get_uptime
Uptime history for an MCP endpoint over the last N days (max 30), with incident windows. Reads stored history; does not probe.

Endpoints

URLTransportStateLatencyChecked
https://mcp-uptime.theopslog.workers.dev/mcp streamable-http answering 238 ms 0 min ago

MCP Registry Validator — Check Endpoints Actually Resolve — questions

Answers built from our own checks of this server.

What can MCP Registry Validator — Check Endpoints Actually Resolve do?
It exposes 4 tools, read directly from the server on our last check. Among them: check_mcp_endpoint, check_schema_drift, get_known_tools, get_uptime. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is MCP Registry Validator — Check Endpoints Actually Resolve working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 411 ms. The bar chart above shows every period we have measured.
How do I connect MCP Registry Validator — Check Endpoints Actually Resolve?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MCP Registry Validator — Check Endpoints Actually Resolve need an API key?
No. MCP Registry Validator — Check Endpoints Actually Resolve completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is MCP Registry Validator — Check Endpoints Actually Resolve?
It answers our handshake in 411 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.