MCP server

Patchy, inside your AI agent.

Add Shippable once. Your agent scans the app it's building, reads the proof and applies the fix, before it tells you it's done. Free, runs on your machine. No account to scan your dev server; the full web report needs an email.

claude mcp add shippable -- npx -y shippable-dev mcp
Patchy inside a chat bubble, handing you a brick from his workshop

Install

Pick your agent. Other MCP clients take the same JSON.

Plugin (MCP server plus a "check before shipping" skill), inside Claude Code:

claude code
/plugin marketplace add Egarter/shippable-plugin /plugin install shippable@shippable

Or just the MCP server:

terminal
claude mcp add shippable -- npx -y shippable-dev mcp

Two tools

shippable_scan

Checks the running app from the outside: open database tables, secret keys in the browser, exposed files, missing headers. Your dev server scans straight away; a live URL needs the ownership tag.

shippable_review_code

Reads your project: database rules, functions that don't check who's calling, unsigned webhooks, every dependency. Then gives your agent a checklist for what patterns can't catch, like limits enforced only in the frontend or codes that work twice.

What to ask your agent

prompt
Scan my app with Shippable before we ship, and fix every critical and high finding.
prompt
Review my code with Shippable and work through its checklist.
prompt
Scan localhost:5173 with Shippable, then re-scan after each fix to confirm it's gone.

Make it a rule

Paste this into your AI tool. It writes the rule into AGENTS.md (and CLAUDE.md or Cursor rules if you use them), so your agent won't call it ready until Patchy agrees.

Prompt for your AI tool
Add this "Before shipping" section to this project's agent instructions so every future session follows it. Put it in AGENTS.md at the project root (create the file if it doesn't exist). If the project also has CLAUDE.md or Cursor rules (.cursor/rules), add it there too. Don't change anything else. ## Before shipping Before telling me this app is ready to ship: 1. Run `npx shippable-dev scan <dev server URL>` (for example localhost:5173). 2. Fix every critical and high finding it reports, then scan again to confirm. 3. After deploying, run `npx shippable-dev scan <live URL>`. 4. Give me the "Full report" file path from the last scan.

Questions

Is there a server URL?

No. The server runs on your own machine: your AI tool starts it with "npx -y shippable-dev mcp". That's what lets it read your project folder. In the official MCP Registry it's listed as io.github.Egarter/shippable; the npm package is shippable-dev.

Does my code leave my machine?

No. Code checks run locally. Package names and versions go to the public OSV vulnerability database, and each scan sends us an anonymous count (version, scan type, number of findings by severity; never URLs, code or findings). Turn that off with SHIPPABLE_TELEMETRY=0. Live scans talk to your app and its database, read-only.

Can my agent scan any website?

No. Your dev server on localhost scans straight away. A live URL first needs a one-line ownership tag that only the app's owner can deploy; the agent gets the tag and the prompt to add it.

Does it change my app or data?

Never. Every check only reads. When it proves a table is open, it reads at most a few rows as evidence.

What does it cost?

Nothing. The MCP server and the CLI are free and unlimited, including code review and your local dev server. Saving a live app to your Shippable account follows the web pricing: your first app is free, then $1 a month per extra app.

Which agents work?

Any agent that supports MCP servers over stdio: Claude Code, Cursor, Windsurf, VS Code, Cline, Zed and others. Use the JSON config for anything not listed above.

See everything Patchy checks →

Patchy reading a blueprint and directing three small robots as they fix a brick wall
Patchy leaning proudly on a freshly patched wall

Find the leaks before someone else does.

Your first app is free; it's read-only and takes about a minute. Patchy's ready when you are.