MCP Registry Validator — Check Endpoints Actually Resolve

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

Should I use this

Quality & Safety

A
Description quality
95%
Schema completeness
100%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~409Tokens (tool definitions)
~658 BTypical response size
Minimal attention impact (0.32% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "mcp-uptime": {
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

Remote endpoints

https://mcp-uptime.theopslog.workers.dev/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢check_mcp_endpoint(url, include_tools)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Public http(s) URL of the MCP endpoint to inspect."
    },
    "include_tools": {
      "type": "boolean",
      "description": "Return the full tool list, not just the count."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}
🟢get_uptime(url, days)

Uptime history for an MCP endpoint over the last N days (max 30), with incident windows. Reads stored history; does not probe.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Public http(s) URL of the MCP endpoint to inspect."
    },
    "days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 30,
      "description": "Window in days. Default 30."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}
🟢get_known_tools(url)

The tool list last observed at an MCP endpoint, with the timestamp of the most recent schema change. Reads stored history; does not probe.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Public http(s) URL of the MCP endpoint to inspect."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}
🟢check_schema_drift(url)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Public http(s) URL of the MCP endpoint to inspect."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools