Skip to main content
Glama

Server Details

Registry Rot Watch: liveness + successor-contract verdicts for MCP endpoints.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2024-11-05
URL
ChatGPT
–
Claude
–

TDQS

B3.3/5.0

Scored across 5 tools

Disambiguation4/5

add_watch and list_watches are clearly distinct from the verdict/probe tools, but get_verdict, probe_endpoint, and successor_check all return contract/status information and could be confused without careful reading. The descriptions do clarify the live-probe vs stored-verdict vs successor-snapshot distinction.

Naming Consistency4/5

Four tools follow a verb_noun pattern (add_watch, get_verdict, list_watches, probe_endpoint), but successor_check breaks it with a noun_noun form. The deviation is minor and the overall style remains predictable.

Tool Count5/5

Five tools are well-scoped for a focused endpoint-rot monitoring service, with each tool covering a distinct capability (watch management, live probe, verdict retrieval, successor check). No tool feels redundant or excessive.

Completeness3/5

Watch lifecycle is incomplete: add_watch and list_watches exist, but there is no delete_watch or update_watch to stop or modify a watch. Agents can work around this by ignoring watches, but the missing removal operation is a notable gap for a watch-based service.

Available Tools

5 tools
add_watchCInspect

Watch an endpoint for status/contract changes (watch entitlement required)

get_verdictBInspect

Latest vault verdict for an endpoint ($0.01/call; one free trial query per operator)

list_watchesBInspect

List your watches and alerts

probe_endpointAInspect

Live anonymous MCP probe of an endpoint, stored to the vault ($0.01/call)

successor_checkBInspect

Successor-contract verdict from the stored pre-move snapshot ($0.01/call)

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
      Autonomous synthetic health checks, JSON-RPC 2.0 handshake validation, breaking schema drift detection, and credential leak scanning for remote MCP servers.
      3
      30 npm
      1
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Read-only MCP server that exposes governed operational records with provenance and validity windows so clients can check which evidence is still current before answering. It lets agents reconcile freshness, schedule state, and evidence specificity to determine whether scheduled automations are actually healthy, rather than trusting an expired dashboard summary.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for CometBFT/Cosmos validator operators: checks signing liveness and downtime-jail risk, diagnoses chain halts (who isn't voting), and reports peer topology and upgrade readiness. Keyless and GET-only, with node IPs masked by default.
      28
      6
      1
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources