SemverKit
REMOTE · SEMVERKIT.MIKE-TUSA.WORKERS.DEV
Semver parse, compare, npm range checks, max-satisfying and version bumps (node-semver compatible).
Available components
Last scanned (23 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://semverkit.mike-tusa.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mike-tusa.workers.dev | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f05aa95d8943eeed0e4e86dd1f6f1e02 |
| SANs: mike-tusa.workers.dev, *.mike-tusa.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of semverkit.mike-tusa.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://semverkit.mike-tusa.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://semverkit.mike-tusa.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bump_version Compute the next version ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| preid | string | – | Prerelease identifier, e.g. "beta" (for pre* and prerelease). |
| release | string | – | Release type. |
| version | string | yes | Current version: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5". |
| Name | Type | Req | Description |
|---|---|---|---|
| apiVersion | string | yes | – |
| from | string | yes | – |
| notes | array | – | – |
| preid | string|null | – | – |
| release | string | – | – |
| version | string | yes | – |
No examples provided.
check_range Check a version against an npm range ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| includePrerelease | boolean | – | Let prereleases match any range they fall inside (npm includePrerelease). Default false (npm behaviour). |
| range | string | yes | 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 | yes | Version to test: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5". |
| Name | Type | Req | Description |
|---|---|---|---|
| apiVersion | string | yes | – |
| includePrerelease | boolean | – | – |
| normalized | string | yes | – |
| notes | array | – | – |
| range | string | – | – |
| satisfies | boolean | yes | – |
| version | string | – | – |
No examples provided.
compare_versions Compare two semantic versions ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | First version: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5". |
| b | string | yes | Second version: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5". |
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | – | – |
| apiVersion | string | yes | – |
| b | string | – | – |
| buildDiffers | boolean | – | – |
| diff | string|null | yes | – |
| notes | array | – | – |
| relation | string | yes | – |
| result | integer | yes | – |
No examples provided.
parse_version Parse and validate a semantic version ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | yes | Version: a semantic version such as "1.4.2", "v2.0.0" or "3.0.0-rc.1+build.5". |
| Name | Type | Req | Description |
|---|---|---|---|
| apiVersion | string | yes | – |
| build | array | – | – |
| input | string | – | – |
| isPrerelease | boolean | yes | – |
| isStable | boolean | – | – |
| major | integer | yes | – |
| minor | integer | yes | – |
| notes | array | – | – |
| patch | integer | yes | – |
| prerelease | array | – | – |
| version | string | yes | – |
No examples provided.
resolve_versions Sort versions and resolve a range ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 1 to 200 versions. |
| Name | Type | Req | Description |
|---|---|---|---|
| apiVersion | string | yes | – |
| count | integer | – | – |
| duplicatesRemoved | integer | – | – |
| includePrerelease | boolean | – | – |
| invalid | array | – | – |
| latestStable | string|null | – | – |
| matching | array | yes | – |
| maxSatisfying | string|null | yes | – |
| minSatisfying | string|null | – | – |
| normalized | string|null | – | – |
| range | string|null | – | – |
| sorted | array | yes | – |
No examples provided.
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.
remote · semverkit.mike-tusa.workers.dev
claude mcp add --transport http dev-workers-mike-tusa-semverkit-semverkit 'https://semverkit.mike-tusa.workers.dev/mcp'
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 71 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.