Skip to main content
Glama

MCP Registry Validator — Check Endpoints Actually Resolve

Server Details

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

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A4.3/5.0

Scored across 4 tools

Disambiguation4/5

Most tools are clearly distinct: get_known_tools and get_uptime read history, while check_mcp_endpoint is a general live probe. The only potential confusion is between check_mcp_endpoint and check_schema_drift, as both involve schema changes, but their descriptions clarify that one is a broad health check and the other is a focused diff.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: check_ for active probes and get_ for historical retrievals. This makes the tool's behavior predictable from its name.

Tool Count5/5

Four tools is well-scoped for a validator/monitoring server, covering live checks and historical reads without unnecessary bloat.

Completeness4/5

The server covers live probing, schema drift detection, and historical views of tools and uptime. A minor gap is the lack of a tool to list all monitored endpoints or manage snapshots, but for the stated purpose the core operations are present.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Checks the MCP server you're building the way clients and agents meet its tool list. It flags what agents misread (vague parameters, writes marked read-only), what breaks clients or prompt caches (tools that appear mid-session, schemas that change on every call), and breaking changes between releases with the version bump they need. Same input, same answer: no LLM involved.
      6
      2,042 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Runs the MCP initialize handshake and validates tools/list JSON schemas on any public MCP server, and inspects x402 payment endpoints. Ships as a stdio MCP server the agent calls directly, plus a CLI and a GitHub Action. Read-only, no API key needed.
      558 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables checking an MCP server before installation by returning outside-in trust ratings, comparing candidates, and listing dated tool-surface findings for 7,000+ operators, with publisher and fleet concentration data and no key required.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets agents check remote MCP servers before calling a tool, returning a safe/caution/unsafe verdict with live status, latency, auth requirements, spec readiness and whether the tool list just changed in a breaking way. It also suggests alternative servers for a given capability and sends webhook alerts when a watched server's verdict, auth state, or tool list changes.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources