Shipcheck MCP

io.github.TateLymanPublished by GitHub account TateLymanv0.1.12Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that runs read-only Shipcheck launch-risk scans on authorized JavaScript and TypeScript repositories.

What you can do
Scan a local JS or TS repository for launch risks such as exposed env vars, unsigned webhooks, debug routes, missing CI, loose dependencies and thin release docs, plus MCP-specific gaps like missing smoke-test proof and undocumented STDIO or remote auth boundaries. Choose the output format (text, markdown, JSON or SARIF) and a severity threshold for failing the scan, with an optional strict mode.
When to use it
Use it before shipping or publishing a JavaScript, TypeScript or MCP project, when you want a quick static review of launch-readiness and security hygiene from inside your MCP client.
Requirements
Runs as a local stdio process, launched with npx from the shipcheck-mcp npm package, so Node.js and npm are needed. No accounts, API keys or environment variables are declared, and it does not require network access.
Before you install
It reads local project files, so run it only on repositories you own or are authorized to inspect. It is defensive static analysis, not a penetration test, and its findings are not a guarantee of safety. Review the command, args and any env values in generated client configs and keep the package source trusted.

Installation

In SourceWeft

  1. Open Shipcheck MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

shipcheck-mcp

[npm version] [ci] [MCP Registry] [shipcheck-mcp MCP server]

MCP server that lets local MCP clients run Shipcheck on authorized JavaScript and TypeScript repositories.

Shipcheck scans apps and MCP servers for launch risks such as exposed private-looking env vars, unsigned Stripe webhooks, missing Supabase/Firebase rule evidence, debug routes, missing usage-cost guardrails, missing CI, loose dependencies, thin release docs, missing MCP smoke-test proof, undocumented STDIO execution boundaries, and undocumented remote MCP auth boundaries.

Tool page: https://tateprograms.com/shipcheck.html

Free MCP launch self-check: https://tateprograms.com/mcp-self-check.html

MCP directory launch checklist: https://tateprograms.com/mcp-directory-checklist.html

Paid MCP launch check: https://tateprograms.com/mcp-launch-review.html

Official MCP Registry: https://registry.modelcontextprotocol.io/v0/servers?search=shipcheck

Install

Run directly with npx:

bash
npx --yes shipcheck-mcp

MCP Config

Add this server to an MCP client that supports stdio servers:

json
{  "mcpServers": {    "shipcheck": {      "command": "npx",      "args": ["--yes", "--package", "shipcheck-mcp", "shipcheck-mcp"]    }  }}

STDIO MCP client config launches a local command. Review the command, args, and any env values before running generated configs, keep the package source trusted, and prefer pinned package versions when a deployment needs repeatability.

Tool

scan_repository

json
{  "root": ".",  "format": "markdown",  "failOn": "medium",  "strict": true}

Formats: text, markdown, json, or sarif.

Severities: info, low, medium, or high.

Shipcheck is defensive static analysis, not a penetration test. It reads local project files, does not modify the repository, does not execute project code, and does not require network access. Run it only on repos you own or are authorized to inspect.

Development

bash
npm installnpm run check

Source: README.md at commit beab6af

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.12LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts