DepHealth MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DepHealth MCP audit the dependencies in ./my-project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DepHealth MCP
Dependency security & health auditing for AI agents — no account, no API key.
DepHealth is an MCP server that lets any AI agent (Claude Code, Claude Desktop, Cursor, …) answer two questions instantly:
"Are this project's dependencies safe?" →
audit_project"Should I add / upgrade to this package?" →
check_package
Vulnerability data comes from Google's OSV.dev (738K+ advisories, 40+ ecosystems); package health signals (latest version, license, release recency, deprecation) come from deps.dev. Both are free public APIs — zero signup, zero keys, zero config.
Why this instead of Snyk/Socket MCP?
DepHealth | Snyk MCP | Socket MCP | |
Account required | No | Yes | Yes (OAuth) |
API key / auth flow | None | Snyk auth | Sign-in via client |
Ecosystems | npm, PyPI, Go, crates.io | many | many |
Token-lean output | Yes — capped, structured | — | — |
Open source | MIT | partial | partial |
MCP servers are notorious for context bloat (some inject 50K+ tokens of schema). DepHealth exposes 2 tools, 1 resource, 1 prompt with compact structured outputs — advisories are capped at 5 per package, worst-severity first, with the fix version included.
Related MCP server: @4da/mcp-server
Install
Requires Python 3.11+ and uv.
git clone https://github.com/hasarahman/dephealth-mcp
cd dephealth-mcp && uv syncClaude Code:
claude mcp add --scope user dephealth -- uv run --project /path/to/dephealth-mcp dephealth-mcpClaude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"dephealth": {
"command": "uv",
"args": ["run", "--project", "/path/to/dephealth-mcp", "dephealth-mcp"]
}
}
}Tools
audit_project(path)
Scans every supported manifest directly in path — package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml — batch-queries OSV, and returns a structured report:
verdict: "1 of 2 checked dependencies have known vulnerabilities (worst severity: HIGH)."
vulnerable_packages:
- lodash 4.17.20 (npm) — 5 advisories
GHSA-35jh-r3h4-6jhm CVE-2021-23337 HIGH Command Injection fixed_in: 4.17.21
...
unpinned_skipped: ["flask"] # hygiene flag: deps with no resolvable versionRange specifiers (^4.17.20, >=2.0) are audited at their floor and marked version_is_range_floor: true.
check_package(ecosystem, name, version?)
The "should I add this?" tool. Omit version to check the latest release. Combines OSV advisories with deps.dev health signals and returns a verdict:
avoid— CRITICAL/HIGH vulnerabilities in this versioncaution— lower-severity vulns, no release in 2+ years, or deprecatedok— clean and maintained
check_package("npm", "left-pad")
→ verdict: caution
reasons: ["no release since 2018-04-09 (possibly unmaintained)",
"latest version is marked deprecated"]Resource & prompt
dephealth://ecosystems— supported ecosystems and their manifest filessecurity_review(project_path)— a guided prompt: audit, verify upgrade targets are clean, produce a prioritized remediation list
Development
uv run pytest # in-process MCP client tests (hit the live free APIs)
uv run fastmcp dev src/dephealth_mcp/server.py # interactive inspectorBuilt with FastMCP. MIT license.
Available Tools
2 toolsaudit_projectA
Scan a project's dependency manifests (package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml) and report known vulnerabilities from the OSV.dev database. Use before deploying, reviewing, or adopting a codebase.
Inputs: path (required). Returns: path, verdict, manifests_found, unpinned_skipped, +2 more
check_packageA
Assess one package before adding or upgrading it: known vulnerabilities (OSV.dev) plus health signals (deps.dev) — latest version, license, release recency, deprecation. Returns a verdict: ok, caution, or avoid.
Inputs: name (required), ecosystem (required), version. Returns: name, reasons, verdict, version, +7 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
Each tool has a clearly distinct purpose: audit_project scans entire project manifests for vulnerabilities, while check_package assesses a single package before adding/upgrading. No overlap in functionality.
Both tool names follow the consistent verb_noun pattern using snake_case (audit_project, check_package), making them predictable and easy to understand.
With only 2 tools, the server is minimal but well-scoped for dependency health auditing. While additional tools could be added, the current set covers the core use cases.
The tools cover the primary needs: scanning a project and checking a single package. Missing operations like updating dependencies or listing all vulnerabilities are minor gaps that agents can work around.
Maintenance
Related MCP Connectors
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Related MCP Servers
- AlicenseAqualityDmaintenanceActs as a security checkpoint for AI coding agents by intercepting package installations to verify existence, check against CVE databases, and block vulnerable or hallucinated dependencies before they reach your codebase. Provides seven security tools including pre-install gates, full project audits, safe version recommendations, and deep transitive dependency scanning for npm and PyPI packages.742 npm5MIT
- AlicenseAqualityAmaintenanceDependency intelligence for AI agents. CVE scanning, health checks, upgrade planning.9590 npm2Apache 2.0
- AlicenseAqualityDmaintenanceProvides verified dependency-audit verdicts for AI agents, checking installed versions against OSV advisories and splitting direct vs transitive dependencies.3MIT
- AlicenseAqualityBmaintenanceVulnerability intelligence for AI agents that enables CVE lookup, package vulnerability checks, and dependency auditing without API keys.5MIT