# SemverKit (remote · semverkit.mike-tusa.workers.dev)

Semver parse, compare, npm range checks, max-satisfying and version bumps (node-semver compatible).

- Trust score: 72/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `semverkit.mike-tusa.workers.dev`: 72/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-mike-tusa-semverkit-semverkit/semverkit.md), [page](https://verifymcp.io/servers/dev-workers-mike-tusa-semverkit-semverkit/semverkit)

## Channel facts

- Endpoint: `https://semverkit.mike-tusa.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1066 tokens (~213/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the SemverKit MCP server?

SemverKit is a hosted endpoint at https://semverkit.mike-tusa.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-workers-mike-tusa-semverkit-semverkit 'https://semverkit.mike-tusa.workers.dev/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "dev-workers-mike-tusa-semverkit-semverkit": {
      "type": "http",
      "url": "https://semverkit.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-mike-tusa-semverkit-semverkit]
url = "https://semverkit.mike-tusa.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-mike-tusa-semverkit-semverkit": {
      "type": "remote",
      "url": "https://semverkit.mike-tusa.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-mike-tusa-semverkit-semverkit --url 'https://semverkit.mike-tusa.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-mike-tusa-semverkit-semverkit:
    url: "https://semverkit.mike-tusa.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-mike-tusa-semverkit-semverkit": {
      "Transport": "http",
      "Url": "https://semverkit.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-mike-tusa-semverkit-semverkit -t streamable-http -u 'https://semverkit.mike-tusa.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-mike-tusa-semverkit-semverkit": {
      "type": "http",
      "url": "https://semverkit.mike-tusa.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-05 (score 72, +1)

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

### 2026-11-03 (score 71, +1)

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

### 2026-11-01 (score 70, +1)

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

### 2026-10-30 (score 69, +1)

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

### 2026-10-27 (score 68, +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-10-25 (score 67, +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-10-23 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 65)

First indexed and scored.

## MCP tools (5)

### `parse_version` (~101 tokens)

Parse and validate a semantic version

Validate a version against SemVer 2.0.0 and split it into major, minor, patch, prerelease identifiers and build metadata, with isPrerelease/isStable flags. Read-only. Same engine as GET /api/parse.

Input parameters:

- `version` (string, required): Version: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5".

Output parameters:

- `apiVersion` (string)
- `build` (array)
- `input` (string)
- `isPrerelease` (boolean)
- `isStable` (boolean)
- `major` (integer)
- `minor` (integer)
- `notes` (array)
- `patch` (integer)
- `prerelease` (array)
- `version` (string)

### `compare_versions` (~176 tokens)

Compare two semantic versions

Compare a and b by SemVer precedence (prereleases sort before the release, build metadata ignored). Returns -1, 0 or 1 and the change type from the lower to the higher version (major, minor, patch, premajor, preminor, prepatch, prerelease) exactly like semver.diff. Read-only. Same engine as GET /api/compare.

Input parameters:

- `a` (string, required): First version: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5".
- `b` (string, required): Second version: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5".

Output parameters:

- `a` (string)
- `apiVersion` (string)
- `b` (string)
- `buildDiffers` (boolean)
- `diff` (string|null)
- `notes` (array)
- `relation` (string)
- `result` (integer)

### `check_range` (~239 tokens)

Check a version against an npm 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.

Input parameters:

- `includePrerelease` (boolean): Let prereleases match any range they fall inside (npm includePrerelease). Default false (npm behaviour).
- `range` (string, required): npm-style range, e.g. "^1.2.0", "~1.4", ">=1.0.0 <2.0.0", "1.2.3 - 2.x", "1.x || >=3.0.0-beta.1".
- `version` (string, required): Version to test: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5".

Output parameters:

- `apiVersion` (string)
- `includePrerelease` (boolean)
- `normalized` (string)
- `notes` (array)
- `range` (string)
- `satisfies` (boolean)
- `version` (string)

### `resolve_versions` (~183 tokens)

Sort versions and resolve a range

Sort 1 to 200 versions by SemVer precedence (duplicates removed, invalid ones listed separately) and, if a range is given, return the matching versions plus maxSatisfying / minSatisfying (what npm would install from that list) and the latest stable version. Read-only. Same engine as GET /api/resolve.

Input parameters:

- `includePrerelease` (boolean): Let prereleases match any range they fall inside (npm includePrerelease). Default false (npm behaviour).
- `range` (string): npm-style range, e.g. "^1.2.0", "~1.4", ">=1.0.0 <2.0.0", "1.2.3 - 2.x", "1.x || >=3.0.0-beta.1".
- `versions` (array, required): 1 to 200 versions.

Output parameters:

- `apiVersion` (string)
- `count` (integer)
- `duplicatesRemoved` (integer)
- `includePrerelease` (boolean)
- `invalid` (array)
- `latestStable` (string|null)
- `matching` (array)
- `maxSatisfying` (string|null)
- `minSatisfying` (string|null)
- `normalized` (string|null)
- `range` (string|null)
- `sorted` (array)

### `bump_version` (~156 tokens)

Compute the next 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.

Input parameters:

- `preid` (string): Prerelease identifier, e.g. "beta" (for pre* and prerelease).
- `release` (string): Release type.
- `version` (string, required): Current version: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5".

Output parameters:

- `apiVersion` (string)
- `from` (string)
- `notes` (array)
- `preid` (string|null)
- `release` (string)
- `version` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-mike-tusa-semverkit-semverkit/semverkit#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 67
- 2026-10-25: 67
- 2026-10-24: 66
- 2026-10-23: 66
- 2026-10-22: 65

## Common questions

### What is the SemverKit MCP server?

SemverKit is an MCP server listed in the public MCP registry as dev.workers.mike-tusa.semverkit/semverkit. Semver parse, compare, npm range checks, max-satisfying and version bumps (node-semver compatible). This page covers its hosted endpoint (https://semverkit.mike-tusa.workers.dev/mcp).

### Is the SemverKit MCP server safe to use?

SemverKit scores 72 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 SemverKit MCP server expose?

SemverKit exposes 5 tools: parse_version, compare_versions, check_range, resolve_versions, bump_version. Their descriptions and schemas cost roughly 855 tokens of context every time the server is loaded.

### Does the SemverKit MCP server require authentication?

No. We connected to SemverKit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SemverKit MCP server still maintained?

SemverKit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://semverkit.mike-tusa.workers.dev/mcp
- Website: https://semverkit.mike-tusa.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-mike-tusa-semverkit-semverkit/semverkit.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-mike-tusa-semverkit-semverkit/semverkit.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-mike-tusa-semverkit-semverkit/semverkit