- What it does
- Order versions by SemVer 2.0.0 precedence including pre-release tags, find the highest, and see which strings are not valid SemVer and why, with a signed record.
- Who it is for
- Agents and their builders.
- Start in one step
- Ask your agent to call
semver_compareat 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 Compare is for agents and developers that pick the newest release from a list of tags, gate a release, or check that a version string is real SemVer before publishing. Order version strings by Semantic Versioning 2.0.0 precedence, pre-release tags included, and find the highest. Send versions, a list of up to 100 strings such as ['1.10.0', '1.9.0', '1.0.0-rc.1']. Get back the valid versions from lowest to highest (with each one's position in your list), the highest and lowest, versions that tie (they differ only in build metadata), and every string that is not valid SemVer 2.0.0 with the reason (a leading v, a leading zero, a missing part, an empty pre-release field ...). Use it for 'which release is newest' and to check that a tag is a real SemVer. It is one of the developer department tools LLPRO builds for the work agents do across business software (GitHub, Npm, Pypi, Cargo, Docker). 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
- Agents and developers that pick the newest release from a list of tags, gate a release, or check that a version string is real SemVer before publishing.
- 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 100 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 accept or repair near-versions: v1.2.3, 1.2, 1.2.3.4, 01.2.3 and similar are reported as invalid, not guessed (other tools such as npm's node-semver have a loose mode; this one is strict SemVer 2.0.0). Does not read version ranges (^1.2, ~1.2, >=1) or other schemes (calendar versions, Debian, Python PEP 440 and Maven orders differ: 1.0.0-rc.1 is not PEP 440's 1.0.0rc1). Does not check that a version exists on any registry. Version numbers are compared as whole numbers of any length (no 2^53 cap). Limits: 100 versions, 256 characters each. No personal data: strings containing @ or a scheme such as https:// are refused.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "semver_compare", "arguments": {"versions": ["1.0.0", "1.0.0-rc.1", "1.0.0-beta.11", "1.0.0-alpha", "1.0.0-beta", "1.0.0-alpha.beta", "1.0.0-beta.2", "1.0.0-alpha.1"]}}}For agents
Tool semver_compare on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:65lshmbympbmh3rc5kqbbbplwi): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): HYwr2Gtp5INmtW+udiE1oXvGAr1q5WDDQaCeVvhdhxw=
For agents that search MCP registries for semver, semantic versioning, version compare tools (listed in MCP registries, served by the LLPRO 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 LLPRO: Picking a version is one step of shipping or updating software. Tell LLPRO the whole job; it routes you to the right signed tools (semver range check, JSON Schema validate).
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card