Skip to main content
Glama
princeruhulofficial

MCP Tool Auditor

by princeruhulofficial
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP Tool Auditor

No user-submitted related servers found.

    Related Servers

    • teeshield

      teehooai
      A
      license
      A
      quality
      D
      maintenance
      Static security linter for MCP servers. Scans tool definitions for vulnerabilities (path traversal, SQL injection, SSRF), scores description quality, and auto-rewrites descriptions for safer agent tool selection.
      2
      10
      MIT

    • MCP Tool Security Inspector

      danveil
      A
      license
      Not graded
      quality
      A
      maintenance
      Performs explainable, deterministic static analysis of MCP tool metadata to detect misleading instructions, concealed capabilities, and schema drift without executing tools.
      1
      MIT

    • mcp-tool-poison-guard

      princeruhulofficial
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that detects and guards against tool poisoning and prompt injection attacks in tool descriptions and schemas. It provides risk scoring, pattern detection, safe rewriting, and audit reports with zero external API cost.
      MIT

    • Plugin Health Auditor MCP

      AMATSUGI-120
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides audit_plugin_health and prepare_semantic_review tools for deterministic inspection of Codex plugins and Agent Skills, generating evidence-backed reports without executing or transmitting target code.
      1
      MIT
    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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation4/5

    Audit_tool and audit_tool_list overlap in purpose (auditing descriptions) but are clearly separated by scope (single vs. list). Rewrite and best practices are distinct. The descriptions make the boundaries clear, so confusion is unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (audit_tool, rewrite_tool_description, audit_tool_list, get_best_practices). No mixed casing or stylistic deviations.

    Tool Count5/5

    Four tools is well-scoped for the server's purpose. Each tool addresses a distinct step in the auditing workflow: reference, single audit, batch audit, and rewrite.

    Completeness4/5

    The core workflow is covered: get best practices, audit individual or list, and rewrite weak descriptions. A minor gap is lack of a validation/apply tool after rewriting, but the existing set supports the main use case effectively.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources