Skip to main content
Glama

Related Servers

Alternatives to AgentAudit

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a security scanner for AI agent skills and MCP servers, detecting threats like prompt injection, identity hijacking, and memory poisoning.
      15 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A security scanner that evaluates installed MCP servers for vulnerabilities by aggregating findings from 16 scanning engines into detailed trust scores. It enables users to scan their local AI agent configurations or specific repository URLs for potential security risks.
      4
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Scans MCP servers for security vulnerabilities, prompt injection, and tool poisoning, providing risk scores and protection.
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables scanning of AI agent code for security vulnerabilities such as prompt injection, tool abuse, and data exfiltration, directly from MCP-compatible clients like Claude Code.
      2
      LGPL 3.0

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: discover_servers is for listing installed servers, audit_package for deep code audits, check_package for registry lookups, etc. However, check_package and consensus_analysis both relate to registry lookups and could be confused, though descriptions clarify that one is for initial checks and the other for multi-auditor consensus.

    Naming Consistency4/5

    Six of the seven tools follow a consistent verb_noun pattern (discover_servers, audit_package, submit_report, check_package, search_packages, scan_tool_poisoning). The one deviation is 'consensus_analysis', which uses a noun phrase instead of a verb_noun form, creating a minor inconsistency.

    Tool Count5/5

    With 7 tools, the set is well-scoped for the security-audit domain. Each tool serves a distinct stage (discovery, lookup, search, audit, submission, consensus, poisoning scan), fitting comfortably within the ideal 3-15 range without bloat or deficiency.

    Completeness4/5

    The toolset covers the full workflow from discovering installed servers to auditing, submitting reports, and obtaining consensus. While there is no tool to edit or delete submitted reports, this is a minor gap and the core lifecycle is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues