Safeship

app.safeshipPublished by safeship.appOfficial publisherv1.0.0Updated Oct 24, 2026

API monitoring from your editor. Checks the JSON your endpoints return, not just the status code.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Safeship lets an assistant check the JSON that your API endpoints return, not just their status codes, from within your editor.

What you can do
Safeship is a remote MCP endpoint for API monitoring. According to its description, it checks the JSON payloads your endpoints return rather than only the HTTP status code, so an assistant can help verify that responses have the expected shape and content. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to inspect or monitor API responses during development and catch malformed or unexpected JSON that a simple status-code check would miss. It is aimed at developers working with HTTP APIs who already use Safeship.
Requirements
A remote MCP endpoint at mcp.safeship.app over streamable HTTP; no local runtime or package is needed. It requires an API key sent in the X-API-Key header, created under Settings then API Keys on the Safeship site. The key is described as starting with sk_live_. Network access to the endpoint is required.
Before you install
The X-API-Key header carries a live API key (sk_live_), so treat it as a secret and avoid exposing it in logs, shared configs, or prompts. Because the server monitors your API endpoints, the data it reads may include response payloads sent to a third-party service; confirm what is transmitted before connecting production endpoints.

Installation

In SourceWeft

  1. Open Safeship in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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/app.safeship%2Fmcp/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": {
    "safeship": {
      "type": "http",
      "url": "https://mcp.safeship.app/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

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

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.