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.
Available components
Last scanned (3 hours ago)
Scores higher than 93% of npm servers
Category Testing and QA
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to specshield-io/specshield-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 80 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
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 5 Nov 2026 · Analysed npm/specshield-mcp-server@1.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | specshield-io/specshield-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/specshield-io/specshield-mcp-server/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2489819962 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b3a169808d54ef517fe84e0043cce5ed5b355e5636e6f965397cadcb0413e4d24f411542f73bcc42812b93ceaac3fd06c420db0c251913a679ade4f25 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compare_specs Compare two API specs ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
explain_breaking_changes Explain the breaking changes ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
generate_migration_guide Generate a migration guide ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
generate_release_notes Generate release notes ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
is_change_safe Is this API change safe to ship? ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
run_governance_review Review an API spec against governance rules ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| specContent | string | – | Inline OpenAPI spec content (YAML or JSON). |
| specPath | string | – | Path to an OpenAPI spec file. |
No output schema declared.
No examples provided.
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.
npm · specshield-mcp-server
claude mcp add specshield-io-specshield-mcp-server -- npx -y specshield-mcp-server
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 90 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 5 November 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.