SemverKit

{
  "mcpServers": {
    "dev.workers.mike-tusa.semverkit/semverkit": {
      "url": "https://semverkit.mike-tusa.workers.dev/mcp"
    }
  }
}

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

5 shown · authentication unknown

• Compute the next version

  bump_version

  Compute the next version for a release type (major, minor, patch, premajor, preminor, prepatch, prerelease, release), with an optional prerelease id such as alpha, beta or rc, exactly like npm version / semver.inc. Read-only: nothing is published. Same engine as GET /api/bump.

  Schema valid · SHA-256 86959fc2aadd…

  View input schema

  {
    "type": "object",
    "properties": {
      "version": {
        "type": "string",
        "minLength": 1,
        "maxLength": 256,
        "description": "Current version: a semantic version such as \"1.4.2\", \"v2.0.0\" or \"3.0.0-rc.1+build.5\"."
      },
      "release": {
        "type": "string",
        "enum": [
          "major",
          "minor",
          "patch",
          "premajor",
          "preminor",
          "prepatch",
          "prerelease",
          "release"
        ],
        "default": "patch",
        "description": "Release type."
      },
      "preid": {
        "type": "string",
        "minLength": 1,
        "maxLength": 64,
        "description": "Prerelease identifier, e.g. \"beta\" (for pre* and prerelease)."
      }
    },
    "required": [
      "version"
    ],
    "additionalProperties": false
  }

• Check a version against an npm range

  check_range

  Does a version satisfy an npm-style range (^, ~, x-ranges, hyphen ranges, comparators, || alternatives)? Returns the answer and the range desugared into plain comparators (e.g. ^0.2.3 → >=0.2.3 <0.3.0-0), with a note when npm's prerelease rule is why it fails. Read-only. Same engine as GET /api/satisfies.

  Schema valid · SHA-256 69cf5b82f7b9…

  View input schema