Skip to content

Breakwire MCP server

Which MCP servers are Breakwire's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Breakwire

Whose server it is
  • Registry nameorg.breakwire/breakwireverified in the MCP registry

The registry name sits under breakwire.org. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools3
  • Server calls itselfbreakwire
  • Server version0.11.8
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 65 ms.

Should an agent connect itNot proven either way yet
  • Its tools do look up the cause of an agent's API error; report whether a documented fix resolved an agent error, but not track deprecation deadlines for packages in package.json.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "look up the cause of an agent's API error", the likely first call is lookup_error.
  • For "report whether a documented fix resolved an agent error", the likely first call is close_lookup.
  • Parameters are untyped or undescribed in 3 of 3 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it2 of 3 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer86 ms
  • Space in an agent's context≈ 1,265 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 3 of 3

What an agent can do with it

  • can do · look up the cause of an agent's API error
  • cannot · track deprecation deadlines for packages in package.json
  • can do · report whether a documented fix resolved an agent error

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-29
  • session_brief

    Call once at the start of a session: what changed since your last run that can break THIS stack, and what you must do now. Send your stack once (services, packages like "npm:@modelcontextprotocol/[email protected]", runtime {"node":"22"}, models…

  • lookup_error

    Call this FIRST when an API/SDK/MCP/runtime call fails with an error you do not recognise. Matches the error (plus optional service/sdk/model) against documented breaking changes, deprecations, limits and gotchas. Returns answer (one…

  • close_lookup

    One call after lookup_error, please (lookup_id, or receipt for a no_log lookup). fixed (the fix worked), partial (right cause, different error text), applies (informational/deadline match was useful), not_fixed (fix did not work for you…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "breakwire": {
      "type": "http",
      "url": "https://breakwire.org/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http breakwire https://breakwire.org/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://breakwire.org/mcp as a custom connector in the settings.

OpenAPI spec

49 paths, read 2026-10-29. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.