Shippable
NPM · SHIPPABLE-DEV
Find leaks in AI-built apps: open Supabase/Firebase data, exposed keys, unsafe edge functions
Available components
Last scanned (22 hours ago)
Scores higher than 37% of npm servers
Category Security
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 494 tokens (~247/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 16 Oct 26 +42
- Injection markers: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → pass ▲ functional
- 15 Oct 26 −41
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: pass → unverified ▼ functional
- Package version: 0.11.11 → 0.12.0 functional
- 14 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 0
- Package version: 0.11.10 → 0.11.11 functional
- 12 Oct 26 34
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 16 Oct 2026 · Analysed npm/shippable-dev@0.12.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
shippable_review_code Shippable code review ~147
Review the project's own code before shipping. Runs Shippable's code checks on the project folder (edge functions nobody authenticates, HTML built from request data, redirects taken from the request, database rules users can abuse, open storage) and returns a checklist for you to work through by reading the code: caller checks, plan limits enforced only in the frontend, email HTML, payments, tables users can edit, storage. Use it before shipping; it complements shippable_scan, which checks the running app from outside. Read-only; your code never leaves the machine.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Absolute path of the project folder. Defaults to the server's working directory. |
No output schema declared.
No examples provided.
shippable_scan Shippable security scan ~229
Scan a web app for security leaks an attacker could find from the outside: Supabase/Firebase data readable by anyone, secret API keys in client code, public storage buckets, exposed .env/.git files, source maps, vulnerable libraries and missing security headers. Read-only: it never changes the app or its data. Pass the local dev server URL (e.g. http://localhost:5173) to scan right away with no setup, or the live URL (e.g. https://myapp.com); the first live scan returns a meta tag to add and deploy to prove ownership. Local scans also read the project folder on disk (unprotected Supabase migrations, secrets in code or .env files, open Firebase rules); your code and findings never leave the machine.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Absolute path of the project folder to also check, for local scans. Defaults to the server's working directory. |
| url | string | yes | The app's URL: a local dev server like http://localhost:5173, or the live site like https://myapp.com |
No output schema declared.
No examples provided.
How do I install the Shippable MCP server?
Shippable runs locally as an npm package, launched with npx -y shippable-dev. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · shippable-dev
claude mcp add egarter-shippable -- npx -y shippable-dev
What is the Shippable MCP server?
Shippable is an MCP server listed in the public MCP registry as io.github.Egarter/shippable. Find leaks in AI-built apps: open Supabase/Firebase data, exposed keys, unsafe edge functions. This page covers its npm package (shippable-dev).
Is the Shippable MCP server safe to use?
Shippable scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Shippable MCP server expose?
Shippable exposes 2 tools: shippable_scan, shippable_review_code. Their descriptions and schemas cost roughly 376 tokens of context every time the server is loaded.
Is the Shippable MCP server still maintained?
Shippable is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Shippable MCP server under?
Shippable declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.