ShipSafe — Independent security verification
co.ship-safe/scannerVersion 0.6.4Independent security review for AI-built apps: exposed secrets, broken auth, unsafe data access.
Status
Sign-in required383 msReachable. It asks for authorization, so we did not look inside.- Last checked
- Nov 14, 2026, 13:44 UTC
- Latency
- 383 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://ship-safe.co/api/mcpSign-in required383 msAPI key
Claude Code
This server asks for sign-in. Your client opens the sign-in when it connects.
claude mcp add --transport http scanner https://ship-safe.co/api/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: scanner
Remote MCP server URL: https://ship-safe.co/api/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"scanner": {
"url": "https://ship-safe.co/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"scanner","type":"http","url":"https://ship-safe.co/api/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Streamable HTTP
npm: @ship-safe/mcp 0.6.4Package only
npm (npx)
claude mcp add scanner -- npx -y @ship-safe/mcp@0.6.4Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
Tools are visible after sign-in; we do not look inside protected servers.
Details
- Registry status
- Active
- Published
- Sep 28, 2026
- Updated
- Sep 28, 2026
- Repository
- Not given
- Categories (suggested)
- SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared