# Breach to Claim Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Breach to Claim

Check whether a data breach notice means you can file a claim, and what it pays

- Record: https://musedirectory.ai/connector/breach-to-claim
- Category: Legal
- Developer: 2016judea (https://breach-to-claim.vercel.app/connect/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 176ms, checked 2026-11-20T13:15:44Z
- Endpoint: https://breach-to-claim.vercel.app/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-19T22:31:32Z)
- Source: Found in the official MCP Registry (io.github.2016judea/breach-to-claim) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.2016judea%2Fbreach-to-claim

Connects to a daily-refreshed index of open data breach and privacy settlements read from their official court-authorized sites. Muse can match a company from a breach letter, show deadlines, payout types and class definitions, and point to the official claim page.

Example request: "I got a data breach letter from Columbia University, am I owed any money and how do I claim it?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Breach to Claim to help me. It is a free service with an MCP server at https://breach-to-claim.vercel.app/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- find_breach_settlement: 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 
- list_open_breach_settlements: 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 settl
- breach_settlement_details: 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 ca

Screening checks:
- MCP handshake: pass (Answered in 454ms)
- Domain against threat feeds (Cloudflare security DNS): pass (breach-to-claim.vercel.app not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (3 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 2487 days ago)
- AI review of purpose and tool behavior: pass (No concerns)
