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.
Supported ecosystems/tools:
1) Developer ecosystems: NPM, PyPI, NuGet, Maven/Gradle, Go, PHP, Ruby, Rust, Swift, Dart
2) DevOps ecosystems:
- Docker: Docker container images from Docker registries
- Helm: Helm charts from ChartMuseum repositories and OCI registries
- GitHub Actions: Actions hosted on GitHub.com, returning their current version, their inputs and outputs, and (optionally) their entire README with usage examples
- Terraform Providers and Modules: Providers & Modules from Terraform Registry, OpenTofu Registry, or custom registries
- Various tools such as kubectl, terraform, gradle, maven, etc. (as long as they are supported by mise-en-place)
There is a free-for-all hosted version on https://package-version-check-mcp.onrender.com/mcp, and you can run it with Docker or uv (uvx).
This MCP is certainly not the first one to tackle the "outdated dependency" problem. However, I feel that it has various advantages over other MCPs:
- It offers (far) better ecosystem coverage than other MCPs
- There is full test coverage, with automated dependency updates (powered by Renovate) and regular, automated release builds. In contrast, other projects are often vibe-coded, have poor (or no) tests, and are already abandoned
- This MCP uses a minimal Docker/OCI image, hardened for security. SBOMs you generate with tools like Trivy are known to be correct, and the image is signed with Cosign (which allows you to verify its authenticity in case you want to self-host the MCP)
Let me know what you think.