Skip to main content
Glama

Related Servers

Alternatives to audit-mcp-cli

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Audits package lockfiles for vulnerabilities, supporting npm, yarn, and pnpm. Runs via CLI or as an MCP server over stdio.
      1
      21 npm
      78
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Node.js-based frontend security audit tool that performs comprehensive dependency security audits for both local projects and remote repositories. Generates detailed Markdown reports with vulnerability detection, risk assessment, and fix recommendations.
      1
      5 npm
      7
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to audit npm, Yarn, and pnpm lockfiles from local directories or remote Git repositories via a stdio MCP interface, with configurable vulnerability thresholds, registry, dev-dependency skipping, retry, and text/JSON output.
      21 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables auditing npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories, returning vulnerability reports in text or JSON with configurable severity thresholds and dev-dependency filtering.
      21 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables auditing npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories for dependency vulnerabilities, with configurable severity thresholds, dev-dependency skipping, and text or JSON reporting.
      21 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables auditing npm, Yarn, and pnpm lockfiles from local directories or remote Git repositories through an MCP tool, returning vulnerability results in text or JSON with configurable thresholds and optional dev dependency skipping.
      21 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined.

    Naming Consistency5/5

    The single tool follows a clear verb_noun pattern (audit_dependencies), which is consistent and descriptive.

    Tool Count4/5

    The tool count matches the narrow scope of auditing Node.js dependencies. While a single tool may feel minimal, it fully covers the intended functionality.

    Completeness3/5

    The tool covers security auditing and report generation, which is the core purpose. However, it lacks support for other package managers (e.g., yarn) and additional lifecycle operations like fixing or updating dependencies.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues