Skip to content

use-latest-version-mcp

Stop suggesting stale package versions. Live version truth for AI coding assistants — across 39 registries — plus a safe scan → optimize → validate → apply upgrade pipeline.

plugin-validate License: FSL-1.1-ALv2 Claude Code plugin Ask DeepWiki Docs

Install

Claude Code

/plugin marketplace add 88plug/claude-code-plugins
/plugin install use-latest-version@88plug

Grok Build

grok plugin marketplace add 88plug/claude-code-plugins
grok plugin install use-latest-version@88plug --trust

No environment variables. No API keys. On first launch the plugin compiles itself and starts the MCP server.

Tip

Enable auto-update once (/plugin → Marketplaces → 88plug → Enable auto-update) and you always get the latest at startup.

Manual, Docker, and generic MCP client setup: Installation.

Quickstart

Ask the assistant:

You say Tool
What's the latest express on npm? get_latest_version
Is requests==2.28.0 current? compare_versions
Scan this project for outdated deps check_outdated
Plan an upgrade, show the diff first optimize_versions → validate_upgrade_plan → apply_upgrades

The apply step is dry-run by default. You only write files when you pass dry_run: false. Details: Getting Started and Tool Reference.

Why it exists

A model's training data has a cutoff. Left alone it writes versions that were current then. This server asks the registry every time — then can inventory, plan, and apply dependency upgrades for a whole repo.

What it does

Capability Tools
Lookup latest version + metadata, install command, semver compare get_latest_version, get_package_info, get_install_command, compare_versions, check_multiple_packages
Project scan and outdated report scan_project, check_outdated
Conflict / compatibility / upgrade path check_compatibility, detect_conflicts, find_compatible_version, suggest_upgrade_path, resolve_conflicts
Whole-project plan → validate → apply optimize_versions, validate_upgrade_plan, apply_upgrades

15 tools total. Full argument lists: Tool Reference.

Registries

39 registries behind one interface: npm, PyPI, Maven, crates.io, Go, RubyGems, NuGet, Packagist, Hex, pub.dev, CRAN, CPAN, Clojars, Hackage, Dub, LuaRocks, Elm, Swift, JSR, Conda, Bioconductor, Docker Hub, GHCR, Quay, GCR, GitHub, GitLab, Homebrew, AUR, Snap, Flatpak, Chocolatey, CocoaPods, Gradle, Terraform, Ansible Galaxy, VS Code, WordPress, Jenkins.

Name formats and aliases: Supported Registries.

Safety

apply_upgrades is the only tool that writes to disk.

  • Defaults to dry_run: true (preview only)
  • When writing (dry_run: false), backs up each file under .dependency-backups/ unless create_backup: false
  • Rolls back a file's edits on error

Everything else is read-only. Optional GITHUB_TOKEN only raises GitHub rate limits for github / ghcr / swift — never required.

Start here

Features

Feature Detail
Live version lookup Latest version, package info, install command, batch checks
Semver compare Pin vs latest: update-available / up-to-date / ahead-of-latest
Project scan Manifests + lock files (package.json, requirements.txt, go.mod, Cargo.toml, …)
Outdated report Major / minor / patch + estimated risk
Conflict reasoning Compatibility, detect conflicts, find compatible version, upgrade path
Safe upgrade pipeline optimize_versions → validate_upgrade_plan → apply_upgrades
Write safety Only apply_upgrades writes; dry_run: true by default; backups + rollback
39 registries npm, PyPI, Maven, crates.io, Go, Docker/GHCR, Homebrew, and more
Local-first MCP No API key; optional GITHUB_TOKEN only raises GitHub rate limits

Development

git clone https://github.com/88plug/use-latest-version-mcp
cd use-latest-version-mcp
npm ci
npm run build
node build/index.js stdio        # or: http
# tests
for t in test-*.js; do node "$t"; done
bun test test-upgrade-applier.test.js test-upgrade-validator.test.js

Docs site (Material for MkDocs, strict):

pip install mkdocs mkdocs-material
mkdocs build --strict

See CONTRIBUTING.md.