Skip to main content
Glama
KryptosAI

MCP Observatory

by KryptosAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP Observatory

No user-submitted related servers found.

    Related Servers

    • MCP server config linter and

      rajmaurya0904
      A
      license
      Not graded
      quality
      B
      maintenance
      Validates .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

    • SilentFail

      decksaga
      A
      license
      Not graded
      quality
      C
      maintenance
      Diagnose 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.
      1
      MIT

    • Scepter

      VeldanDev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      352 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    Resources