Skip to main content
Glama
mcp-security-auditor

mcp-security-auditor

by jashory

Related Servers

Alternatives to mcp-security-auditor

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to run deterministic, fully local static security and compliance audits of code, configurations, and dependencies through 32 MCP tools covering 24 vulnerability categories. It also detects the project stack, generates risk reports and checklists, suggests stack-aware remediations, and re-validates fixes to confirm vulnerabilities were eliminated.
      32
      1
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Security scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.
      2
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding assistants to perform real-time security auditing of MCP servers and AI agents, including code security scanning, prompt-injection fuzzing, and verification badge generation.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Agent-native "safe to ship?" security gate for AI-generated code. Uses real parsers and inter-rocedural taint analysis (JS/TS, Python, Go) to flag the classes AI coding agents get wrong — secrets, SQL injection, SS, SSRF, path traversal, command injection, weak JWT/CORS — and ranks findings by confidence. Exposes a scan tool over MCP.
      1
      8 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.
      MIT

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scanning, listing rules, and remediation. An agent should have no trouble choosing between them.

    Naming Consistency5/5

    All tools use consistent snake_case verb_noun naming: scan_path, list_security_rules, remediate_path. The pattern is predictable and readable.

    Tool Count4/5

    Three tools is a focused, reasonable surface for a local security auditor, and each earns its place. It is slightly thin, with no dedicated reporting or configuration tool.

    Completeness4/5

    The set covers scanning, rule discovery, and basic remediation, which are the core workflows. Minor gaps exist around exporting reports, configuring rule sets, or verifying remediation results.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues