Skip to main content
Glama
MCP Agent Health Reporter

MCP Agent Health Reporter

by aos-standard

Related Servers

Alternatives to MCP Agent Health Reporter

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Runs read-only, offline static scans of the local machine's MCP server configs and agent skill folders, surfacing prompt injection, hidden Unicode, dangerous commands, credential paths, hardcoded secrets, unpinned packages, and over-broad filesystem or transport scope as text, JSON, SARIF, or HTML reports an agent can act on. Also allows scanning a single downloaded skill folder or a saved tools/list JSON so an agent can vet third-party components before installing them.
      40 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a deterministic pre-install security scan for Agent skills, plugins, and MCP servers via stdio, returning verdicts, audited badges, CI gates, and reports without executing code or making network calls.
      99 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that lets an agent audit its own environment by discovering local MCP configurations and skill folders on Windows, macOS, and Linux and running offline static checks for prompt injection, hidden instructions, hardcoded secrets, dangerous commands, unpinned packages, and excessive filesystem or transport permissions. It exposes tools to scan everything discovered, list configurations, vet a single skill, or analyze supplied text, returning text, JSON, SARIF, or HTML findings with CI-friendly severity levels.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only repository health scanning tools for drift detection, module reachability, prompt bloat, evidence calibration, and registration completeness, enabling agents to diagnose repositories via MCP.
      1
      MIT

    TDQS

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one performs a health scan on a specific agent, the other is a self-connectivity check. No overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow the consistent pattern 'aos_agent_health_<verb>', using snake_case and clear verb descriptors ('scan' and 'self_test').

    Tool Count3/5

    Two tools is minimal but acceptable for a focused health reporter. However, the server's scope feels limited, bordering on thin.

    Completeness2/5

    Missing obvious operations like listing agents, batch scanning, or retrieving historic results. The surface covers only one core action and a connectivity test, leaving significant gaps.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing