# Version range checker (8 package managers) (mcpb · version-range-mcp-1.2.0.mcpb)

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

- Trust score: 43/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `version-range-mcp-1.2.0.mcpb`: 43/100 (this document), [markdown](https://verifymcp.io/servers/lawatch-version-range-mcp/version-range-mcp.md), [page](https://verifymcp.io/servers/lawatch-version-range-mcp/version-range-mcp)
- oci · `ghcr.io/lawatch/version-range-mcp`: 44/100, [markdown](https://verifymcp.io/servers/lawatch-version-range-mcp/ghcr-io-lawatch-version-range-mcp.md), [page](https://verifymcp.io/servers/lawatch-version-range-mcp/ghcr-io-lawatch-version-range-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Lawatch/10aday/releases/download/exp007-v1.2.0/version-range-mcp-1.2.0.mcpb`
- Transport: `stdio`
- SHA-256: `d96daa6bfacd580a37db88493910cd2b177cae66e4dc98c93dfeda79f1e3e20a`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 651 tokens (~162/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Version range checker (8 package managers) MCP server?

Version range checker (8 package managers) ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, d96daa6bfacd580a37db88493910cd2b177cae66e4dc98c93dfeda79f1e3e20a; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Lawatch/10aday/releases/download/exp007-v1.2.0/version-range-mcp-1.2.0.mcpb`
- SHA-256: `d96daa6bfacd580a37db88493910cd2b177cae66e4dc98c93dfeda79f1e3e20a`

### Verify on macOS / Linux

```bash
echo "d96daa6bfacd580a37db88493910cd2b177cae66e4dc98c93dfeda79f1e3e20a  version-range-mcp-1.2.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\version-range-mcp-1.2.0.mcpb).Hash -eq "d96daa6bfacd580a37db88493910cd2b177cae66e4dc98c93dfeda79f1e3e20a"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 40, +1)

- [functional regression] Schema quality: 455 → 651
- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 39)

First indexed and scored.

## MCP tools (4)

### `resolve_from_registry` (~182 tokens)

Look up a real package on its public registry (npmjs, crates.io, Packagist, PyPI, RubyGems, Maven Central, NuGet) and tell which published version a constraint installs today, with the exact rules of that package manager. Use it before writing or changing a dependency line. For maven and gradle, package is "groupId:artifactId".

Input parameters:

- `constraint` (string, required): Constraint as written in the manifest, e.g. "^4.18", "~=2.31", "[32.0,33.0)", "13.*".
- `ecosystem` (string, required): Package manager whose rules apply.
- `package` (string, required): Package name, e.g. "express", "serde", "laravel/framework", "requests", "rails", "com.google.guava:guava", "Newtonsoft.Json".

### `check_version_constraint` (~175 tokens)

Tell which versions a dependency constraint accepts, and which one gets installed, using the exact rules of one package manager (npm, cargo, composer, pip, rubygems, maven, gradle, nuget). Pre-releases, carets, tildes, wildcards, Maven/NuGet interval ranges and Gradle "+" selectors behave as in the real tool.

Input parameters:

- `constraint` (string, required): Constraint as written in the manifest, e.g. "^1.2", "~=3.10", "[1.0,2.0)", "1.+".
- `ecosystem` (string, required): Package manager whose rules apply.
- `versions` (array, required): Published versions to test, e.g. ["1.2.0","1.3.0-beta.1","2.0.0"].

### `compare_across_ecosystems` (~122 tokens)

Evaluate the SAME constraint string in every package manager that accepts it and list where they disagree (e.g. "^0.2" or "1.0" or "[1.0,2.0)" mean different things in npm, Cargo, Composer, Maven, NuGet...). Useful when porting a dependency between languages.

Input parameters:

- `constraint` (string, required)
- `versions` (array, required): Published versions to test, e.g. ["1.2.0","1.3.0-beta.1","2.0.0"].

### `sort_versions` (~125 tokens)

Sort version strings in the order a given package manager uses (e.g. Maven puts 1.0-alpha < 1.0 < 1.0-sp; pip puts 1.0.dev0 < 1.0a1 < 1.0 < 1.0.post1). Invalid versions are returned separately.

Input parameters:

- `ecosystem` (string, required): Package manager whose rules apply.
- `versions` (array, required): Published versions to test, e.g. ["1.2.0","1.3.0-beta.1","2.0.0"].

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/lawatch-version-range-mcp/version-range-mcp#diagnostics

## Score history

- 2026-11-21: 43
- 2026-11-20: 43
- 2026-11-19: 42
- 2026-11-18: 42
- 2026-11-17: 41
- 2026-11-16: 41
- 2026-11-15: 40
- 2026-11-14: 40
- 2026-11-13: 39

## Common questions

### What is the Version range checker (8 package managers) MCP server?

Version range checker (8 package managers) is an MCP server listed in the public MCP registry as io.github.Lawatch/version-range-mcp. Which version a dependency constraint installs: npm, Cargo, pip, Maven, Gradle, NuGet, Composer, Gem. This page covers its MCPB bundle (https://github.com/Lawatch/10aday/releases/download/exp007-v1.2.0/version-range-mcp-1.2.0.mcpb).

### Is the Version range checker (8 package managers) MCP server safe to use?

Version range checker (8 package managers) scores 43 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Version range checker (8 package managers) MCP server expose?

Version range checker (8 package managers) exposes 4 tools: resolve_from_registry, check_version_constraint, compare_across_ecosystems, sort_versions. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.

### What licence is the Version range checker (8 package managers) MCP server under?

Version range checker (8 package managers) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Version range checker (8 package managers) MCP server?

VerifyMCP ran 12 checks on Version range checker (8 package managers), covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Version range checker (8 package managers): Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/Lawatch/10aday
- Changelog RSS feed: https://verifymcp.io/servers/lawatch-version-range-mcp/version-range-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/lawatch-version-range-mcp/version-range-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lawatch-version-range-mcp/version-range-mcp.json
- HTML version of this page: https://verifymcp.io/servers/lawatch-version-range-mcp/version-range-mcp
