Skip to main content
Glama
mcp-triage

mcp-triage

Related Servers

Alternatives to mcp-triage

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI hosts to list services, retrieve service details, and run deterministic support diagnostics through three stdio-based MCP tools.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to inspect and diagnose their own MCP setup by exposing read-only tools that audit configured servers, report which coding agents have configs, surface misplaced or duplicated registrations, and list curated preset packs. It also powers CLI workflows for checking handshake, tool lint, and tool-surface quality scores of any stdio server.
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables an agent or MCP client to scan MCP server configs and AI-agent tool manifests on demand, exposing tools that list detection rules and report hidden prompt injections, data-exfiltration attempts, embedded secrets, deceptive Unicode, unpinned packages and shell-launching tools. Each finding comes with a severity and location so risky tool descriptions can be caught before an attacker exploits them.
      64 PyPI
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables stdio MCP clients to gather read-only diagnostics and incident evidence from Linux homelabs, including health, disks, services, Docker containers, logs, and confirmation-required remediation proposals.
      10
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only API incident triage through MCP tools that classify HTTP failures, timeouts, slow responses, rate limits, and missing observations, and inspect configured public service endpoints, producing structured and human-readable incident reports.
      MIT

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are sharply delineated: triage_scan is read-only and reports problems, while triage_fix performs repairs. There is no overlap in purpose or output.

    Naming Consistency5/5

    Both tools follow the same 'triage_' prefix plus a clear verb ('scan', 'fix'). The naming pattern is uniform and predictive.

    Tool Count4/5

    With only two tools, the set is slightly below the typical 3-15 range, but scan/fix form a natural pair for a focused triage utility. No redundant tools exist.

    Completeness3/5

    triage_scan detects a wide range of configuration issues (PATH, env vars, transport mismatches, etc.), but triage_fix only repairs parse failures. This creates a significant gap: many detected issues have no corresponding fix action.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues