# io.github.kyungseopk1m/semver-checks (npm · semver-checks)

Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump.

- Trust score: 92/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `semver-checks`: 92/100 (this document), [markdown](https://verifymcp.io/servers/kyungseopk1m-semver-checks/semver-checks.md), [page](https://verifymcp.io/servers/kyungseopk1m-semver-checks/semver-checks)

## Channel facts

- Registry: `npm`
- Package: `semver-checks`
- Version: `0.13.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 32 of 108 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to kyungseopk1m/semver-checks).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 27 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1151 tokens (~575/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.kyungseopk1m/semver-checks MCP server?

io.github.kyungseopk1m/semver-checks runs locally as an npm package, launched with npx -y semver-checks. 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 kyungseopk1m-semver-checks -- npx -y semver-checks
```

### Cursor

```json
{
  "mcpServers": {
    "kyungseopk1m-semver-checks": {
      "command": "npx",
      "args": [
        "-y",
        "semver-checks"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kyungseopk1m-semver-checks": {
      "command": "npx",
      "args": [
        "-y",
        "semver-checks"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add kyungseopk1m-semver-checks -- npx -y semver-checks
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kyungseopk1m-semver-checks": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "semver-checks"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kyungseopk1m-semver-checks --command npx --arg -y --arg semver-checks
```

### Hermes

```yaml
mcp_servers:
  kyungseopk1m-semver-checks:
    command: "npx"
    args: ["-y", "semver-checks"]
```

### Netclaw

```json
{
  "McpServers": {
    "kyungseopk1m-semver-checks": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "semver-checks"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add kyungseopk1m-semver-checks -t stdio -c npx -a -y semver-checks
```

### Other

```json
{
  "mcpServers": {
    "kyungseopk1m-semver-checks": {
      "command": "npx",
      "args": [
        "-y",
        "semver-checks"
      ]
    }
  }
}
```

## 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-09-20 (score 92, +1)

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

### 2026-09-19 (score 91, −2)

- [functional] Stability: pass → 0.90

### 2026-09-18 (score 93, +1)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 92, +1)

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

### 2026-09-14 (score 91, +1)

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

### 2026-09-12 (score 90, −3)

- [functional] Stability: pass → 0.80

### 2026-09-11 (score 93, +1)

- [security] Stability: 0.97 → pass

### 2026-09-09 (score 92, +1)

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

## MCP tools (2)

### `semver_compare` (~752 tokens)

Compare two versions of a TypeScript library and detect breaking API changes. Either side can be a filesystem path, a git ref, or an npm spec, so a working tree can be compared against the published release without checking anything out. Returns the recommended SemVer bump (major/minor/patch) and a list of changes. Each change carries a confidence: "proven" (a structurally confident break — gate on these) or "heuristic" (a conservative major the tool could not prove safe — surface for review). summary.majorProven / majorReview split the major count accordingly. Pass "declared" to have the tool grade the bump the release writes down instead of just recommending one. The "gate" field answers what each CLI gate would do with this report, which is what its exit code carries: "strict" fails only on a proven break and is the one safe to leave on every build, while "strictReview" also fails on a major the analyzer could not prove. They are not two strengths of the same check. A passing "strict" is not a clean bill of health, because a real break it could not prove stays review-only; "green means safe" is a claim only "strictReview" can make. Report both rather than reading "strict": "pass" as "nothing broke". Passing "declared" changes the question both gates answer: the release is then graded against the bump it writes down, so a major it already declares passes both.

Input parameters:

- `declared` (string): The bump this release declares, or "auto" to read it from .changeset/*.md and then the two package.json versions. Adds a "declaration" verdict to the report: "mismatch" when a proven break outranks t…
- `entry`: Entry file relative to project root (e.g. "src/index.ts"). Pass an array or a comma-separated string for a package with several entry points. Auto-detected from package.json if omitted.
- `installDeps` (boolean): Install dependencies before analysis (needed for local paths without node_modules)
- `maxChanges` (integer): How many changes to include (default 50). They are ordered proven breaks first, then additions, then review-only ones, so the cap drops the least actionable end. "summary" always counts every change,…
- `new` (string): New version: a filesystem path, a git ref, or an npm spec. Defaults to current directory.
- `newAs` (string): Force "new" to be treated as a filesystem path, a git ref, or an npm spec. "ref" is an accepted spelling of "git".
- `old` (string, required): Old version: a filesystem path, a git ref (tag, branch, commit SHA), or an npm spec. A "name@version" that is not an existing path is read as npm (e.g. "lodash@4.17.21", "lodash@latest"); prefix with…
- `oldAs` (string): Force "old" to be treated as a filesystem path, a git ref, or an npm spec. "ref" is an accepted spelling of "git". Only needed when auto-detection would read the input as the wrong kind, which is wha…

### `semver_snapshot` (~399 tokens)

Extract the public API surface of a TypeScript project as a structured JSON snapshot, keyed by export subpath. Useful for inspecting what a library exports. The source can be a filesystem path, a git ref, or an npm spec, the same three forms semver_compare takes. Returns each symbol's name and kind by default; pass "detail" for full type shapes, which is far larger.

Input parameters:

- `detail` (boolean): Include each symbol's full type shape instead of just its kind. A shape runs a median of about 370 bytes and a wide interface tens of kilobytes, against about 35 for a name and a kind, so a large pac…
- `entry`: Entry file relative to project root (e.g. "src/index.ts"). Pass an array or a comma-separated string for a package with several entry points.
- `installDeps` (boolean): Install dependencies before analysis
- `maxBytes` (integer): Byte budget for the symbols in the response (default 40000). Symbols are included while it lasts, and an "omitted" field then reports how many were left out along with the total. No symbol is exempt:…
- `path` (string): Project source: a filesystem path, a git ref, or an npm spec such as "lodash@4.17.21". Defaults to current directory.
- `pathAs` (string): Force "path" to be treated as a filesystem path, a git ref, or an npm spec. "ref" is an accepted spelling of "git". Only needed when auto-detection would read the input as the wrong kind.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/kyungseopk1m-semver-checks/semver-checks#diagnostics

## Score history

- 2026-09-21: 92
- 2026-09-20: 92
- 2026-09-19: 91
- 2026-09-18: 93
- 2026-09-17: 92
- 2026-09-16: 92
- 2026-09-15: 91
- 2026-09-14: 91
- 2026-09-13: 90
- 2026-09-12: 90
- 2026-09-11: 93
- 2026-09-10: 92
- 2026-09-09: 92
- 2026-09-08: 91
- 2026-09-07: 91
- 2026-09-06: 90
- 2026-09-05: 90
- 2026-09-04: 89
- 2026-09-03: 89
- 2026-09-02: 88
- 2026-09-01: 88
- 2026-08-31: 87
- 2026-08-30: 87
- 2026-08-29: 87
- 2026-08-28: 86
- 2026-08-27: 86
- 2026-08-26: 85
- 2026-08-25: 83
- 2026-08-24: 83
- 2026-08-23: 86

## Common questions

### What is the io.github.kyungseopk1m/semver-checks MCP server?

io.github.kyungseopk1m/semver-checks is an MCP server listed in the public MCP registry as io.github.kyungseopk1m/semver-checks. Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump. This page covers its npm package (semver-checks).

### Is the io.github.kyungseopk1m/semver-checks MCP server safe to use?

io.github.kyungseopk1m/semver-checks scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.kyungseopk1m/semver-checks MCP server expose?

io.github.kyungseopk1m/semver-checks exposes 2 tools: semver_compare, semver_snapshot. Their descriptions and schemas cost roughly 1,151 tokens of context every time the server is loaded.

### Is the io.github.kyungseopk1m/semver-checks MCP server still maintained?

io.github.kyungseopk1m/semver-checks is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.kyungseopk1m/semver-checks MCP server under?

io.github.kyungseopk1m/semver-checks declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/semver-checks
- Socket report: https://socket.dev/npm/package/semver-checks
- Repository: https://github.com/kyungseopk1m/semver-checks
- Changelog RSS feed: https://verifymcp.io/servers/kyungseopk1m-semver-checks/semver-checks.xml
- Changelog JSON feed: https://verifymcp.io/servers/kyungseopk1m-semver-checks/semver-checks.json
- HTML version of this page: https://verifymcp.io/servers/kyungseopk1m-semver-checks/semver-checks