# io.github.specshield26/specshield-mcp-server (npm · specshield-mcp-server)

The API-change deploy gate for AI coding agents. Read-only breaking-change detection.

- Trust score: 79/100 (medium)
- Change this week: +27
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `specshield-mcp-server`: 79/100 (this document), [markdown](https://verifymcp.io/servers/specshield26-specshield-mcp-server/specshield-mcp-server.md), [page](https://verifymcp.io/servers/specshield26-specshield-mcp-server/specshield-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `specshield-mcp-server`
- Version: `1.0.2`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to specshield26/specshield-mcp-server).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 22 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 716 tokens (~119/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add specshield26-specshield-mcp-server -- npx -y specshield-mcp-server
```

### Codex

```bash
codex mcp add specshield26-specshield-mcp-server -- npx -y specshield-mcp-server
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add specshield26-specshield-mcp-server --command npx --arg -y --arg specshield-mcp-server
```

### Hermes

```yaml
mcp_servers:
  specshield26-specshield-mcp-server:
    command: "npx"
    args: ["-y", "specshield-mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "specshield26-specshield-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "specshield-mcp-server"
      ]
    }
  }
}
```

## 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-08-03 (score 79, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 76, +45)

- [security improvement] Install scripts: unverified → pass
- [security improvement] Provenance: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [security] The attested source repository moved: specshield26/specshield-mcp-server
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Schema quality: unverified → good
- [functional improvement] License: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 31, +5)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass

### 2026-07-31 (score 26, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 24, −28)

- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified

### 2026-07-27 (score 52)

First indexed and scored.

## MCP tools (5)

### `is_change_safe` (~183 tokens)

Is this API change safe to ship?

THE DEPLOY GATE. Analyzes whether an API spec change is safe to merge/deploy — will it break existing consumers? Returns a safeToMerge verdict, a risk level, the exact blocking reasons, and a recommended action. Use this before merging or releasing an API change to catch breaking changes before they reach your consumers. Analyzes API contract compatibility only; it does NOT modify code.

Input parameters:

- `baseSpecContent` (string): Inline base (old) spec content.
- `baseSpecPath` (string): Path to the base (old) spec file.
- `environment` (string): Optional target environment, e.g. staging or production.
- `specFormat` (string)
- `targetSpecContent` (string): Inline target (new) spec content.
- `targetSpecPath` (string): Path to the target (new) spec file.

### `explain_breaking_changes` (~117 tokens)

Explain the breaking changes

Explains what breaks in an API spec change and why, with developer impact, likely consumer impact, and suggested migration steps. Analyzes API contract compatibility only; it does NOT modify code.

Input parameters:

- `baseSpecContent` (string): Inline base (old) spec content.
- `baseSpecPath` (string): Path to the base (old) spec file.
- `targetSpecContent` (string): Inline target (new) spec content.
- `targetSpecPath` (string): Path to the target (new) spec file.

### `generate_migration_guide` (~121 tokens)

Generate a migration guide

Generates a migration guide (markdown) and safe rollout steps for the breaking changes in an API spec change. Analyzes API contract compatibility only; it does NOT modify code.

Input parameters:

- `baseSpecContent` (string): Inline base (old) spec content.
- `baseSpecPath` (string): Path to the base (old) spec file.
- `language` (string)
- `targetSpecContent` (string): Inline target (new) spec content.
- `targetSpecPath` (string): Path to the target (new) spec file.

### `generate_release_notes` (~126 tokens)

Generate release notes

Generates release notes (markdown) for an API spec change, grouped into breaking changes, additions, and other changes, tailored to an audience. Analyzes API contract compatibility only; it does NOT modify code.

Input parameters:

- `audience` (string)
- `baseSpecContent` (string): Inline base (old) spec content.
- `baseSpecPath` (string): Path to the base (old) spec file.
- `targetSpecContent` (string): Inline target (new) spec content.
- `targetSpecPath` (string): Path to the target (new) spec file.

### `compare_specs` (~154 tokens)

Compare two API specs

Compares two API specs and lists breaking changes, additions, modifications, and warnings with a risk score and compatibility summary. For a merge/deploy decision prefer is_change_safe. Analyzes API contract compatibility only; it does NOT modify code.

Input parameters:

- `baseSpecContent` (string): Inline base (old) spec content.
- `baseSpecPath` (string): Path to the base (old) spec file.
- `failOnBreaking` (boolean): If true, the header flags when any breaking change is present.
- `specFormat` (string)
- `targetSpecContent` (string): Inline target (new) spec content.
- `targetSpecPath` (string): Path to the target (new) spec file.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/specshield26-specshield-mcp-server/specshield-mcp-server#diagnostics

## Score history

- 2026-08-03: 79
- 2026-08-02: 76
- 2026-08-01: 31
- 2026-07-31: 26
- 2026-07-30: 24
- 2026-07-28: 52
- 2026-07-27: 52

## Links

- npm package: https://www.npmjs.com/package/specshield-mcp-server
- Socket report: https://socket.dev/npm/package/specshield-mcp-server
- Repository: https://github.com/specshield26/specshield-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/specshield26-specshield-mcp-server/specshield-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/specshield26-specshield-mcp-server/specshield-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/specshield26-specshield-mcp-server/specshield-mcp-server