MCP Registry Validator — Check Endpoints Actually Resolve MCP server

MCP Registry Validator — Check Endpoints Actually Resolve is an MCP server with 4 tools an agent can call, among them check_mcp_endpoint, check_schema_drift, get_known_tools. It answers at https://mcp-uptime.theopslog.workers.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.

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

Description as the publisher wrote it.

The 4 tools MCP Registry Validator — Check Endpoints Actually Resolve offers

Add MCP Registry Validator — Check Endpoints Actually Resolve to your AI client

Every block below points at https://mcp-uptime.theopslog.workers.dev/mcp. Pick your client and copy.

claude mcp add --transport http mcp-registry-validator-check-end https://mcp-uptime.theopslog.workers.dev/mcp

{
  "mcpServers": {
    "mcp-registry-validator-check-end": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp-uptime.theopslog.workers.dev/mcp"]
    }
  }
}

{
  "mcpServers": {
    "mcp-registry-validator-check-end": {
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

{
  "servers": {
    "mcp-registry-validator-check-end": {
      "type": "http",
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

{
  "context_servers": {
    "mcp-registry-validator-check-end": {
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "mcp-registry-validator-check-end": {
      "serverUrl": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "mcp-registry-validator-check-end": {
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

name: MCP Registry Validator — Check Endpoints Actually Resolve
version: 0.0.1
schema: v1
mcpServers:
  - name: MCP Registry Validator — Check Endpoints Actually Resolve
    type: streamable-http
    url: https://mcp-uptime.theopslog.workers.dev/mcp

{
  "mcpServers": {
    "mcp-registry-validator-check-end": {
      "httpUrl": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "mcp-registry-validator-check-end": {
      "type": "http",
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "mcp-registry-validator-check-end": {
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

goose://extension?url=https%3A%2F%2Fmcp-uptime.theopslog.workers.dev%2Fmcp&type=streamable_http&id=mcp-registry-validator-check-end&name=MCP%20Registry%20Validator%20%E2%80%94%20Check%20Endpoints%20Actually%20Resolve

Is MCP Registry Validator — Check Endpoints Actually Resolve up right now?

It answered our last check on 22 October 2026 in 140 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to MCP Registry Validator — Check Endpoints Actually Resolve

Questions about MCP Registry Validator — Check Endpoints Actually Resolve

How many tools does MCP Registry Validator — Check Endpoints Actually Resolve have?

4, as returned by the server's own tools/list on 17 September 2026: check_mcp_endpoint, check_schema_drift, get_known_tools, get_uptime.

Is MCP Registry Validator — Check Endpoints Actually Resolve down?

It answered our last check on 22 October 2026 in 140 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add MCP Registry Validator — Check Endpoints Actually Resolve to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp-uptime.theopslog.workers.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does MCP Registry Validator — Check Endpoints Actually Resolve need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.operatorsheets. Endpoint host: mcp-uptime.theopslog.workers.dev. ARD identifier: urn:air:io.github.operatorsheets:mcp:mcp-uptime. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.