MCP Observatory
Related Servers
Alternatives to MCP Observatory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceValidates .mcp.json and claude_desktop_config files to catch duplicate server names, missing binaries, invalid environment variables, and unreachable endpoints. Reports each problem along with how to fix it, so silently failing MCP servers can be diagnosed and repaired.MIT
- AlicenseNot gradedqualityCmaintenanceScans MCP servers for deprecated and removed protocol features, providing a dated migration checklist.6 npmMIT
- AlicenseAqualityDmaintenanceDiagnose, secure, and benchmark your MCP servers. Zero-config CLI for Claude Code, Cursor, VS Code, and Windsurf.44MIT
- AlicenseAqualityBmaintenanceChecks 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.6528 npm1MIT
- AlicenseNot gradedqualityDmaintenanceZero-dependency MCP server inspector for protocol conformance, tool annotations, and capability checks.MIT
- AlicenseAqualityBmaintenanceChecks MCP servers by URL, npm package, or official MCP Registry search, reporting availability, response speed, exposed tools, resources, and prompts. It flags changes since prior runs as breaking, warning, or info using saved snapshots.1113 npmMIT
TDQS
Scored across 13 tools
Several tools overlap heavily in purpose: check_server, scan, watch, verify, and lock_verify all validate server health and/or compare against a known state. The distinctions between live check, cassette replay, lock file verification, and run-to-run diffing are subtle and could easily cause an agent to pick the wrong tool.
All names use snake_case and mostly start with a verb, but the conventions are mixed: single-word verbs (scan, record, replay, verify, watch), verb_noun (check_server, score_server, suggest_servers), get_* (get_last_run, get_history), and non-verb (ci_report). The pattern is readable but not uniform.
13 tools is well-scoped for an observability/health-check server. Each tool adds a distinct capability: scanning, scoring, recording, replaying, verifying, diffing, watching, locking, history, and CI reporting. No obvious bloat.
The toolset covers scan/check/score/record/replay/verify/watch/lock/history/CI workflows comprehensively. Minor gaps like listing/deleting run artifacts or managing lock files directly exist, but they don't cause fundamental failures.