Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.specshield26/specshield-mcp-server

NPM · SPECSHIELD-MCP-SERVER · SCANNED AUG 3

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

Available components

npm · specshield-mcp-server 79
+27 this week 79 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to specshield26/specshield-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 22 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
  • 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 716 tokens (~119/item across 6 items; 5 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · specshield-mcp-server

# add to Claude Code
claude mcp add specshield26-specshield-mcp-server -- npx -y specshield-mcp-server
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add specshield26-specshield-mcp-server --command npx --arg -y --arg specshield-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  specshield26-specshield-mcp-server:
    command: "npx"
    args: ["-y", "specshield-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "specshield26-specshield-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "specshield-mcp-server"
      ]
    }
  }
}
Changelog

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 Aug 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 2 Aug 26 +45
    • Install scripts: unverified → pass ▲ security
    • Provenance: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • 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 security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Maintenance: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Schema quality: unverified → good ▲ functional
    • License: unverified → pass ▲ functional
    • Licence: MIT functional
  • 1 Aug 26 +5
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass ▲ functional
  • 31 Jul 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −28
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
  • 27 Jul 26 52

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
specshield26/specshield-mcp-server
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/specshield26/specshield-mcp-server/.github/workflows/publish.yml@refs/heads/main
Rekor log index:
2088672713
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:412eae538710ca1498104cc4573ae77db25ef750d51117e88f4b59b03be91b2dfd4f0295955be30943d792913e70f4c6d751d42d4cc0670d617d04b6c
Discovery method:
attestation_endpoint
Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~701 tokens

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.

Tool Tokens
compare_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.

NameTypeReqDescription
baseSpecContentstring—Inline base (old) spec content.
baseSpecPathstring—Path to the base (old) spec file.
failOnBreakingboolean—If true, the header flags when any breaking change is present.
specFormatstring——
targetSpecContentstring—Inline target (new) spec content.
targetSpecPathstring—Path to the target (new) spec file.

No output schema declared.

No examples provided.

explain_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.

NameTypeReqDescription
baseSpecContentstring—Inline base (old) spec content.
baseSpecPathstring—Path to the base (old) spec file.
targetSpecContentstring—Inline target (new) spec content.
targetSpecPathstring—Path to the target (new) spec file.

No output schema declared.

No examples provided.

generate_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.

NameTypeReqDescription
baseSpecContentstring—Inline base (old) spec content.
baseSpecPathstring—Path to the base (old) spec file.
languagestring——
targetSpecContentstring—Inline target (new) spec content.
targetSpecPathstring—Path to the target (new) spec file.

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
audiencestring——
baseSpecContentstring—Inline base (old) spec content.
baseSpecPathstring—Path to the base (old) spec file.
targetSpecContentstring—Inline target (new) spec content.
targetSpecPathstring—Path to the target (new) spec file.

No output schema declared.

No examples provided.

is_change_safe ~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.

NameTypeReqDescription
baseSpecContentstring—Inline base (old) spec content.
baseSpecPathstring—Path to the base (old) spec file.
environmentstring—Optional target environment, e.g. staging or production.
specFormatstring——
targetSpecContentstring—Inline target (new) spec content.
targetSpecPathstring—Path to the target (new) spec file.

No output schema declared.

No examples provided.