Skip to main content
ShipSafe

● MCP Server

Scan as your agent writes.

The ShipSafe MCP server lets your AI coding agent scan the code it writes for security vulnerabilities, in-loop, without leaving the editor. Works in Cursor, Claude Code, and Claude Desktop. Your code is never stored.

▸ Tools

Tools

Three tools your agent can call. Most of the time it just needs shipsafe_scan.

shipsafe_scanScan a directory for vulnerabilities — secrets, injection, broken auth/IDOR, misconfiguration, and known-CVE dependencies. Returns plain-English findings with the exact fix, plus a structured clean/not-clean verdict the agent can branch on.Free (local + dependency scan). AI deep analysis needs Growth or Shield.
shipsafe_fix_promptScan, then return one paste-ready prompt that fixes everything at once, tailored to the detected AI builder.Growth / Shield
shipsafe_statusShow login state, plan, and remaining AI scan quota.

▸ Setup

Set up your editor

Point your agent at the ShipSafe MCP server, then ask it to “scan this project with ShipSafe and fix what it finds.”

▸ Claude Code

TERMINAL
claude mcp add shipsafe -- npx -y @ship-safe/mcp

▸ Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

JSON·mcp.json
{
  "mcpServers": {
    "shipsafe": { "command": "npx", "args": ["-y", "@ship-safe/mcp"] }
  }
}

▸ Claude Desktop

Add the same block to claude_desktop_config.json:

JSON·claude_desktop_config.json
{
  "mcpServers": {
    "shipsafe": { "command": "npx", "args": ["-y", "@ship-safe/mcp"] }
  }
}

▸ Login

Log in for AI analysis

The free local pattern and dependency scan works with no login. The MCP server reuses the ShipSafe CLI’s session, so a single login unlocks AI deep analysis and fix prompts. Once, in a terminal:

TERMINAL
npx @ship-safe/cli login