Skip to main content
Glama
mcp-fleet-doctor

mcp-fleet-doctor

by yuehancn

Related Servers

Alternatives to mcp-fleet-doctor

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables static, read-only auditing of MCP servers’ registry entries, package metadata, client configurations, and tool definitions for supply-chain security indicators. It returns merged reports with transparent skipped checks and never executes the inspected code.
      6
      113 PyPI
      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.
      118 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Local-first MCP audit and cleanup tool that scans MCP configs to find stale servers, abandoned packages, duplicates, context-heavy tools, risky permissions, and major upgrades, generating reversible patch plans.
      54 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Security scanning for MCP servers from the inside out. Provides runtime inspection, AST-based static analysis, config audit, dependency analysis, and OWASP MCP Top 10 compliance in a single MCP server.
      55
      100 npm
      5
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct primary role: full health pass, baseline recording, static-only audit, and baseline diff. However, check_fleet is a superset that also performs baseline comparison and config auditing, so it overlaps functionally with diff_baseline and audit_config_only. The descriptions clarify when to prefer the narrower tools, but the boundaries are not perfectly sharp.

    Naming Consistency5/5

    All tool names use snake_case with a consistent verb-first pattern: check_fleet, record_baseline, audit_config_only, diff_baseline. The '_only' suffix on audit_config_only is a readable modifier rather than a convention break.

    Tool Count5/5

    Four tools is well-scoped for a fleet health and baseline management server. Each tool corresponds to a meaningful workflow: full check, baseline capture, static audit, and drift diff.

    Completeness4/5

    The surface covers the core lifecycle of checking fleet health, recording a baseline, auditing configuration, and diffing drift. Minor gaps remain, such as no explicit tool to list configured servers or delete/reset a baseline, but agents can work around these via record_baseline and the full report.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues