Skip to main content
Glama
aos-standard

MCP Agent Health Reporter

by aos-standard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to MCP Agent Health Reporter

No user-submitted related servers found.

    Related Servers

    • yotta-verify-mcp by YottaMeta

      yotta-verify-mcpofficial

      YottaMeta
      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.
      707 npm
      MIT

    • repo-health

      chenyinrusi
      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

    • agent-sec-mcp

      sudo-ai-git
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables authorized security auditing of AI-agent supply chains and agent-facing surfaces: deterministic local skill-bundle audits against eight attack patterns, secrets scanning, and scope-gated read-only recon of agent endpoints and MCP surfaces.
      MIT

    • skillguard

      RudrenduPaul
      A
      license
      A
      quality
      B
      maintenance
      Security scanner for third-party AI agent-skill files: SKILL.md manifests, hooks, and bundled scripts, exposed via an MCP tool.
      1
      16 npm
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityStale
    ResponsivenessNo issues

    Resources