Breach to Claim: data breach settlements MCP server
io.github.2016judea/breach-to-claim2016judeastreamable-httpv0.1.0Scanned
Am I owed money from a data breach? Open settlements, deadlines, payouts and official claim sites
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- 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 Breach to Claim: data breach settlements MCP server can do
The Breach to Claim: data breach settlements MCP server is published by the GitHub account 2016judea. It has 3 tools. It can create or change data (1 tool: breach_settlement_details), but cannot delete data. 2 tools only read.
3 tools bring in text other people can write (find_breach_settlement, list_open_breach_settlements and breach_settlement_details).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 0.1.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 1Claude Code: ask
breach_settlement_detailsEverything read off one settlement's official website: the class definition and any subclasses verbatim, each benefit with its cap and whether documents are needed, the claim, opt-…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Everything read off one settlement's official website: the class definition and any subclasses verbatim, each benefit with its cap and whether documents are needed, the claim, opt-out and objection deadlines, the final approval hearing, the fund and class size when stated, the case, court, administrator and its contact, and the source page for each. Pass the slug from find_breach_settlement or list_open_breach_settlements.
Annotations the server declares
- title: Settlement details
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
Only reads 2Show 2 read-only tools
find_breach_settlementFor 'I got a data breach notice from X', 'am I owed money from the X data breach', 'is there a settlement for X', 'how do I claim the X settlement', 'is this settlement letter real…Reads text others writeNo findings
Why it is in this group
- The name "find_breach_settlement" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it For 'I got a data breach notice from X', 'am I owed money from the X data breach', 'is there a settlement for X', 'how do I claim the X settlement', 'is this settlement letter real'. Matches the company against open class-action data-breach and privacy settlements, each read off its official court-authorized website: the claim deadline and days left, what it pays (documented losses up to $X, cash payment, credit monitoring), the class definition verbatim so the person can see if they are in it, whether the code printed on the notice letter is needed, the case and court, the official claim site, and a link to a page with their claim checklist filled in. If no settlement is open it says so, and lists the breach notices on public record (California and Washington AG) so the person knows the breach is real and to keep the letter. It takes the company name only: no Social Security number, notice ID, claim ID or name is needed or taken. This tool never files a claim; the person files on the official site and signs it themselves.
Annotations the server declares
- title: Find a breach settlement
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
list_open_breach_settlementsEvery open class-action data-breach (and privacy/tracking-pixel) settlement we have read off its official website, sorted by claim deadline: company, deadline and days left, the mo…Reads text others writeNo findings
Why it is in this group
- The name "list_open_breach_settlements" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
Description, as the server wrote it Every open class-action data-breach (and privacy/tracking-pixel) settlement we have read off its official website, sorted by claim deadline: company, deadline and days left, the most cash it pays, whether receipts are needed, and the official site. Use for 'what data breach settlements can I claim right now', 'which settlements close this week', 'data breach settlements with no proof required'. Refreshed daily; each row says when its official site was last read.
Annotations the server declares
- title: List open settlements
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- 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 20, 2026, 18:19 UTC, unchanged since Nov 20, 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
- 1
- 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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://breach-to-claim.vercel.app/mcp: tools/list returned 3 tools to an anonymous client, including breach_settlement_details (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http breach-to-claim https://breach-to-claim.vercel.app/mcpclaude mcp add --transport http breach-to-claim https://breach-to-claim.vercel.app/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": [
"mcp__breach-to-claim__find_breach_settlement",
"mcp__breach-to-claim__list_open_breach_settlements"
],
"ask": [
"mcp__breach-to-claim__breach_settlement_details"
],
"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 breach-to-claim. Review it before you use it.
Capability tags behind 3 rules
- mcp__breach-to-claim__find_breach_settlement untrusted-input
- mcp__breach-to-claim__list_open_breach_settlements untrusted-input
- mcp__breach-to-claim__breach_settlement_details untrusted-input
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/io.github.2016judea/breach-to-claim/verify?hash=3883e5ba66c69723dc57f314778dcf9aa547189d0c985234fe55d419d0144549" | jq -e '.changed == false'Pinned hash 3883e5ba66c6, from Nov 19, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.2016judea/breach-to-claim/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.2016judea/breach-to-claim)Source: MCP Registry · repository. Synced Nov 19, 2026, 23:17 UTC.
Breach to Claim: data breach settlements MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Breach to Claim: data breach settlements MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Breach to Claim: data breach settlements MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Breach to Claim: data breach settlements 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 Breach to Claim: data breach settlements MCP server have?
- 3 tools: 1 write, 2 read. breach_settlement_details, find_breach_settlement and list_open_breach_settlements.
Does the Breach to Claim: data breach settlements MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Breach to Claim: data breach settlements MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Breach to Claim: data breach settlements MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.