Skip to main content
Glama
MCP Server Change and Health Monitor

MCP Server Change and Health Monitor

Related Servers

Alternatives to MCP Server Change and Health Monitor

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to look up and search servers from the official MCP registry, probe any server live for availability, protocol, auth, tools and context-token cost, and retrieve registry-wide statistics. Also supplies a CLI and GitHub Action that measure how many tokens your own configured servers' tool definitions consume against a budget.
      MIT
    • 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
      409 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets an agent inspect and audit MCP servers before connecting to them, checking their exposed tools, prompts and resources for tool poisoning, shadowing, excessive permissions, leaked secrets and unsafe transports against 24 deterministic rules. Results are returned as findings with evidence, remediation and CWE/OWASP references, and can fail CI with SARIF, Markdown or standalone HTML reports.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      npm audit for MCP servers. Point it at an MCP server and get a security grade (A–F) covering missing auth, SSRF surface, high-privilege tools, prompt-injection-prone tool descriptions, and leaked secrets.
      12 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that checks npm and PyPI package health, providing maintenance signals, version info, CVE counts, and alternative suggestions.
      MIT

    TDQS

    A4/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of misselection between overlapping tools. Its purpose—health-checking and diffing MCP servers—is clearly stated.

    Naming Consistency5/5

    The single name check_mcp_servers follows a clear verb_noun snake_case convention. With one tool there is no inconsistency to introduce.

    Tool Count3/5

    A single tool is thin even for a narrow monitoring scope; the three input modes (URL, npm package, registry search) could arguably be distinct tools. Still, one 'check' operation is a defensible minimal surface.

    Completeness3/5

    The core action—probe a server, report latency, exposed tools, and diffs with breaking changes marked—is covered. However, there's no way to manage a watchlist, batch-check multiple servers, or retrieve historical results beyond 'since the last run'.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues