Provides tools to audit local package directories for npm publish-readiness, analyzing configuration files and previewing tarball contents to ensure a successful release.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-shipcheckaudit the current folder for npm publish readiness"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-shipcheck
A.k.a. "NPM Readiness Sheriff"
Given a local package folder, mcp-shipcheck produces a deterministic publish-readiness report: what will be included in the tarball, obvious foot-guns (missing types, broken exports, no LICENSE, etc.), and a concrete fix list.
It turns "release anxiety" into a machine-checkable artifact.
Features
Audit: Analyzes
package.json,tsconfig.json, exports, and file existence to score readiness.Pack Preview: Runs
npm pack --jsonto show exactly what files ship (and their sizes), without needing to unpack a tarball manually.Explain Failures: Provides human-readable context and fixes for specific error codes.
All tools are read-only (no auto-fixes), so they are safe for MCP hosts to call automatically.
Tools
shipcheck.audit
Input:
{ path: string }(Absolute or relative path to package)Output: JSON report containing a score (0-100), structured findings (fails, warnings, infos), and summary counts.
shipcheck.packPreview
Input:
{ path: string }Output: JSON list of files that would be included in the release tarball, along with metadata.
shipcheck.explainFailure
Input:
{ code: string }(e.g.,PKG.EXPORTS.MISSING)Output: Detailed explanation of the error and suggested fixes.
Installation & Usage
Usage with MCP
This tool is designed to be used with an MCP client (like Claude Desktop or an IDE extension).
Configuration (mcp-settings.json):
Building Locally
License
MIT