Audits npm, pip, cargo, and other package manifests against the OSV database to detect known CVEs and malicious packages.
Also known as GuardBee/guardbee-mcp, @guardbee/mcp-dependency-auditor
- Stars
- 2
- Tools
- 4
- Downloads, 30 days
- 2,406
- Latest version
- 0.2.4
- Last commit
- Nov 12, 2026
- License
- MIT
What is dependency-auditor MCP?
dependency-auditor audits npm, pip, cargo, and other package manifests against the OSV database to detect known CVEs and malicious packages. It exposes 4 tools, such as audit_npm, audit_pip, audit_package.
Summary generated from the project's README
About dependency-auditor MCP server
Scanning software projects for security vulnerabilities is what dependency-auditor enables for developers using AI clients like Claude. By connecting to the OSV database, this server identifies known CVEs and malicious packages across multiple ecosystems including npm, pip, cargo, and composer. It works locally via an MCP configuration and requires no authentication to access Google's open-source vulnerability data.
Users can perform targeted scans using tools like audit_npm, audit_pip, or audit_package for single-package lookups. The server supports a wide range of lockfiles such as package-lock.json, pnpm-lock.yaml, poetry.lock, and Cargo.lock. It distinguishes between production and development dependencies and provides a clear fix plan by suggesting the smallest version upgrade that resolves all active advisories.
Security teams benefit from advanced prioritization features that highlight exploits currently used in the wild via CISA KEV and EPSS probability scores. The system also detects malicious releases and provides dependency paths to show exactly how a vulnerable package entered a project. Findings are de-duplicated to ensure that overlapping advisories do not clutter the report.
What you can do with it
- 1Scan local project dependenciesAsk the AI to audit all npm dependencies within a specific local directory path.
- 2Check a specific package versionVerify if a particular version of a library has a known security vulnerability.
- 3Audit Python environmentsRun a security scan on a Python project using its manifest or lockfiles.
- 4Identify malicious package releasesDetect and prioritize known-malicious releases that require immediate credential rotation.
Written from the project's README. Every use case is checked against a quote from it.
How to install dependency-auditor MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall dependency-auditor MCP in Claude Code
$ claude mcp add dependency-auditor -- npx -y @guardbee/mcp-dependency-auditorInstall dependency-auditor MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"dependency-auditor": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dependency-auditor"
]
}
}
}Install dependency-auditor MCP in VS Code
.vscode/mcp.json
{
"servers": {
"dependency-auditor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dependency-auditor"
]
}
}
}Install dependency-auditor MCP in VS Code CLI
$ code --add-mcp '{"name":"dependency-auditor","type":"stdio","command":"npx","args":["-y","@guardbee/mcp-dependency-auditor"]}'Install dependency-auditor MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"dependency-auditor": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dependency-auditor"
]
}
}
}Install dependency-auditor MCP in Codex
$ codex mcp add dependency-auditor -- npx -y @guardbee/mcp-dependency-auditorInstall dependency-auditor MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.dependency-auditor] command = "npx" args = ["-y", "@guardbee/mcp-dependency-auditor"]
Install dependency-auditor MCP in Gemini CLI
$ gemini mcp add -s user dependency-auditor npx -- -y @guardbee/mcp-dependency-auditorInstall dependency-auditor MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"dependency-auditor": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dependency-auditor"
]
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @guardbee/mcp-dependency-auditor 0.2.4 in an isolated container with no network and no keys. It answered and listed 4 tools.
dependency-auditor MCP tools 4
Read from the server with tools/listaudit_npmAudit npm dependencies from a package.json (and optionally package-lock.json) for known CVEs using the OSV database
audit_pipAudit Python dependencies from requirements.txt or pyproject.toml for known CVEs using the OSV database
audit_packageAudit a single package by name, version, and ecosystem
audit_directoryAuto-detect and audit npm and pip manifests (package.json, requirements.txt, pyproject.toml) in a directory
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@guardbee/mcp-dependency-auditor
🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch
An MCP server that audits npm and pip manifests against the OSV database for known CVEs. A single-package lookup also covers PyPI, crates.io, Maven, Go, and RubyGems.
Telemetry is off by default. With
GUARDBEE_TELEMETRY=1it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields likecontent,tokenorpasswordare replaced with a placeholder. See@guardbee/mcp-telemetry.
Features
- OSV API Integration — Google's open-source vulnerability database (free, no authentication required)
- npm Support — reads exact versions from
package-lock.json/npm-shrinkwrap.json(v1/v2/v3),pnpm-lock.yaml(v5/v6/v9),yarn.lock(v1 and Berry) andbun.lock, falling back topackage.jsonranges. Transitive packages are included, and dev-only packages are told apart even when the lockfile does not mark them (pnpm v9, yarn, bun) - Rust, Go, Ruby, PHP —
Cargo.lock(dev crates fromCargo.toml),go.mod(// indirectandreplaceaware),Gemfile.lock(platform builds merged, dev groups from theGemfile) andcomposer.lock(packages-dev), audited byauditand theaudit_directorytool - pip Support — reads exact versions from
uv.lock,poetry.lockandPipfile.lock(dev groups separated), falling back torequirements.txt,requirements/base.txt,requirements/prod.txt, andpyproject.toml - Malicious Package Detection — known-malicious releases (OpenSSF
MAL-*entries and advisories classified CWE-506, e.g. the hijackedchalk@5.6.1/debug@4.4.2of September 2025) are reported first as critical, with a removal and credential-rotation action, and fail any--fail-onthreshold - Exploit Prioritization — findings are enriched with CISA KEV (exploited in the wild, ransomware use) and FIRST EPSS (probability of exploitation in 30 days) and ordered malware → KEV → severity → EPSS. Gate CI on them with
--fail-on-kev/--fail-on-epss=<0-1>(--fail-on=noneturns the severity gate off). Only CVE IDs are sent;--no-exploit-dataorexploit-data: falseinguardbee.ymlturns it off - Severity Scoring — Critical / High / Medium / Low based on CVSS score or a text heuristic
- Fix Plan — one upgrade per package: the smallest listed version that clears every advisory (e.g.
log4j-core 2.14.1 → 2.25.4 (fixes 7/7)), with advisories that stay open and major-version jumps called out. Per-finding fixes follow the installed release line (next-auth 5.0.0-beta.31 → 5.0.0-beta.32, not 4.24.15), using SemVer, PEP 440 or Maven-style version ordering - CVE Links — direct links to NVD or osv.dev
- Dependency Paths — each finding shows how the package gets installed (
express@4.21.2 › proxy-addr@2.0.7), and the fix plan names the direct dependency to bump (← via express@4.21.2). Available forpackage-lock.jsonv2/v3, pnpm, yarn, bun and uv lockfiles - De-duplicated Findings — advisories that alias each other (GHSA + PYSEC, GHSA + MAL) are merged into one finding; ignore lists match any of their IDs
- Tests — unit tests with lockfiles generated by the real package managers and a fake OSV API
Quick Start
npm install -g @guardbee/mcp-dependency-auditor
Add to claude_desktop_config.json:
{
"mcpServers": {
"guardbee-dependency-auditor": {
"command": "npx",
"args": ["-y", "@guardbee/mcp-dependency-auditor"]
}
}
}
MCP Tools
| Tool | Description |
|---|---|
audit_npm |
Audits npm dependencies (package-lock, pnpm, yarn, bun lockfiles or package.json) |
audit_pip |
Audits Python dependencies (uv, Poetry, Pipenv lockfiles or requirements.txt / pyproject.toml) |
audit_package |
Audits a single package by name, version, and ecosystem |
audit_directory |
Auto-detects and audits all supported manifest files |
Example Usage
You can ask Claude:
"Audit my project's npm dependencies:
/Users/me/my-app"
"Is there a CVE for lodash 4.17.20?"
"Scan my Python project:
/Users/me/django-app"
Example Output
⚠️ Found 3 vulnerabilities in 2/142 npm packages (1243ms)
Critical: 1 High: 1 Medium: 1 Low: 0 Unknown: 0
[CRITICAL] lodash@4.17.20
ID : GHSA-35jh-r3h4-6jhm (CVE-2021-23337)
Summary : Command injection via template
Fix : upgrade to lodash@4.17.21
Details : https://nvd.nist.gov/vuln/detail/CVE-2021-23337
Supported Ecosystems
The audit_package tool can query these ecosystems directly:
| Ecosystem | Parameter |
|---|---|
| npm | npm |
| Python | PyPI |
| Rust | crates.io |
| Java | Maven |
| Go | Go |
| Ruby | RubyGems |
CLI — CI/CD Integration
In addition to MCP server mode, this can also be used directly as a CLI:
# Audit all dependencies in a directory (npm + pip auto-detected)
npx @guardbee/mcp-dependency-auditor audit ./my-project
# npm only
npx @guardbee/mcp-dependency-auditor audit-npm . --fail-on=critical
# pip only
npx @guardbee/mcp-dependency-auditor audit-pip . --fail-on=high
# Single package
npx @guardbee/mcp-dependency-auditor audit-pkg lodash 4.17.20 npm
# JSON output
npx @guardbee/mcp-dependency-auditor audit . --format=json
# Fail only on what attackers actually use: CISA KEV, or EPSS ≥ 10%
npx @guardbee/mcp-dependency-auditor audit . --fail-on=none --fail-on-kev --fail-on-epss=0.1
Exit codes: 0 = clean · 1 = findings above threshold · 2 = error
GitHub Actions
name: Dependency Audit
on: [push, pull_request]
jobs:
audit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 20
- run: npm ci
- name: Audit dependencies
run: npx @guardbee/mcp-dependency-auditor audit . --fail-on=high
GitLab CI
dependency-audit:
image: node:20
script:
- npx @guardbee/mcp-dependency-auditor audit . --fail-on=high
only:
- merge_requests
- main
Pre-commit Hook
# .git/hooks/pre-push
npx @guardbee/mcp-dependency-auditor audit . --fail-on=critical || exit 1
Development
npm install
npm test # 20 unit tests
npm run build # TypeScript compile
License
MIT — GuardBee
Feedback
Questions, ideas, or a false positive? Start a thread in GitHub Discussions or open an issue. If GuardBee is useful to you, a ⭐ on the repository helps others find it.
dependency-auditor MCP questions
How do I add dependency-auditor MCP to Claude Code?
Run claude mcp add dependency-auditor -- npx -y @guardbee/mcp-dependency-auditor in your terminal. Add --scope user to make it available in every project.
How do I add dependency-auditor MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does dependency-auditor MCP provide?
It exposes 4 tools, including audit_npm, audit_pip, audit_package, audit_directory.
Does the dependency auditor require an API key?
No, it uses Google's open-source vulnerability database which is free and requires no authentication.
Which ecosystems are supported for single package lookups?
You can audit npm, PyPI, crates.io, Maven, Go, and RubyGems.
How does the tool handle malicious packages?
Known-malicious releases are reported first as critical and include recommended removal and credential-rotation actions.