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

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

- Trust score: 94/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

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

## Channel facts

- Registry: `npm`
- Package: `specshield-mcp-server`
- Version: `1.1.1`
- 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-20.

- **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.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to specshield-io/specshield-mcp-server).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 34 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/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 848 tokens (~121/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 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).
  - 86% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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.specshield-io/specshield-mcp-server server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "specshield-io-specshield-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "specshield-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add specshield-io-specshield-mcp-server -t stdio -c npx -a -y specshield-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "specshield-io-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-09-20 (score 94, +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-18 (score 93, +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-16 (score 92, −3)

- [functional] Stability: pass → 0.80

### 2026-09-15 (score 95, +1)

- [security] Stability: 0.97 → pass

### 2026-09-13 (score 94, +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-11 (score 93, +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-09 (score 92, +1)

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

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

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

## MCP tools (6)

### `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.

### `run_governance_review` (~132 tokens)

Review an API spec against governance rules

Runs SpecShield's deterministic API governance ruleset against a single OpenAPI spec — design and policy checks that go beyond breaking changes: missing operationId, undocumented error responses, no declared security scheme, missing pagination, inconsistent versioning, unconstrained additionalProperties, and more. Returns located findings, each with a severity and a suggested fix. Paid feature (Team plan or above). Analyzes the spec only; it does NOT modify code.

Input parameters:

- `specContent` (string): Inline OpenAPI spec content (YAML or JSON).
- `specPath` (string): Path to an OpenAPI spec file.

## Diagnostics

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

## Score history

- 2026-09-20: 94
- 2026-09-19: 93
- 2026-09-18: 93
- 2026-09-17: 92
- 2026-09-16: 92
- 2026-09-15: 95
- 2026-09-14: 94
- 2026-09-13: 94
- 2026-09-12: 93
- 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: 89
- 2026-09-01: 88
- 2026-08-31: 88
- 2026-08-30: 87
- 2026-08-29: 87
- 2026-08-28: 86
- 2026-08-27: 86
- 2026-08-26: 85
- 2026-08-25: 84
- 2026-08-24: 83
- 2026-08-23: 79
- 2026-08-22: 79

## Common questions

### What is the io.github.specshield-io/specshield-mcp-server server?

io.github.specshield-io/specshield-mcp-server is listed in the public MCP registry as io.github.specshield-io/specshield-mcp-server. The API-change deploy gate for AI coding agents. Read-only breaking-change detection. This page covers its npm package (specshield-mcp-server).

### Is the io.github.specshield-io/specshield-mcp-server server safe to use?

io.github.specshield-io/specshield-mcp-server scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.specshield-io/specshield-mcp-server server expose?

io.github.specshield-io/specshield-mcp-server exposes 6 tools: is_change_safe, explain_breaking_changes, generate_migration_guide, generate_release_notes, compare_specs, run_governance_review. Their descriptions and schemas cost roughly 833 tokens of context every time the server is loaded.

### Is the io.github.specshield-io/specshield-mcp-server server still maintained?

io.github.specshield-io/specshield-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 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.specshield-io/specshield-mcp-server server under?

io.github.specshield-io/specshield-mcp-server 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/specshield-mcp-server
- Socket report: https://socket.dev/npm/package/specshield-mcp-server
- Repository: https://github.com/specshield-io/specshield-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/specshield-io-specshield-mcp-server/specshield-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/specshield-io-specshield-mcp-server/specshield-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/specshield-io-specshield-mcp-server/specshield-mcp-server