depsdev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host to bind when using the streamable-http transport. | 127.0.0.1 |
| MCP_PORT | No | Port to bind when using the streamable-http transport. | 8000 |
| MCP_TRANSPORT | No | Transport to use: `stdio` or `streamable-http`. | stdio |
| DEPSDEV_RETRIES | No | Retries on HTTP 429, 502, 503, 504 and timeouts. | 2 |
| DEPSDEV_TIMEOUT | No | Request timeout in seconds. | 30 |
| DEPSDEV_BASE_URL | No | API root (for a mirror or proxy). | https://api.deps.dev/v3 |
| DEPSDEV_MAX_CHARS | No | Responses longer than this are cut with a notice. | 20000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Look up open-source package facts from deps.dev (Open Source Insights): versions, licences, security advisories, dependency graphs and source-project health. Start with audit_package for a quick review of one package, or package_overview to find which version to inspect. Data is read-only and needs no credentials.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| package_overviewA | 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. |
| version_detailsA | 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). |
| dependenciesA | 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. |
| requirementsA | 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. |
| audit_packageA | 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. |
| advisoryA | Details of one security advisory by its OSV id (for example GHSA-xxxx-xxxx-xxxx): title, severity, CVSS v3, aliases such as CVE ids. |
| project_healthA | 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. |
| project_packagesA | Packages published from a source project, grouped by package with version counts. Verified source-repo links are listed first. |
| lookup_hashA | Identify which package versions a file hash belongs to (for example the SHA-256 of a downloaded archive). Accepts hex or base64. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.