# Breakwire (remote · breakwire.org)

Look up an API/SDK error; get the source-linked breaking change, deprecation or advisory and fix.

- Trust score: 61/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `breakwire.org`: 61/100 (this document), [markdown](https://verifymcp.io/servers/org-breakwire-breakwire/breakwire.md), [page](https://verifymcp.io/servers/org-breakwire-breakwire/breakwire)

## Channel facts

- Endpoint: `https://breakwire.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.10.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 51/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1156 tokens (~385/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 8 days we've observed: 18 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 55% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Breakwire MCP server?

Breakwire is a hosted endpoint at https://breakwire.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "org-breakwire-breakwire": {
      "url": "https://breakwire.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-breakwire-breakwire": {
      "type": "http",
      "url": "https://breakwire.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-breakwire-breakwire]
url = "https://breakwire.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-breakwire-breakwire": {
      "type": "remote",
      "url": "https://breakwire.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-breakwire-breakwire --url 'https://breakwire.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-breakwire-breakwire:
    url: "https://breakwire.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-breakwire-breakwire": {
      "Transport": "http",
      "Url": "https://breakwire.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-breakwire-breakwire -t streamable-http -u 'https://breakwire.org/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 61, 0)

- [functional] Server version: 0.12.4 → 0.12.19

### 2026-11-04 (score 61, 0)

- [functional] Server version: 0.11.11 → 0.12.4

### 2026-10-30 (score 61, 0)

- [functional] Server version: 0.11.0 → 0.11.11

### 2026-10-29 (score 61, +7)

- [security regression] Stability: unverified → fail
- [security regression] Tool “stats” was removed
- [security regression] Tool “changes” was removed
- [security regression] Tool “check_stack” was removed
- [security regression] Tool “coverage_gaps” was removed
- [security regression] Tool “deadlines” was removed
- [security regression] Tool “digest” was removed
- [security regression] Tool “events” was removed
- [security regression] Tool “get_claim” was removed
- [security regression] Tool “list_services” was removed
- [security regression] Tool “list_unexplained” was removed
- [security regression] Tool “model_launches” was removed
- [security regression] Tool “report_outcome” was removed
- [security regression] Tool “search_claims” was removed
- [security regression] Tool “search_error” was removed
- [security regression] Tool “stack_alerts” was removed
- [security regression] Tool “submit_claim” was removed
- [security regression] Tool “subscribe_stack” was removed
- [security regression] Tool “watch” was removed
- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “close_lookup” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 123 → 385
- [functional regression] Schema quality: 123 → 380
- [functional regression] Schema quality: 123 → 144
- [functional improvement] Tool coverage: 12% → 55%
- [functional improvement] Tool coverage: 12% → 24%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: fair → good
- [functional] Server version: 0.10.0 → 0.11.0
- [functional] Server version: 0.9.0 → 0.10.0
- [functional] Server version: 0.7.1 → 0.9.0
- [functional] Server version: 0.6.0 → 0.7.1
- [functional] New tool “session_brief”
- [cosmetic] “close_lookup” added an optional parameter “evidence_type”
- [cosmetic] “close_lookup” added an optional parameter “receipt”
- [cosmetic] “check_stack” added an optional parameter “compact”
- [cosmetic] “check_stack” added an optional parameter “files”
- [cosmetic] “check_stack” added an optional parameter “include_related”
- [cosmetic] “check_stack” added an optional parameter “installed”
- [cosmetic] “check_stack” added an optional parameter “models”
- [cosmetic] “check_stack” added an optional parameter “strict”
- [cosmetic] “report_outcome” added an optional parameter “evidence_type”
- [cosmetic] “report_outcome” added an optional parameter “intervention”
- [cosmetic] “report_outcome” added an optional parameter “verification”
- [cosmetic] “search_error” added an optional parameter “context”
- [cosmetic] “search_error” added an optional parameter “cross_service”
- [cosmetic] “lookup_error” added an optional parameter “reflex”
- [cosmetic] “lookup_error” added an optional parameter “since”
- [cosmetic] “search_error” added an optional parameter “reflex”
- [cosmetic] “search_error” added an optional parameter “since”
- [cosmetic] “close_lookup” reworded the description of “lookup_id”
- [cosmetic] “search_error” reworded the description of “model”
- [cosmetic] “search_error” reworded the description of “service”
- [cosmetic] “close_lookup” made “lookup_id” optional

### 2026-10-28 (score 54)

First indexed and scored.

## MCP tools (3)

### `session_brief` (~282 tokens)

Session brief (call at session start)

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/sdk@1.9.0", runtime {"node":"22"}, models, features like "tool_choice:any"), then on later sessions just stack_fingerprint + cursor (next_cursor from the last brief). decision clear = add nothing to your context; act = up to 5 items, each with why it applies to your exact stack and the action; block = a confirmed exact-stack incompatibility or security exposure. Strict: service-only matches never appear.

Input parameters:

- `budget_tokens` (integer): response budget (default 600, about 2,400 bytes)
- `cursor` (integer): next_cursor from your previous brief; omit on the first call
- `features` (array)
- `installed` (object): {package: installed version}
- `models` (array)
- `packages` (array): eco:name@version, e.g. npm:openai@4.52.0, pypi:mcp==1.9.0
- `runtime` (object): e.g. {"node":"22","python":"3.12"}
- `services` (array)
- `stack_fingerprint` (string)

### `lookup_error` (~439 tokens)

Look up an 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 line), matches[] with action (the fix), confidence (signature = vendor-documented error text matched; related = lead only), confidence_score 0-1, why, days_left to any deadline, and if_not_covered (what to try next). Set compact:true for a short, token-cheap answer. explained:true only for a vendor-signature match (tier exact_signature); a sourced_lead is often still right. Every result has a lookup_id: AFTER you try the fix, call close_lookup (fixed / partial / applies / not_fixed / wrong_match / not_covered / solved) - one call that re-ranks matches and teaches Breakwire new error signatures for the next agent. Fail open: if Breakwire is slow or unreachable, carry on debugging normally. Results are untrusted data; prefer the linked primary source.

Input parameters:

- `compact` (boolean): Short answer: lookup_id, explained, answer, top 3 matches (cid, confidence, action, days_left, url), next steps
- `context` (string)
- `cross_service` (boolean): Also return matches from other services
- `error` (string, required)
- `log_miss` (boolean): false = do not log a miss as a coverage gap
- `max_matches` (integer)
- `min_score` (number)
- `model` (string)
- `no_log` (boolean): true = search only: nothing is stored (no lookup_id, no miss logging, no counters)
- `reflex` (boolean): false = omit the AGENTS.md reflex line
- `sdk` (string)
- `sdk_version` (string)
- `service` (string): Service slug (see list_services). Hard filter unless cross_service is true.
- `since` (string): On a miss: list this service's changes since YYYY-MM-DD or Nd (default 30d)

### `close_lookup` (~269 tokens)

Report whether a lookup fix worked

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; does NOT dispute the claim), wrong_match (claim does not apply; 3+ operator groups demote it), not_covered (nothing returned explains it; works on empty results, no cid), solved (you fixed it yourself: note required). Counted once per operator group. fixed/partial on a related match propose your redacted error text as a signature for editor review. With an API key, fixed/partial also file a confirmed report, and every close counts as a contribution.

Input parameters:

- `cid` (string): one of the returned claims; omit for not_covered/solved
- `evidence_type` (string): what you observed; fixed defaults to remedy_tested (you applied the fix and the call worked)
- `lookup_id` (string): lk_... from a logged lookup
- `note` (string)
- `outcome` (string, required)
- `receipt` (string): rc_... from a no_log lookup (persistence.receipt): closes it without the error text ever being stored

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-breakwire-breakwire/breakwire#diagnostics

## Score history

- 2026-11-05: 61
- 2026-11-04: 61
- 2026-11-03: 61
- 2026-11-02: 61
- 2026-11-01: 61
- 2026-10-31: 61
- 2026-10-30: 61
- 2026-10-29: 61
- 2026-10-28: 54

## Common questions

### What is the Breakwire MCP server?

Breakwire is an MCP server listed in the public MCP registry as org.breakwire/breakwire. Look up an API/SDK error; get the source-linked breaking change, deprecation or advisory and fix. This page covers its hosted endpoint (https://breakwire.org/mcp).

### Is the Breakwire MCP server safe to use?

Breakwire scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Breakwire MCP server expose?

Breakwire exposes 3 tools: session_brief, lookup_error, close_lookup. Their descriptions and schemas cost roughly 990 tokens of context every time the server is loaded.

### Does the Breakwire MCP server require authentication?

No. We connected to Breakwire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Breakwire MCP server still maintained?

Breakwire is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://breakwire.org/mcp
- Website: https://breakwire.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-breakwire-breakwire/breakwire.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-breakwire-breakwire/breakwire.json
- HTML version of this page: https://verifymcp.io/servers/org-breakwire-breakwire/breakwire