# Shipcheck MCP (npm · shipcheck-mcp)

Read-only Shipcheck launch-risk scans for authorized JS, TS, and MCP repos.

- Trust score: 82/100 (high trust)
- Change this week: +29
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `shipcheck-mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/tatelyman-shipcheck-mcp/shipcheck-mcp.md), [page](https://verifymcp.io/servers/tatelyman-shipcheck-mcp/shipcheck-mcp)

## Channel facts

- Registry: `npm`
- Package: `shipcheck-mcp`
- Version: `0.1.12`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to TateLyman/shipcheck-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 85 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 246 tokens (~123/item across 2 items; 1 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add tatelyman-shipcheck-mcp -- npx -y shipcheck-mcp
```

### Codex

```bash
codex mcp add tatelyman-shipcheck-mcp -- npx -y shipcheck-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add tatelyman-shipcheck-mcp --command npx --arg -y --arg shipcheck-mcp
```

### Hermes

```yaml
mcp_servers:
  tatelyman-shipcheck-mcp:
    command: "npx"
    args: ["-y", "shipcheck-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "tatelyman-shipcheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "shipcheck-mcp"
      ]
    }
  }
}
```

## 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-08-03 (score 82, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-02 (score 78, +52)

- [security improvement] Install scripts: unverified → pass
- [security improvement] Provenance: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] 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
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-07-31 (score 26, −27)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 53)

First indexed and scored.

## MCP tools (1)

### `scan_repository` (~232 tokens)

Scan repository with Shipcheck

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.

Input parameters:

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

Output parameters:

- `failOn` (string): Severity threshold used for the pass/fail decision.
- `findings` (array): Ordered launch-risk findings.
- `ok` (boolean): Whether the scan passed the selected failOn threshold.
- `root` (string): Scanned repository root.
- `score` (number): Launch-readiness score from 0 to 100.
- `totals` (object): Finding counts by severity.

## Diagnostics

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

## Score history

- 2026-08-03: 82
- 2026-08-02: 78
- 2026-08-01: 26
- 2026-07-31: 26
- 2026-07-30: 53
- 2026-07-28: 53
- 2026-07-27: 53

## Links

- npm package: https://www.npmjs.com/package/shipcheck-mcp
- Socket report: https://socket.dev/npm/package/shipcheck-mcp
- Repository: https://github.com/TateLyman/shipcheck-mcp
- Website: https://tateprograms.com/shipcheck.html
- Changelog RSS feed: https://verifymcp.io/servers/tatelyman-shipcheck-mcp/shipcheck-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/tatelyman-shipcheck-mcp/shipcheck-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/tatelyman-shipcheck-mcp/shipcheck-mcp