Shipcheck MCP
NPM · SHIPCHECK-MCP
Read-only Shipcheck launch-risk scans for authorized JS, TS, and MCP repos.
Available components
Last scanned (18 hours ago)
Scores higher than 90% of npm servers
Category Security
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 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to TateLyman/shipcheck-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 178 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 246 tokens (~123/item across 2 items; 1 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
- 4 Nov 26 −4
- Stability: pass → 0.77 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 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
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
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 4 Nov 2026 · Analysed npm/shipcheck-mcp@0.1.12
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 | TateLyman/shipcheck-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/TateLyman/shipcheck-mcp/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 1489229663 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d4d90d1fa6614990ef0a73070de94b685d9af82ae8e1d8d77c26e452146c5cbb59456106de4e11d2f71d01afa29b1b496bfb39838325f7582ed599f27 |
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 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
scan_repository Scan repository with Shipcheck ~232
Run read-only Shipcheck static analysis on an authorized local JavaScript, TypeScript, or MCP repository. Use before launch, directory submission, or client handoff to find exposed environment values, unsigned webhook handlers, missing database-rule evidence, debug leftovers, dependency risk, weak CI/docs, and usage-cost guardrail gaps. The tool reads project files, does not modify the repository, does not execute project code, and does not require network access. It returns both a formatted report and structured findings with severity, file path, and remediation.
| Name | Type | Req | Description |
|---|---|---|---|
| failOn | string | – | Pass/fail threshold. high fails only high findings; medium fails medium and high; low fails low through high; info fails on any finding. |
| format | string | – | Report rendering: text for terminals, markdown for review notes, json for automation, or sarif for code-scanning upload. |
| root | string | – | Absolute or relative path to the authorized local repository. Defaults to the current working directory. |
| strict | boolean | – | When true, enables extra release-readiness checks for launch handoff, directory submission, and production review. |
| Name | Type | Req | Description |
|---|---|---|---|
| failOn | string | yes | Severity threshold used for the pass/fail decision. |
| findings | array | yes | Ordered launch-risk findings. |
| ok | boolean | yes | Whether the scan passed the selected failOn threshold. |
| root | string | yes | Scanned repository root. |
| score | number | yes | Launch-readiness score from 0 to 100. |
| totals | object | yes | Finding counts by severity. |
No examples provided.
How do I install the Shipcheck MCP server?
Shipcheck MCP runs locally as an npm package, launched with npx -y shipcheck-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · shipcheck-mcp
claude mcp add tatelyman-shipcheck-mcp -- npx -y shipcheck-mcp
What is the Shipcheck MCP server?
Shipcheck MCP is listed in the public MCP registry as io.github.TateLyman/shipcheck-mcp. Read-only Shipcheck launch-risk scans for authorized JS, TS, and MCP repos. This page covers its npm package (shipcheck-mcp).
Is the Shipcheck MCP server safe to use?
Shipcheck MCP scores 86 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 Shipcheck MCP server expose?
Shipcheck MCP exposes 1 tool: scan_repository. Their descriptions and schemas cost roughly 232 tokens of context every time the server is loaded.
Is the Shipcheck MCP server still maintained?
Shipcheck MCP is still listed as active in the MCP registry. We last reached this channel on 4 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 Shipcheck MCP server under?
Shipcheck MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.