get_latest_versionLABSCO SUMMARY
Version questions answered by the registry, not by recollection.
Which version is current, what a version pulled in, and what changed since the one you are on are exactly the facts a model states confidently and gets a year out of date. This puts the npm registry behind them, including the changelog from the linked repo.
What it is
An MCP server over the public npm registry, exposing package and version data as structured tools so an assistant answers from registry.npmjs.org rather than from memory.
What you get
- The latest stable version of a package, and the complete list of every version published
- The manifest for one specific version — dependencies, license, engines and the rest
- All dist-tags (latest, beta, next and any others) and the versions they point at
- Release notes pulled from GitHub Releases, or CHANGELOG.md from the linked repository
- A yes-or-no check on whether a given package@version was ever published
- Package metadata beyond versions: description, author, license, homepage, maintainers, keywords, repository and README
Requirements
A recent Python, speaking MCP over stdio, so it drops into Claude Code, Claude Desktop, Cursor, Cline, Windsurf and Copilot Chat with one config entry. No API key — the npm registry data it reads is public.
Setup effort
Build from source — git clone https://github.com/yash-neural/Depverse.git
USE CASES
01
Deciding whether an upgrade is worth doing
Compare the version you are pinned to against the current one, then read the release notes between them before touching the lockfile.
02
Checking what a version actually drags in
Read that version's manifest — dependencies, license, engine constraints — instead of installing it to find out.
03
Working out which tag to install from
See every dist-tag and the version behind it, so beta and next stop being guesses about what you would get.
04
Verifying a version referenced in an old build file
Confirm whether that exact package and version was published at all, before debugging why an install fails.
05
Writing the upgrade note for your team
Pull the changelog and the version list together, so the summary you circulate names real releases and real changes.
58 tools
Listed in project docs. Your client may show a different list.
get_all_versionsget_version_infoget_dist_tagsget_changelogcheck_version_existsget_package_infoget_package_readmeget_package_keywordsget_package_repositoryget_package_homepageget_package_licenseget_package_sizeget_dependenciesget_peer_dependenciesget_dev_dependenciesget_dependency_treecheck_peer_compatibilitycheck_vulnerabilitiesget_deprecation_statuscheck_maintainer_activityget_download_statscheck_typosquat_riskget_download_trendcompare_popularityget_download_by_versionget_vulnerability_detailsaudit_all_dependenciescheck_supply_chain_riskget_patched_versioncheck_node_compatibilitycompare_versionsget_breaking_changesresolve_semvercheck_outdatedsearch_packagesget_similar_packagesget_packages_by_authorget_organization_packagesbatch_get_versionsvalidate_package_jsongenerate_install_commandresolve_cdn_urlget_bundle_sizeget_bundle_size_historycheck_treeshakeablecompare_bundle_sizesget_bundle_size_impactcheck_esm_supportcheck_cjs_supportcheck_typescript_supportget_exports_mapcheck_browser_compatiblecheck_deno_compatibleget_package_on_jsrsuggest_upgrade_pathfind_replacement_packagecheck_migration_guideBEFORE YOU INSTALL
What to know first
Tools you get
58 tools named in the project's documentation.
Requires
Python 3.10+
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/yash-neural/Depverse.git
cd Depverse
uv venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
uv pip install -e .MCP Clients
Claude Desktop, Any MCP client
JSON
{
"mcpServers": {
"Depverse": {
"type": "stdio",
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_DEPVERSE>",
"run",
"mcp_server.py"
],
"env": {}
}
}
}
