Skip to main content
MCP server CX Codex

package-version-check-mcp — Claude Code MCP server

Feeds your coding agent the current version of a dependency instead of the one it remembers. Covers npm, PyPI, Go, Docker, Helm and GitHub Actions.

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add --env GITHUB_PAT=<GITHUB_PAT> --env PACKAGE_VERSION_CACHE_ENABLED=<PACKAGE_VERSION_CACHE_ENABLED> --transport stdio package-version-check-mcp -- uvx package-version-check-mcp
Open on GitHub

What package-version-check-mcp does

An agent writes a lockfile or a requirements list and pins versions from its training data. Those numbers go stale within weeks, and you end up fixing them by hand. This server asks the registries what is current and hands the answer back.

Coverage runs wide: npm, PyPI, NuGet, Maven and Gradle, Go, PHP, Ruby, Rust, Swift, Dart, plus Docker images, Helm charts, GitHub Actions and Terraform providers and modules. Tool versions for kubectl, terraform, gradle and roughly a thousand others come through mise-en-place. That last part needs the mise binary on your PATH; without it the get_supported_tools and get_latest_tool_versions calls fail.

Three ways to run it. A hosted endpoint at https://package-version-check-mcp.onrender.com/mcp over HTTP, a local uvx package-version-check-mcp --mode=stdio, or the published Docker image. The hosted route can hit rate limits imposed by the registries themselves. GITHUB_PAT is optional, though skipping it leaves you exposed to GitHub API throttling. Caching stays off until you set PACKAGE_VERSION_CACHE_ENABLED=true.

One thing to know up front: most models will not call these tools on their own. You have to ask for a version check in the prompt.

What it helps with

  • pin a dependency to its real current release
  • refresh versions the agent just added
  • find the newest Docker tag matching a suffix
  • read the current version of a GitHub Action
  • look up a Terraform provider or module version

Example prompts for the agent

  • Use the MCP to get the latest versions and write them into package.json
  • Update the dependencies you just added to their latest versions via MCP
  • Check the latest kubectl and terraform versions with the MCP tools

How to install package-version-check-mcp

Platform CLI

claude mcp add --env GITHUB_PAT=<GITHUB_PAT> --env PACKAGE_VERSION_CACHE_ENABLED=<PACKAGE_VERSION_CACHE_ENABLED> --transport stdio package-version-check-mcp -- uvx package-version-check-mcp

Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from package-version-check-mcp <command>

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about package-version-check-mcp

How do I install package-version-check-mcp in Claude Code?

Run claude mcp add package-version-check-mcp -e GITHUB_PAT=<GITHUB_PAT> -- uvx package-version-check-mcp. Or use the variant with caching and an explicit transport: `claude mcp add --env GITHUB_PAT=<GITHUB_PAT> --env PACKAGE_VERSION_CACHE_ENABLED=<PACKAGE_VERSION_CACHE_ENABLED> --transport stdio package-version-check-mcp -- uvx package-version-check-mcp`.

What does package-version-check-mcp do?

It returns the newest stable releases for packages and tools across npm, PyPI, Go, Docker, Helm, GitHub Actions, Terraform and more. Your agent uses those numbers so it stops writing outdated pins into project files.

What does the server need to run?

The mise binary has to be on PATH for the get_supported_tools and get_latest_tool_versions tools. GITHUB_PAT is optional, but setting it keeps you clear of GitHub API rate limits.

Similar MCP servers

All MCP servers for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor