Skip to main content
ShipSafe

● Live URL Scan

Scan the app you shipped.

A source scan reads your code. A live-URL scan reads what you actually deployed. Some of the worst leaks only exist in the built artifact: an API key inlined at build time lives in the JavaScript your users download, not in your repo. ShipSafe fetches your live app and checks for exactly that.

What it checks

  • Leaked client secrets — fetches your entry bundle and its lazy-loaded chunks and scans them for API keys, tokens, and service-role keys baked into the browser code.
  • Exposed source maps — flags publicly fetchable .map files that hand attackers your original source.
  • Runtime headers & CSP — the full set of DAST checks: HSTS, Content-Security-Policy quality, clickjacking, exposed paths.

Run it from the web

On the scan page, switch the target toggle to Live URL, paste your deployed app URL, confirm you are authorized to test it, and scan.

Run it from your editor (MCP)

The MCP server exposes the same scan as a tool your AI agent can call:

AGENT
shipsafe_scan_url
  url: "https://yourapp.com"
  confirmOwnership: true

Privacy

Fetched pages and bundles are analyzed in memory and are not stored. ShipSafe keeps only the findings (the type and location of each issue), not your app's content, and the live-URL scan sends nothing to any third-party AI provider.