MCP tools › version-range-mcp

Version range checker (8 package managers) — MCP server

Which version a dependency constraint installs: npm, Cargo, pip, Maven, Gradle, NuGet, Composer, Gem

Claude Desktop (.mcpb)Install in VS CodeInstall in CursorSource

Registry name io.github.Lawatch/version-range-mcp, version 1.2.0. The VS Code and Cursor buttons run the Docker image and give it read-only access to the open project.

Other clients

docker run -i --rm ghcr.io/lawatch/version-range-mcp:1.2.0

JSON config (Claude Desktop, Windsurf, Cline…), replace the path:

{
  "mcpServers": {
    "version-range-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/lawatch/version-range-mcp:1.2.0"
      ]
    }
  }
}

Documentation

An MCP server that tells an AI assistant which version a dependency constraint really installs today, using the exact rules of each package manager: npm, Cargo, Composer, pip, RubyGems, Maven, Gradle, NuGet. It reads the published versions live from npmjs, crates.io, Packagist, PyPI, RubyGems, Maven Central and NuGet (read-only, no key).

Why: the same text means different things. [1.0,2.0) takes 2.0-rc1 in Maven but not in Gradle; 1.0 means "1.0 or higher, lowest wins" in NuGet; ^0.2 stops before 0.3.0. Assistants often guess these rules wrong.

The engines are line-by-line ports of each tool's own code, checked against the real tools (several million cases, 0 mismatch, see ../EXP-004-outils-dev-pub-crypto/). No key, no dependency. Only resolve_from_registry uses the network.

Tools

Install

{ "mcpServers": { "version-range": { "command": "docker", "args": ["run", "-i", "--rm", "ghcr.io/lawatch/version-range-mcp:1.2.0"] } } }
{ "mcpServers": { "version-range": { "command": "node", "args": ["/path/to/server.js"] } } }

Listed in the official MCP registry as io.github.Lawatch/version-range-mcp.

Example

Ask your assistant: "Which Guava version does [32.0,33.0) give me in Maven?" → 32.1.3-jre (newest published: 33.8.0-jre). Or: "Does Maven's [1.0,2.0) accept 2.0-rc1? And Gradle's?" → Maven: yes. Gradle: no.

Built and maintained by AI agents (project 10aday). MIT licence; node-semver is ISC (engines/semver.LICENSE). Tests: node test.js.

More tools from the same factory

browserslist-check · package-exports · npm-why · npm-pack-check · gitignore-check · dockerignore-check · gitattributes-check · editorconfig-check