MCP Security Audit logo

MCP Security Audit

by qianniuspace

Audits npm dependencies against the remote registry and reports severity, CVE, CVSS, and upgrade information.

Install MCP Security Audit

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "qianniuspace-mcp-security-audit": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-security-audit"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 1 tools correctly (28d ago).

Overview

qianniuspace/mcp-security-audit MCP server audits npm package dependencies for known security vulnerabilities using a remote npm registry. It returns structured findings with severity levels, descriptions, CVE and GitHub advisory references, CVSS data, and available fixes. The server supports npm, pnpm, and yarn projects and can recommend upgrade versions. Reach for it when an MCP-compatible client needs dependency security checks without leaving the development workflow.

Use cases

  • Audit npm dependencies for known vulnerabilities
  • Review package findings by severity
  • Identify upgrade versions for vulnerable packages
  • Inspect CVE and CVSS details in an MCP client

Key features

  • Remote npm registry security checks
  • Critical-to-low severity reporting
  • CVE, CVSS, CWE, and advisory references
  • Automatic fix recommendations
  • npm, pnpm, and yarn support
  • Structured clean-audit responses

Tools1

What MCP Security Audit lets your agent do. Expand a tool for its parameters.

Verified live~65 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

10/13 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · mcp-security-audit (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars57Stargazers on the source repository.
npm downloads353Package downloads in the last 30 days.
Last commit1y agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed1Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Security Audit works

What qianniuspace/mcp-security-audit MCP server does

qianniuspace/mcp-security-audit MCP server exposes npm dependency auditing through the Model Context Protocol. It checks dependencies for known vulnerabilities and returns a structured result for each finding. The reported data can include the affected package, installed version, severity, vulnerability description, CVE identifier, GitHub advisory ID, CVSS score and vector, CWE identifiers, advisory URL, and whether a fix is available.

The server recognizes four severity levels: critical, high, moderate, and low. When a vulnerable dependency has a known remedy, the response can include a recommended version and the fixed version. A clean result is represented separately, with metadata and a message indicating that no known vulnerabilities were found.

How it works

Audits use integration with the remote npm registry, allowing the server to perform current checks against registry-provided security information rather than relying only on local example data. The output is transformed into a more structured format than the raw npm audit response. Each response includes metadata such as the audit timestamp and package manager.

The documented examples show results for npm packages, including a vulnerable lodash version and its related advisory information. The README also identifies npm, pnpm, and yarn as supported package managers. It does not document a separate database, authentication flow, or a user-configurable registry URL.

Setup and configuration

The package can be run directly through npx:

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

The repository documents configuration for Cline and Cursor. Claude Desktop installation is also documented through Smithery. For a source-based setup, clone the repository, run npm install, and build it with npm run build; the resulting build entry point can then be referenced in an MCP client configuration.

Tools and capabilities

qianniuspace/mcp-security-audit MCP server provides dependency vulnerability scanning with:

  • Real-time checks through a remote npm registry
  • Critical, high, moderate, and low severity classification
  • Structured vulnerability reports
  • CVE, GitHub advisory, CVSS, and CWE details when available
  • Upgrade recommendations and fixed-version information
  • Support references for npm, pnpm, and yarn package managers
  • Clean-result responses when no known vulnerabilities are found

Client configuration should therefore be based on the package instructions rather than an assumed tool name.

Limitations and notes

The server reports known vulnerabilities returned by its audit source; a clean response should not be interpreted as proof that dependencies are free of every possible security issue. Its operation depends on access to the remote npm registry. Fix recommendations are reported as audit results; the documentation does not state that the server applies upgrades itself.

The project is released under the MIT License. Example response files are included in the repository for development reference, but they are transformed examples rather than a substitute for a live audit.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Security Audit

Run it with npx using `npx -y mcp-security-audit`, then add that command and package name to the MCP client configuration.

Yes.

Yes. The documented supported package managers are npm, pnpm, and yarn.

Reports can include severity, package and version, descriptions, CVE and GitHub advisory IDs, recommendations, fixed versions, CVSS data, CWE identifiers, and advisory URLs.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Security Audit AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/qianniuspace-mcp-security-audit?style=directory)](https://allmcps.com/mcp/qianniuspace-mcp-security-audit)
HTML Embed
<a href="https://allmcps.com/mcp/qianniuspace-mcp-security-audit"><img src="https://allmcps.com/api/badge/qianniuspace-mcp-security-audit?style=directory" alt="MCP Security Audit on AllMCPs" /></a>