A
licenseNot graded
qualityC
maintenanceScans MCP servers for deprecated and removed protocol features, providing a dated migration checklist.
5 npm
MIT
MCP Observatory
by KryptosAI
Related Servers
Alternatives to MCP Observatory
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceDiagnose, secure, and benchmark your MCP servers. Zero-config CLI for Claude Code, Cursor, VS Code, and Windsurf.48 npm3MIT
- AlicenseNot gradedqualityBmaintenanceZero-dependency MCP server inspector for protocol conformance, tool annotations, and capability checks.MIT
- AlicenseNot gradedqualityCmaintenanceDiagnose MCP servers — health checks, tool testing, token cost audits, conflict detection, and security scanning with 50+ prompt injection patterns. Works as CLI or MCP server inside Claude Desktop.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables checking whether MCP servers are alive, maintained, and safe to use by scoring metadata health and trust, scanning MCP config files, and optionally wrapping a server to log tool calls and errors locally.MIT
- AlicenseAqualityCmaintenanceLets users discover, compare, and audit public MCP servers from the official registry, validate server.json metadata, and generate installation snippets and publication checklists.6MIT
TDQS
B3.4/5.0
Scored across 13 tools
Disambiguation2/5
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.
Naming Consistency3/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityActive
ResponsivenessWithin a week