Skip to main content
Glama
MCP Security Audit Server

MCP Security Audit Server

by qianniuspace

Security Audit Tool

NPM version License: MIT

A powerful MCP (Model Context Protocol) Server that audits npm package dependencies for security vulnerabilities. Built with remote npm registry integration for real-time security checks.

Features

  • πŸ” Real-time security vulnerability scanning

  • πŸš€ Remote npm registry integration

  • πŸ“Š Detailed vulnerability reports with severity levels

  • πŸ›‘οΈ Support for multiple severity levels (critical, high, moderate, low)

  • πŸ“¦ Compatible with npm/pnpm/yarn package managers

  • πŸ”„ Automatic fix recommendations

  • πŸ“‹ CVSS scoring and CVE references

Installing via Smithery

To install Security Audit Tool for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @qianniuspace/mcp-security-audit --client claude

MCP Integration

  1. Add MCP configuration to Cline /Cursor:

{
  "mcpServers": {
    "mcp-security-audit": {
      "command": "npx",
      "args": ["-y", "mcp-security-audit"]
    }
  }
}

Option 2: Download Source Code and Configure Manually

  1. Clone the repository:

git clone https://github.com/qianniuspace/mcp-security-audit.git
cd mcp-security-audit
  1. Install dependencies and build:

npm install
npm run build
  1. Add MCP configuration to Cline /Cursor :

{
  "mcpServers": {
    "mcp-security-audit": {
      "command": "npx",
      "args": ["-y", "/path/to/mcp-security-audit/build/index.js"]
    }
  }
}

Related MCP server: locklens

Configuration Screenshots

Cursor Configuration

Cursor Configuration

Cline Configuration

Cline Configuration

API Response Format

The tool provides detailed vulnerability information including severity levels, fix recommendations, CVSS scores, and CVE references.

Response Examples

1. When Vulnerabilities Found (Severity-response.json)

{
  "content": [{
    "vulnerability": {
      "packageName": "lodash",
      "version": "4.17.15",
      "severity": "high",
      "description": "Prototype Pollution in lodash",
      "cve": "CVE-2020-8203",
      "githubAdvisoryId": "GHSA-p6mc-m468-83gw",
      "recommendation": "Upgrade to version 4.17.19 or later",
      "fixAvailable": true,
      "fixedVersion": "4.17.19",
      "cvss": {
        "score": 7.4,
        "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"
      },
      "cwe": ["CWE-1321"],
      "url": "https://github.com/advisories/GHSA-p6mc-m468-83gw"
    },
    "metadata": {
      "timestamp": "2024-04-23T10:00:00.000Z",
      "packageManager": "npm"
    }
  }]
}

2. When No Vulnerabilities Found (no-Severity-response.json)

{
  "content": [{
    "vulnerability": null,
    "metadata": {
      "timestamp": "2024-04-23T10:00:00.000Z",
      "packageManager": "npm",
      "message": "No known vulnerabilities found"
    }
  }]
}

Development

For development reference, check the example response files in the public directory:

  • Severity-response.json : Example response when vulnerabilities are found (transformed from npm audit API response)

  • no-Severity-response.json : Example response when no vulnerabilities are found (transformed from npm audit API response)

Note: The example responses shown above are transformed from the raw npm audit API responses to provide a more structured format. The original npm audit API responses contain additional metadata and may have a different structure.

Contributing

Contributions are welcome! Please read our Contributing Guide for details on our code of conduct and the process for submitting pull requests.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Author

ESX (qianniuspace@gmail.com)

Available Tools

1 tool
audit_nodejs_dependenciesC

Audit specific dependencies for vulnerabilities

Inputs: dependencies (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/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 stated in its name and description, making it unambiguous.

    Naming Consistency5/5

    A single tool name follows a clear verb_noun pattern (audit_nodejs_dependencies) which is consistent with typical MCP naming conventions. There are no other names to compare, but the pattern is clear.

    Tool Count1/5

    Having only one tool is extremely thin for a security audit server. Auditing dependencies likely requires supporting operations like resolving dependency trees, checking for updates, or generating reports, which are missing.

    Completeness1/5

    The server's purpose appears to be auditing Node.js dependencies, but it only offers a single operation that audits dependencies without coverage for other lifecycle steps like viewing audit results, fixing vulnerabilities, or scanning different scopes.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to audit npm, Yarn, and pnpm lockfiles in local projects or remote Git repositories through MCP, with configurable vulnerability thresholds, dev-dependency skipping, retry counts, and text or JSON reports.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables auditing npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories via an MCP tool, returning vulnerability results in text or JSON with configurable thresholds, registry, dev-dependency skipping, and retries.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables auditing npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories through an MCP tool, returning vulnerability results in text or JSON with configurable thresholds and dev dependency skipping.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables auditing npm, Yarn, and pnpm lockfiles in local directories or remote Git repositories through MCP tools, returning vulnerability results with configurable thresholds, registry, dev-dependency skipping, and text or JSON output.
      9 npm
      MIT