ShipSafe — Independent security verification

co.ship-safePublished by ship-safe.coOfficial publisherv0.6.4Updated Oct 24, 2026

Independent security review for AI-built apps: exposed secrets, broken auth, unsafe data access.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

ShipSafe gives an assistant independent security review of AI-built apps, flagging exposed secrets, broken auth and unsafe data access.

What you can do
  • Run an independent security review of an app built with AI assistance.
  • Surface exposed secrets, broken authentication and unsafe data access.
  • Reach the service either through a remote endpoint or a local npm package started with npx.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you have an app or codebase generated with AI help and want a second, independent check of its security posture before shipping or sharing it.
Requirements
A ShipSafe account and a bearer token, supplied in the Authorization header; the same token the ShipSafe CLI uses. The token is obtained from the provider's settings page. Can run as a remote endpoint or locally via the npm package with npx, which needs Node.js.
Before you install
The server requires a bearer token in the Authorization header, so treat it as a secret and keep it out of shared configs and logs. The manifest lists no tools, so what the review reads or sends to the provider cannot be verified from this listing; confirm what code or data leaves your machine before running it on private repositories.

Installation

In SourceWeft

  1. Open ShipSafe — Independent security verification in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.ship-safe%2Fscanner/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "shipsafe-independent-security-verificati": {
      "type": "http",
      "url": "https://ship-safe.co/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

6
  1. v0.6.4LatestSep 29, 2026
  2. v0.6.3Sep 25, 2026
  3. v0.6.2Sep 25, 2026
  4. v0.6.1Sep 24, 2026
  5. v0.6.0Sep 23, 2026
  6. v0.5.3Sep 22, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.