depver-mcp
Checks the public npm registry for package versions, including latest stable and latest overall versions, exact version existence, range resolution, and deprecation notices.
Checks Packagist for package versions, including latest stable and latest overall versions, exact version existence, range resolution, and abandoned-package status.
Checks PyPI for package versions, including latest stable and latest overall versions, exact version existence, yanked status, range resolution, and project deprecation status.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
depver-mcp
A local MCP server that tells AI coding agents which package
versions really exist. One tool, check_packages, asks the public registries of npm, PyPI,
pub.dev and Packagist and answers with the latest stable version, the latest version
overall, whether a given version or range resolves, and whether the package is deprecated. No
account, no database, no hosted service: it runs on your machine and talks to the registries
directly.
Why: agents writing package.json, requirements.txt, pubspec.yaml or composer.json from
memory invent version numbers. This tool replaces the guess with a lookup, in one call for up to
100 packages, with a response small enough not to eat your context window.
Install
Requires Node.js 20 or newer. Nothing else: the package ships as a single file with no runtime dependencies.
Claude Code: add to .mcp.json in your project (or ~/.claude.json for all projects):
{
"mcpServers": {
"depver": {
"command": "npx",
"args": ["-y", "depver-mcp"]
}
}
}or run:
claude mcp add --transport stdio depver --scope project -- npx -y depver-mcpCursor: the same mcpServers entry in .cursor/mcp.json (project) or ~/.cursor/mcp.json
(global). Other stdio-capable clients: see docs/clients.md.
Restart the agent. It now sees a tool called check_packages.
Related MCP server: package-version-check-mcp
What the agent sees
Verify that packages exist and get their current versions from public registries (npm, PyPI, pub.dev, Packagist). Use before writing or updating a dependency manifest instead of guessing versions. Accepts up to 100 packages from mixed ecosystems in one call. Pass
versionto check an exact version or resolve a range.
The tool is annotated read-only, idempotent and open-world (it reaches external registries), so hosts that auto-approve read-only tools will not prompt for it.
Input
{
"packages": [
{ "ecosystem": "npm", "name": "react" },
{ "ecosystem": "pip", "name": "requests", "version": "2.31.0" },
{ "ecosystem": "pypi", "name": "requests", "version": ">=2.0,<2.20" },
{ "ecosystem": "dart", "name": "http", "version": "^1.0.0" },
{ "ecosystem": "composer", "name": "laravel/framework", "version": "~10.0" },
{ "ecosystem": "npm", "name": "left-pad", "version": "1.3.0" },
{ "ecosystem": "pub", "name": "htttp" }
]
}packages: 1 to 100 items. More is a validation error, never a silent truncation.ecosystem: a canonical name or an alias (table below), case-insensitive.name: the package name as your package manager spells it (@types/node,laravel/framework).version(optional): an exact version or a range in that ecosystem's own syntax.
Output
One minified JSON text block with one result per input item, in input order:
{
"results": [
{ "e": "npm", "n": "react", "s": "ok", "stable": "19.3.1", "latest": "19.3.1" },
{
"e": "pypi",
"n": "requests",
"s": "ok",
"stable": "2.34.2",
"latest": "2.34.2",
"v": "2.31.0",
"v_exists": true,
"v_yanked": false
},
{
"e": "pypi",
"n": "requests",
"s": "ok",
"stable": "2.34.2",
"latest": "2.34.2",
"v": ">=2.0,<2.20",
"v_match": "2.19.1"
},
{
"e": "pub",
"n": "http",
"s": "ok",
"stable": "1.6.0",
"latest": "1.6.0",
"v": "^1.0.0",
"v_match": "1.6.0"
},
{
"e": "packagist",
"n": "laravel/framework",
"s": "ok",
"stable": "v13.39.0",
"latest": "v13.39.0",
"v": "~10.0",
"v_match": "v10.48.29"
},
{
"e": "npm",
"n": "left-pad",
"s": "deprecated",
"stable": "1.3.0",
"latest": "1.3.0",
"v": "1.3.0",
"v_exists": true,
"v_deprecated": true,
"msg": "use String.prototype.padStart()"
},
{ "e": "pub", "n": "htttp", "s": "not_found" }
]
}Key | Meaning |
| Canonical ecosystem and the name as the registry knows it |
| Status: |
| Highest version that is neither a pre-release nor yanked (npm: the |
| Highest version overall, pre-releases included, yanked excluded |
| Echo of the |
| The exact version is published |
| That version was yanked (PyPI) or retracted (pub.dev) |
| That version carries a deprecation notice (npm) |
| Highest stable version satisfying the range, or |
| One sentence: deprecation notice, reason, or failure |
Keys are omitted when they do not apply. There are no nulls except v_match: null, no
descriptions, authors or changelogs.
Statuses
| Meaning |
| The package exists. If every version is yanked, |
| The package exists and its registry marks it deprecated: npm (latest version deprecated), PyPI (project status), pub.dev (discontinued), Packagist (abandoned). |
| The registry says nothing installable exists under this name: never existed, unpublished, or quarantined. |
| The registry could not be asked (timeout, outage, rate limit, malformed answer) or the item was unusable (unknown ecosystem, unparseable range). An error never means the package does not exist. |
Supported ecosystems
Ecosystem | Aliases | Registry | Range syntax |
|
| registry.npmjs.org | node-semver: |
|
| pypi.org | PEP 440: |
|
| pub.dev | pub: |
|
| packagist.org | Composer: |
Ranges are interpreted with each ecosystem's own rules, not translated through a common library:
Composer's ~10.0 means >=10.0 <11.0, PyPI's ~=2.31 means >=2.31, ==2.*, and so on.
Limits and behaviour
Up to 100 packages per call, mixed ecosystems allowed.
Registry requests run in parallel, at most 6 at a time per registry, with an 8 second timeout per request and one retry on network errors. One slow registry never blocks the others.
Results are cached in memory for 5 minutes while the server process lives. Nothing is written to disk.
DEPVER_MCP_DEBUG=1prints diagnostics to stderr. Nothing is ever written to stdout except protocol messages.npx depver-mcp --helpand--versionprint to stderr and exit.
Privacy
Queries go from your machine straight to the public registries, with a User-Agent of
depver-mcp/<version> (+https://github.com/tweetgeek/depver-mcp). No telemetry, no proxy, no
account.
Contributing
See CONTRIBUTING.md. Adding an ecosystem is one adapter file plus fixtures.
License
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
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.
Check npm/PyPI packages exist and that a function or method exists in an exact package version.
Live npm and UNPKG data for AI agents: resolution, audits, import maps, malware/CVE checks.
Related MCP Servers
- AlicenseAqualityCmaintenanceChecks npm and PyPI packages for outdated versions, deprecation status, and breaking changes with cited sources, enabling AI agents to verify dependency freshness.16 npmISC
- AlicenseAqualityBmaintenanceEnables AI coding agents to retrieve the latest stable versions of packages and tools across multiple ecosystems, preventing outdated dependency versions in generated code.4187 PyPI9Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables users to look up package versions, scan for vulnerabilities, and analyze dependencies across multiple registries (npm, Maven, PyPI, etc.) using exact version recommendations for security.5MIT
- AlicenseNot gradedqualityDmaintenanceValidates and checks packages across 19 ecosystems to prevent AI agents from installing hallucinated, deprecated, or malicious packages.60 npmAGPL 3.0