- What it does
- Check whether a version satisfies an npm version range, or pick the highest matching version from a list, exactly as node-semver 7.8.6 does, with the range spelled out and a signed record.
- Who it is for
- Agents and their builders.
- Start in one step
- Ask your agent to call
semver_range_checkat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
Semantic Version Range Check is for coding agents and developers that update dependencies, review lockfiles or answer 'does 2.0.0-rc.1 satisfy ^1.9 || 2.x?' and need npm's exact answer, prerelease rule included. Check whether a version satisfies a version range, or find the highest version in a list that does, exactly as npm's node-semver 7.8.6 does in its default (strict) mode. Send range (npm range grammar: ^1.2.3, ~1.2, 1.x, >=1.2.0 <2, 1.2.3 - 2.3.4, a || b) and either version or versions (up to 200). Optional include_prerelease. Get back the range as node-semver normalizes it (e.g. ^1.2.3 is >=1.2.3 <2.0.0-0), satisfies true or false per version with the set that matched, whether the prerelease rule excluded it, invalid versions marked, and max_satisfying. It is one of the developer department tools LLPRO builds for the work agents do across business software (GitHub, Npm, Gitlab, Renovate). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Coding agents and developers that update dependencies, review lockfiles or answer 'does 2.0.0-rc.1 satisfy ^1.9 || 2.x?' and need npm's exact answer, prerelease rule included.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call, versions up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not use node-semver's loose mode (forms like '=1.2.3' as a version or '1.2.3beta' are invalid here, as in npm's default). Does not look up which versions exist in npm or any registry: you send the list. Does not follow other range dialects (Python PEP 440, Maven, Cargo and Composer differ, e.g. Cargo reads a bare 1.2.3 as ^1.2.3 where npm reads it as =1.2.3). Does not resolve dist-tags such as 'latest', git URLs or file paths. Up to 200 versions per call.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "semver_range_check", "arguments": {"range": "^1.2.3", "version": "1.9.0"}}}For agents
Tool semver_range_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:h7xsj7gurj4rpj63mgi6ju6lae): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): Ipxm8AlhOQI17+OpzQDeoYo7bSfWdi27S+OYcgCadH8=
For agents that search MCP registries for semver, version range, npm semver tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: Checking a version range is one step of a dependency update. Tell the Hub the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card