mcp-package-version

MCP.Pizza Chef: sammcj

Eleven tools look up the current release of a library across npm, PyPI, Maven, Gradle, Go, Swift, Docker Hub, GitHub Container Registry and GitHub Actions, so your assistant stops suggesting versions from two years ago. The two Amazon Bedrock model tools are the exception: they hand back a list written into the code and frozen at Claude 3 and Llama 2, not anything live. The project was archived in January 2026, and its author says the work has moved into his mcp-devtools server.

Archived · The author made this repository read-only on GitHub.
Coding

Use This MCP server To

Check whether the packages in my project are out of date Find the current version of a Python library Look up the newest tag for a container image See which GitHub Actions versions I should pin to Get the latest release of a Java or Go library

README

Package Version MCP Server

smithery badge

An MCP server that provides tools for checking latest stable package versions from multiple package registries:

  • npm (Node.js/JavaScript)
  • PyPI (Python)
  • Maven Central (Java)
  • Go Proxy (Go)
  • Swift Packages (Swift)
  • AWS Bedrock (AI Models)
  • Docker Hub (Container Images)
  • GitHub Container Registry (Container Images)
  • GitHub Actions

This server helps LLMs ensure they're recommending up-to-date package versions when writing code.

IMPORTANT: I'm slowly moving across this tool to a component of my mcp-devtools server

https://github.com/sammcj/mcp-package-version MCP server

Screenshot

tooling with and without mcp-package-version

Installation

Requirements:

Using go install (Recommended for MCP Client Setup):

go install github.com/sammcj/mcp-package-version/v2@HEAD

Then setup your client to use the MCP server. Assuming you've installed the binary with go install github.com/sammcj/mcp-package-version/v2@HEAD and your $GOPATH is /Users/sammcj/go/bin, you can provide the full path to the binary:

{
  "mcpServers": {
    "package-version": {
      "command": "/Users/sammcj/go/bin/mcp-package-version"
    }
  }
}
  • For the Cline VSCode Extension this will be ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
  • For Claude Desktop ~/Library/Application\ Support/Claude/claude_desktop_config.json
  • For GoMCP ~/.config/gomcp/config.yaml

Other Installation Methods

Or clone the repository and build it:

mcp-package-version FAQ

Is this still maintained?
No. The repository was archived in January 2026 and is now read-only. The author's own note says he is folding this work into his mcp-devtools project, which is the replacement he points people to.
Does it need an access key?
No. It reads public package listings with no sign-up and no credential of any kind in the code. The flip side is that the GitHub Actions and container lookups run as an anonymous visitor, so checking a long list in one go can start hitting GitHub's limit for anonymous requests.
Does the Amazon Bedrock model checker really report the newest models?
No, and this is worth knowing before you rely on it. Those two tools return a fixed list of nine models typed into the source file — the newest being Claude 3 from early 2024 — next to a comment saying the live lookup was never built. Everything else does query the real registries.
Which apps does it work in?
Claude Desktop, VS Code with the Cline extension, GoMCP, and anything else that can point at a program on your machine or at a local web address if you run the container version.
How hard is the setup?
This one is for developers. You either install Go and build the program yourself, then give your assistant the full path to it, or run the container image and point your assistant at a local address. There is no ready-made installer.
Can I use this to find out if my project's dependencies are stale?
Yes. Hand it your list of packages and it comes back with the current published version of each, and you can tell it to stay inside a particular major version if you are not ready to jump.
Can it change my project files?
No. Every tool is a lookup. It reports versions and never writes to your files, so any actual upgrade is still yours to make and review.