Package Version Check queries registries across multiple ecosystems to return current, up-to-date versions of dependencies and development tools. Key features: - Multi-ecosystem package lookups: NPM, PyPI, NuGet, Maven/Gradle, Go modules, PHP (Packagist), RubyGems, Rust crates, Swift packages, and Dart packages - DevOps registry support: Docker images, Helm charts, GitHub Actions (including inputs, outputs, and usage documentation), Terraform providers and modules - Development runtime and tool versions: Python, Node.js, .NET, kubectl, Terraform, Gradle, and ~1000 other tools via mise-en-place integration - Helps AI coding agents avoid generating code with stale dependency versions by providing real-time registry data

package-version-check-mcp

A MCP server that returns the latest stable versions of packages you use as dependencies in a variety of ecosystems, such as Python, NPM, Go, or GitHub Actions.

It also supports looking up the latest versions of almost 1000 tools, such as development runtimes like python, node, dotnet, development tools like gradle, and various DevOps tools like kubectl or terraform, via the mise-en-place tool.

Why do I need this?

Whenever an AI coding agents generates files that pin dependency versions, they insert outdated versions because their training happened weeks or months ago, and new dependency versions have been released since then. As a developer, it is annoying having to manually fix these outdated versions.

This MCP fixes this problem. Use it together with an MCP such as Context7 to avoid that your AI agent produces outdated code.

Features

Supported ecosystems / tools:

Usage

Adding the MCP to Your Agent

There are three ways to make this MCP available to your AI coding agent:

#### Option 1: Use the Hosted Service (Easiest)

Point your agent to the free hosted service:

https://package-version-check-mcp.onrender.com/mcp

This is the quickest way to get started. Note that the hosted service may have rate limits from the underlying package registries.

#### Option 2: Run with uvx (for local use)

Use uvx to run the MCP server locally:

uvx package-version-check-mcp --mode=stdio

This automatically installs and runs the latest version from PyPI.

Requirements:

Optional but recommended: Set the GITHUB_PAT environment variable to a GitHub Personal Access Token (no scopes required) to avoid GitHub API rate limits.

#### Option 3: Run with Docker (for local use)

Use the pre-built Docker image:

docker run --pull=always --rm -i ghcr.io/mshekow/package-version-check-mcp:latest --mode=stdio

Optional but recommended: Pass the GITHUB_PAT environment variable using -e GITHUB_PAT=your_token_here to avoid GitHub API rate limits.

Caching Configuration

To improve performance and reduce API calls to package registries, you can enable caching:

The cache is an in-memory TTL (Time-To-Live) cache. It resets when the MCP server restarts.

Configuring Your Agent

Once you've added the MCP server, you need to:

1. Enable the MCP tools in your agent's configuration. The available tools are documented below

2. Nudge the agent to use the MCP in your prompts. Most LLMs don't automatically invoke this MCP's tools without explicit guidance. Include instructions like: - "Use MCP to get latest versions" - "Check the latest package versions using the MCP tools" - "Use get_latest_package_versions to find the current version"

In case you forgot to add this prompt and your agent generated code with _outdated_ versions, you can just ask your agent to update the versions afterwards (e.g., "Update the dependencies you just added to the latest version via MCP").

Available Tools

#### get_latest_package_versions

Fetches the latest versions of packages from various ecosystems.

Input: