depsdev-mcp
Integrates with deps.dev (Open Source Insights), Google's free service that tracks package versions, licences, security advisories and dependency graphs, providing read-only tools to look up package overviews, version details, declared requirements, resolved dependency trees, per-package vulnerability audits, individual OSV advisories, project health (GitHub stats and OpenSSF Scorecard results), packages published from a repository, and reverse hash lookups across ecosystems such as npm, PyPI, Cargo, Go, Maven, NuGet and RubyGems.
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., "@depsdev-mcp audit the npm package express for vulnerabilities in its dependencies"
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.
depsdev-mcp
A Model Context Protocol server for deps.dev (Open Source Insights), the free Google-run service that tracks versions, licences, security advisories and dependency graphs for open-source packages. It needs no API key.
The tools are shaped around questions people ask when choosing or reviewing a dependency, rather than one tool per endpoint. Advisories are resolved to titles and severities in the same call, responses are trimmed to the fields that matter, and failures come back as readable messages.
Supported ecosystems: npm, PyPI, Cargo, Go, Maven, NuGet and RubyGems (resolved dependency graphs: npm, PyPI, Cargo and Maven).
Setup
Requires Python 3.12+ and uv.
git clone <this repo> && cd depsdev-mcp
uv sync
uv run depsdev-mcp # stdio transportAdd it to any MCP client that launches stdio servers:
{
"mcpServers": {
"depsdev": {
"command": "uv",
"args": ["run", "--directory", "/path/to/depsdev-mcp", "depsdev-mcp"]
}
}
}For HTTP instead of stdio: MCP_TRANSPORT=streamable-http MCP_HOST=127.0.0.1 MCP_PORT=8000 uv run depsdev-mcp.
Related MCP server: package-intel-mcp
Tools
All tools are read-only.
Tool | What it returns |
| Default version, version and deprecation counts, most recent versions. Use it to pick a version. |
| Licences, publish date, deprecation, source projects, provenance flag, and the version's advisories with titles and severity (resolved in the same call). |
| Resolved dependencies of a version: direct or all, with direct/indirect counts. |
| Declared dependency constraints in the ecosystem's own form. Works for every supported system. |
| One-call review: the version's own advisories by severity, plus which of its dependencies (direct first) have known advisories. |
| One advisory by OSV id: title, severity, CVSS v3 score and vector, CVE aliases. |
| Stars, forks, open issues, licence and the OpenSSF Scorecard overall score, listing only the weak checks by default. |
| Packages published from a source repository, grouped, verified links first. |
| Which package versions a file hash (MD5, SHA1, SHA256, SHA512; hex or base64) belongs to. |
Version arguments are optional; when omitted the package's default (latest stable) version is used.
Configuration
All optional environment variables:
Variable | Default | Meaning |
|
| API root (for a mirror or proxy) |
|
| Request timeout in seconds |
|
| Retries on HTTP 429, 502, 503, 504 and timeouts |
|
| Responses longer than this are cut with a notice |
|
|
|
Limits
audit_packagechecks at mostmax_dependencies(default 60) dependencies, direct ones first, with up to 8 requests in flight. Large trees are reported as partially checked.Advisory data comes from deps.dev, which mirrors OSV. A clean result means no advisory is recorded there, not that a package is safe.
Scorecard data is only present for projects that the OpenSSF Scorecard project scans, and it can be several weeks old.
project_packagesreflects at most the 1,500 package versions that deps.dev returns for a project, so the package count can be a lower bound for very popular repositories.deps.dev does not document rate limits. The server retries politely but does not queue requests.
Development
uv sync
uv run pytestTests mock all HTTP traffic with respx; no network access is needed.
Licence
MIT. Author: Ankur Kapuriya. Not affiliated with or endorsed by Google or the deps.dev team.
Available Tools
9 toolsadvisoryARead-onlyIdempotent
Details of one security advisory by its OSV id (for example GHSA-xxxx-xxxx-xxxx): title, severity, CVSS v3, aliases such as CVE ids.
Inputs: advisory_id (required).
audit_packageARead-onlyIdempotent
One-call security and hygiene review of a package version: licences, deprecation, its own advisories by severity, and which of its dependencies (direct first) have known advisories. Replaces many separate lookups.
Inputs: name (required), system (required), version, max_dependencies.
dependenciesARead-onlyIdempotent
List the resolved dependencies of a version (npm, cargo, maven, pypi). Returns direct and indirect counts; scope 'direct' lists only direct dependencies, 'all' includes the transitive ones.
Inputs: name (required), system (required), limit, scope, +1 more.
lookup_hashARead-onlyIdempotent
Identify which package versions a file hash belongs to (for example the SHA-256 of a downloaded archive). Accepts hex or base64.
Inputs: hash_type (required), hash_value (required), limit.
package_overviewARead-onlyIdempotent
Summarise a package: default version, number of versions, how many are deprecated, and the most recently published versions. Use this first to pick a version for the other tools.
Inputs: name (required), system (required), recent.
project_healthARead-onlyIdempotent
Health of a source repository: stars, forks, open issues, licence and the OpenSSF Scorecard overall score. By default lists only the checks that scored below 10, weakest first.
Inputs: project_id (required), all_checks.
project_packagesARead-onlyIdempotent
Packages published from a source project, grouped by package with version counts. Verified source-repo links are listed first.
Inputs: project_id (required), limit.
requirementsARead-onlyIdempotent
Declared dependency constraints of a version, in the ecosystem's own form (for example npm dependencies and devDependencies with version ranges). Works for all systems, including go, nuget and rubygems.
Inputs: name (required), system (required), version.
version_detailsARead-onlyIdempotent
Facts about one package version: licences, publish date, deprecation, source projects, provenance flag, and its known security advisories with severity (already resolved, no extra calls needed).
Inputs: name (required), system (required), version.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct resource or workflow (package, version, dependencies, advisory, project, hash), but version_details, advisory, and audit_package overlap on security data, and dependencies vs requirements may be confused. Descriptions mostly clarify when to use which, so boundaries are usable but not perfectly crisp.
All names use snake_case and are readable, but the set mixes noun phrases (package_overview, version_details, dependencies) with verb-led names (audit_package, lookup_hash), so there is no single predictable verb_noun pattern. The inconsistency is mild and does not impede understanding.
Nine tools is well within a healthy range and matches the read-only package intelligence domain. Each tool covers a meaningful slice, even though audit_package is an intentional convenience aggregate rather than a fundamentally new capability.
The surface covers package overview, version facts, resolved and declared dependencies, advisories, audits, project health/packages, and hash identification, giving strong end-to-end coverage for dependency investigation. Minor gaps remain around package/version search and listing all versions, but agents can work around them with package_overview and version_details.
Maintenance
Related MCP Connectors
Real-time package and vulnerability data (Python, npm, Cargo, Go, and more) for AI coding agents.
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.
Package versions, licences and known vulnerabilities for npm, PyPI, crates, Go, Maven, NuGet
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and retrieve detailed package information from multiple package registries (NPM, crates.io, NuGet, PyPI, Go).3,695 npmMIT
- AlicenseAqualityBmaintenanceProvides software supply-chain intelligence for AI agents, enabling them to query package metadata, versions, downloads, dependencies, and health signals for npm, PyPI, and crates.io packages without API keys.666 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables checking whether software packages are deprecated, archived, stale, active, or unknown with supporting evidence, auditing dependency manifests, and looking up runtime support and end-of-life dates.MIT
- AlicenseNot gradedqualityBmaintenanceEnables safety-ranked discovery of open-source components across npm, PyPI, crates.io, RubyGems, GitHub, and Hugging Face, with license, security, and health checks.1,348 npmMIT