Breakwire MCP server
org.breakwire/breakwirebreakwire.orgstreamable-httpv0.10.0Scanned
Look up an API/SDK error; get the source-linked breaking change, deprecation or advisory and fix.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Breakwire MCP server can do
The Breakwire MCP server is published by breakwire.org, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: session_brief, lookup_error and close_lookup), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 0.10.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 3Claude Code: ask
close_lookupOne call after lookup_error, please (lookup_id, or receipt for a no_log lookup).No findings
Why it is in this group
- The name "close_lookup" says "close": a word for a change.
Description, as the server wrote it 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. Fail open: if Breakwire is slow, down or returns nothing, continue with the original task; never block on it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_errorCall this FIRST when an API/SDK/MCP/runtime call fails with an error you do not recognise.No findings
Why it is in this group
- The name "lookup_error" says "lookup": a word for reading.
- The description's first verb is "call": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
session_briefCall once at the start of a session: what changed since your last run that can break THIS stack, and what you must do now.1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "session_brief" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
Description, as the server wrote it 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. Fail open: if Breakwire is slow, down or returns nothing, continue with the original task; never block on it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 5, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://breakwire.org/mcp: tools/list returned 3 tools to an anonymous client, including session_brief (write), lookup_error (write), close_lookup (write)
Posture changes
- Nov 5, 2026
- Tools that change things, listed without credentials: 13 to 3
Findings
Matches of fixed checks, with the text they matched.
- Warnsession_brief
The server marks "session_brief" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:close_lookupChanges thingsdescription
- Changed:session_briefChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 13 -> 3.View diff
- Tools that change things, listed without credentials: 13 to 3
Tools1 added, 18 removed, 1 changed.+1 added−18 removed~1 changedView diff
- Added:session_briefChanges things
- Removed:changes
- Removed:check_stack
- Removed:coverage_gaps
- Removed:deadlines
- Removed:digest
- Removed:events
- Removed:get_claim
- Removed:list_services
- Removed:list_unexplained
- Removed:model_launches
- Removed:report_outcome
- Removed:search_claims
- Removed:search_error
- Removed:stack_alerts
- Removed:stats
- Removed:submit_claim
- Removed:subscribe_stack
- Removed:watch
- Changed:close_lookupChanges thingsdescriptioninputSchema
Tools7 changed.~7 changedView diff
- Changed:close_lookupChanges thingsannotations
- Changed:lookup_errorChanges thingsinputSchemaannotations
- Changed:report_outcomeChanges thingsannotations
- Changed:search_errorOnly readsinputSchema
- Changed:submit_claimChanges thingsannotations
- Changed:subscribe_stackChanges thingsannotations
- Changed:watchChanges thingsannotations
Tools2 added, 3 changed.+2 added~3 changedView diff
- Added:model_launchesChanges things
- Added:search_errorOnly reads
- Changed:changesCan't be undonedescriptioninputSchema
- Changed:digestChanges thingsdescriptioninputSchema
- Changed:lookup_errorChanges thingsdescriptioninputSchema
Tools4 added, 5 changed.+4 added~5 changedView diff
- Added:coverage_gapsChanges things
- Added:stack_alertsOnly reads
- Added:statsChanges things
- Added:subscribe_stackChanges things
- Changed:check_stackChanges thingstitledescriptioninputSchema
- Changed:close_lookupChanges thingsdescriptioninputSchema
- Changed:deadlinesChanges thingsdescriptioninputSchema
- Changed:lookup_errorChanges thingsdescriptioninputSchema
- Changed:watchChanges thingsdescription
Install
Pinned to version 0.10.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http breakwire https://breakwire.org/mcpclaude mcp add --transport http breakwire https://breakwire.org/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__breakwire__session_brief",
"mcp__breakwire__lookup_error",
"mcp__breakwire__close_lookup"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as breakwire. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/org.breakwire/breakwire/verify?hash=43ac5f544c4b250357546ea328395aae035eddce2e66b75ee370bab7925f7eb1" | jq -e '.changed == false'Pinned hash 43ac5f544c4b, from Nov 10, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/org.breakwire/breakwire/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/org.breakwire/breakwire)Source: MCP Registry. Synced Oct 29, 2026, 05:18 UTC.
Breakwire MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Breakwire MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Breakwire MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Breakwire MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Breakwire MCP server have?
- 3 tools: 3 write. session_brief, lookup_error and close_lookup.
Does the Breakwire MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Breakwire MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Breakwire MCP server changed its tools?
- Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.