Skip to content
BEAD

SemVer Compare

Compare two SemVer 2.0.0 versions — get direction (upgrade / downgrade / equal) and the diff kind.

Developer
A → B
upgrademajor
1.4.2→2.0.0-rc.1
</>Use this tool programmaticallycurl · JavaScript · MCP

Same tool, callable from any HTTP client or from Claude (via MCP). Anonymous: 100 req/day per IP. Sign up for 1,000 req/day.

curl
curl https://api.b-e-a-d.com/tools/semver-compare/run \
  -H "Content-Type: application/json" \
  -d '{
  "a": "a",
  "b": "a"
}'
JavaScript (fetch)
const res = await fetch("https://api.b-e-a-d.com/tools/semver-compare/run", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "a": "a",
  "b": "a"
}),
});
const data = await res.json();
console.log(data.result);
MCP (Claude Desktop / Claude Code)
# In Claude Desktop / Claude Code, add to your MCP config:
{
  "mcpServers": {
    "bead": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.b-e-a-d.com"]
    }
  }
}

# Then ask Claude to call:
mcp__bead__bead_semver_compare

Full reference: developer docs · OpenAPI spec

Comparison rules

Strictly per SemVer 2.0.0: major / minor / patch as numbers, then prerelease identifiers compared part-by-part (numeric vs alphanumeric). Build metadata is ignored.

What you get

  • Direction (up / down / equal)
  • Diff kind (major / minor / patch / prerelease / build / none)
  • Per-component breakdown

You might also like

Used in these workflows