Depverse MCP Server

If you already use Depverse, the depverse mcp server is the piece that lets your assistant work with it directly. The server speaks MCP's stdio transport, so it plugs straight into Claude Code, Claude Desktop, Cursor, Cline, Windsurf, and Copilot Chat. No API key required — the client brings its own auth.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• get_latest_version — Latest stable version string of a package
• get_all_versions — Every published version (plus a count)
• get_version_info — Manifest for a specific version (deps, license, engines, …)
• get_dist_tags — All dist-tags (latest, beta, next, …) and the versions they point to
• get_changelog — Release notes from GitHub Releases (if a version is given) or CHANGELOG.md from the linked repo
• check_version_exists — Boolean check: is pkg@version published?
• get_package_info — High-level metadata card: name, description, author, license, homepage, maintainers, created/modified dates
• get_package_readme — README markdown for the latest version (truncated to 20,000 chars)
• get_package_keywords — Keywords / tags declared in package.json
• get_package_repository — Source repo URL, plus a parsed owner/repo slug when the repo is on GitHub
• get_package_homepage — Homepage URL + npm page URL as a fallback
• get_package_license — Declared license (string, SPDX, or legacy array form)

Credentials and setup notes

• Python 3.10+ - uv (recommended) or plain pip - Network access to registry.npmjs.org, api.osv.dev, api.npmjs.org and (for changelogs) api.github.com / raw.githubusercontent.com > No Anthropic API key required. Claude Code (or any MCP client) brings its own auth. A key is only needed if you also want to use the optional bundled CLI chat

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Depverse's toolset — get_latest_version, get_all_versions, get_version_info and 11 more — is a fair guide to whether it matches your workflow. It is maintained by yash-neural; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Depverse.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.