ShipSafe — Independent security verification

Run a non-destructive dynamic scan against a RUNNING app (your localhost dev server or a deployed URL you own). Unlike the static scan (which reads source), this makes real GET requests to find issues only visible at runtime: missing security headers (CSP, HSTS, clickjacking), insecure cookies (Secure/HttpOnly/SameSite), CORS misconfiguration and leaked stack traces. It is read-only (GET only, bounded request count, gentle rate) and never sends payloads that change data. CONSENT REQUIRED: only probe an app you own or operate; you MUST pass confirmOwnership:true. NOTE: probing for exposed files the app never linked (/.env, /.git/config, backups, /admin), and anything in extraPaths, are unsolicited requests, so they run only when the human operator has set SHIPSAFE_MCP_ALLOW_ACTIVE_PROBE=true in their MCP config — a tool argument cannot turn them on. The result says which tier actually ran. Use after deploying, or against your local dev server before shipping.

Scan the project and generate a single paste-ready prompt that fixes ALL findings at once, tailored to the detected AI builder (Cursor, Lovable, Bolt, v0). Requires a login on a monthly plan (`shipsafe login`). Use when the user wants one prompt to hand to their AI tool to fix everything.

Log in to ShipSafe without leaving the editor, to unlock AI deep analysis and fix prompts. Two steps: call with NO arguments to start; you'll get a URL and a code to authorize in the browser. After authorizing, call again with the returned `device_code` to finish. The free local + dependency scan works without logging in.

Tell ShipSafe that a finding it reported is a false positive. This sends the rule + context to ShipSafe's central false-positive database (shared with the web app and CLI) so the team can tune the rule and stop it from misfiring. Use when you and the user agree a finding is wrong, not a real issue. Requires a ShipSafe login. The code snippet is redacted before sending; no secrets leave the machine.

Scan a project directory for security vulnerabilities using ShipSafe: exposed secrets, injection, broken auth/access control (IDOR), misconfiguration, and known-vulnerable dependencies (CVEs found in package-lock.json/pnpm-lock.yaml/yarn.lock/requirements.txt/go.sum/Gemfile.lock). A fast local pattern + dependency scan runs for free with no login; with a login it can also run AI deep analysis (automatic on paid plans; a free account includes one AI scan — pass ai: true). Returns plain-English findings (each with the exact fix) AND structured output: a `clean` boolean + severity `counts` you can branch on, plus a `diff` (for full-project scans) showing what your last fix resolved vs what's still open. Pass `paths` or `changedOnly:true` to scan just the files you edited for a fast inner loop. Use right after writing or changing code, and again after fixing to confirm the issues are gone. The user's code is never stored.

Test a running API you own for IDOR / BOLA (OWASP API #1, the #1 vuln AI builders ship): can one logged-in user read ANOTHER user's objects by changing the ID? You provide TWO test-account bearer tokens (A and B) and the resource endpoints; for each resource, user A lists their own objects, then user B tries to read them by ID. A 200 = a real IDOR. Also flags collections readable with no token. Read-only (GET only), bounded. CONSENT REQUIRED. Use TWO DISPOSABLE TEST ACCOUNTS on a non-production environment, never real customer IDs. Provide two bearer tokens, OR test-account credentials plus a `login` config and ShipSafe fetches the tokens for you (Supabase Auth or a generic JWT endpoint). Tokens are used read-only and never stored.

Scan a local git repository's COMMIT HISTORY for secrets that were ever committed: API keys, service-role keys, tokens, secret-named env vars. This catches the dangerous case a normal scan can't see: a credential that was committed and later deleted from the current files but still lives in git history (anyone who clones the repo can recover it). Read-only and fully local; it reads past file versions with git and never writes or pushes. Findings flagged `removedFromHead` are the urgent ones: gone from your code, still in history, so the credential must be rotated AND the history purged (e.g. git filter-repo / BFG). Use after a repo has handled secrets, before going public, or when onboarding an existing repo.

Scan a RUNNING deployed app you own in one shot: (1) the DAST runtime probe (security headers, CSP quality, clickjacking) AND (2) the high-value check a source scan can miss: it fetches the deployed CLIENT JS bundles (entry + lazy-loaded chunks) and scans them for SECRETS leaked into the browser. AI builders (Lovable, Bolt, v0) routinely inline API keys at build time, so the leak exists only in the deployed artifact, not the repo. Also flags publicly accessible source maps (original source recoverable). Read-only (GET only, bounded, gentle). CONSENT REQUIRED: only scan an app you own; pass confirmOwnership:true. Secret VALUES are redacted in the output. NOTE: exposed-path probing and validateSecrets send unsolicited requests to the target or to a third party, so they run only when the human operator set SHIPSAFE_MCP_ALLOW_ACTIVE_PROBE=true in their MCP config; a tool argument cannot turn them on, and the result says which tier ran.

Show whether the user is logged in to ShipSafe, their plan, and remaining AI scan quota. Use this to check if AI deep analysis is available before scanning.