Shipcheck MCP
NPM · SHIPCHECK-MCP · SCANNED AUG 3
Read-only Shipcheck launch-risk scans for authorized JS, TS, and MCP repos.
Available components
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 (96 of 100), 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 (96 of 100), 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 TateLyman/shipcheck-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 85 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · shipcheck-mcp
claude mcp add tatelyman-shipcheck-mcp -- npx -y shipcheck-mcp
codex mcp add tatelyman-shipcheck-mcp -- npx -y shipcheck-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tatelyman-shipcheck-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"shipcheck-mcp"
],
"enabled": true
}
}
} openclaw mcp add tatelyman-shipcheck-mcp --command npx --arg -y --arg shipcheck-mcp
mcp_servers:
tatelyman-shipcheck-mcp:
command: "npx"
args: ["-y", "shipcheck-mcp"] {
"mcpServers": {
"tatelyman-shipcheck-mcp": {
"command": "npx",
"args": [
"-y",
"shipcheck-mcp"
]
}
}
} 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 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +52
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- The attested source repository moved: TateLyman/shipcheck-mcp security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 31 Jul 26 −27
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 53
First indexed and scored.
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:
- 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:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:d4d90d1fa6614990ef0a73070de94b685d9af82ae8e1d8d77c26e452146c5cbb59456106de4e11d2f71d01afa29b1b496bfb39838325f7582ed599f27
- Discovery method:
- attestation_endpoint
Dependencies 96 packages
96 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.