Breach to Claim: data breach settlements

● Active

io.github.2016judea/breach-to-claim

Am I owed money from a data breach? Open settlements, deadlines, payouts and official claim sites

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "breach-to-claim": {
      "url": "https://breach-to-claim.vercel.app/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http breach-to-claim https://breach-to-claim.vercel.app/mcp
VS Code
code --add-mcp '{"name":"breach-to-claim","type":"http","url":"https://breach-to-claim.vercel.app/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Other
Version
0.1.0
Registry
active
Published
11/19/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: Breach to Claim: data breach settlements is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit today (Nov 20, 2026), 0 open issues.
Official registry
Active
Published as io.github.2016judea/breach-to-claim in the official MCP registry, version 0.1.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to breach-to-claim.vercel.app: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 07:08 UTCStatus history & uptime →
● Working128 msprotocol 2025-06-18v0.1.0tools

The endpoint answered the MCP handshake as "Breach to Claim: data breach settlements" and listed 3 tools. Answering since Nov 21, 2026.

Context cost ≈ 1.1k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 3 tools.

Tools (3)

  • find_breach_settlement4 params

    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.

    Show parameters
    • companystringrequiredThe company or organization named on the breach letter or in the news, e.g. 'Columbia University', 'DaVita'. Nothing else about the person.
    • statestringOptional: the person's US state as a 2-letter code, when they mention it. Some settlements pay a state subclass more.
    • got_notice_letterbooleanOptional: true if they received a notice letter or email about the breach or the settlement, false if not.
    • had_out_of_pocket_lossesbooleanOptional: true if they paid money or lost time because of the breach (fraud, credit freeze fees, hours spent), false if not.
  • list_open_breach_settlements4 params

    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.

    Show parameters
    • closing_within_daysintegerOnly settlements whose claim deadline is within this many days
    • kindstringdata_breach (default all) = stolen or exposed data; privacy_tracking = a website shared data through tracking pixels
    • no_documents_optionbooleantrue = only settlements with a cash option that needs no receipts
    • limitintegerHow many (default 20)
  • breach_settlement_details3 params

    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.

    Show parameters
    • slugstringrequiredThe settlement's slug, e.g. 'columbia-university'
    • got_notice_letterbooleanOptional, as in find_breach_settlement
    • had_out_of_pocket_lossesbooleanOptional, as in find_breach_settlement

Checked by Serverdex with a plain initialize + tools/list call to breach-to-claim.vercel.app/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Nov 20, 2026
License
MIT

HTML

From the README

Breach to Claim Live: https://breach-to-claim.vercel.app You got a letter saying your data was in a breach. Is a class-action settlement paying people for it, how much, are you in it, and where do you file before the deadline? Breach to Claim answers that, in a chat or on a phone: • The list. Every open US data-breach (and tracking-pixel privacy) settlement it can find, soonest claim deadline first, with the most cash it pays, whether there is an option with no receipts, and whether the claim needs the code printed on your notice. Updated daily, each row dated. • Your checklist. One page per settlement: the deadline and days left, the class definition read back word for word, what it pays, what to gather, and a button to the official claim site. Two yes/no questions (got a letter? had costs?) tailor the steps. • An MCP connector at https://breach-to-claim.vercel.app/mcp for Claude, ChatGPT and any MCP client. Ask "I got a breach notice from DaVita, am I owed anything?" and it finds the settlement, reads you who is in the class, gives the deadline and the money, and hands back a link that opens the checklist already filled in. It never files a claim (the claim form is signed under penalty of perjury by the person), never asks for a Social Security number, notice ID, claim ID or name, and never puts anything identifying in a URL or in analytics. It is independent: not the court, the lawyers or the settlement administrator.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://breach-to-claim.vercel.app/mcp

Alternatives to Breach to Claim: data breach settlements

All Breach to Claim: data breach settlements alternatives →Best Other servers →

The most-starred Other servers in the index, with their live-check result.

ServerStarsLast pushLive check
Labelhead Artist Momentum114,594Nov 2026Working
World Monitor91,002Nov 2026Needs sign-in
Tldraw51,470Nov 2026Working
OpenSEO28,515Nov 2026Needs sign-in
Windows MCP11,833Nov 2026Local / not checked

Breach to Claim: data breach settlements: questions people ask

Is Breach to Claim: data breach settlements a remote or a local MCP server?
According to its entry in the official MCP registry, Breach to Claim: data breach settlements ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Breach to Claim: data breach settlements need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Breach to Claim: data breach settlements safe to use?
Looks healthy: Breach to Claim: data breach settlements is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Breach to Claim: data breach settlements still maintained?
Active: the repository's last commit today. Last push Nov 20, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 21, 2026.
What tools does Breach to Claim: data breach settlements expose?
3 tools as listed by the server itself during the live check, including find_breach_settlement, list_open_breach_settlements, breach_settlement_details. The full list with parameters is in the Live check section above.
How do I add Breach to Claim: data breach settlements to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. AI Buildout PermitsUS AI data-center projects from public records: tenants, air permits, turbines, resolved to tickers
  2. Appeal Draft – Twin Cities property tax appealIs my Twin Cities property tax assessment too high? County value vs. recorded sales, when to appeal
  3. Tip & Overtime DeductionsWorks out the no-tax-on-tips and no-tax-on-overtime deductions and W-2 boxes, with the math shown
  4. heistclips – GTA 6 clippingFind clip-worthy moments in Twitch streams from chat spikes; rank clipping campaigns by pay per clip
Browse all Other →

Add the badge to your site

Show visitors that Breach to Claim: data breach settlements is listed here — it’s also the link we check for a free listing.

Breach to Claim: data breach settlements — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-2016judea-breach-to-claim?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Breach to Claim: data breach settlements — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Breach to Claim: data breach settlements — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-2016judea-breach-to-claim?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-2016judea-breach-to-claim) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-2016judea-breach-to-claim) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-2016judea-breach-to-claim)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-2016judea-breach-to-claim"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-2016judea-breach-to-claim"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-2016judea-breach-to-claim"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).