data-breach-detector
v0.3.2Read-only breach intel, full history 2007-today: reports THAT an org was breached, never the data.
Endpoint health
online- Last checked
- 11/20/2026, 9:17:14 AM
- Latency
- 327 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.beepboop2025%2Fdata-breach-detector
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.beepboop2025/data-breach-detector": {
"url": "https://breach.seiche.info/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
7 shown · authentication unknown
assess_threat
Classify a piece of security text you supply — an advisory, alert or forum post — into a threat level, matched categories, financial-target flags, a confidence score and a recommended action. Pure local analysis: it collects nothing, stores nothing and reaches no network; the text never leaves the server. Use it to triage findings surfaced by breach_news or from your own monitoring.
Schema valid · SHA-256 866a15419afc…
View input schema
{ "type": "object", "properties": { "text": { "description": "the security text to classify — an advisory, alert or forum post", "title": "Text", "type": "string" } }, "required": [ "text" ], "title": "assess_threatArguments" }breach_history
Search the FULL historical breach archive — every incident this server knows about, back to 2007: HaveIBeenPwned's verified breach directory, the 2020-2025 ransomwatch leak-site archive (~16k victims), the RansomLook live tracker and SEC 8-K Item 1.05 filings. Filter by keyword, year range, sector, exposed data type or minimum scale; order by date or size. Returns disclosure metadata only, never breach contents. Use this for questions like 'what were the biggest breaches of 2013' or 'which airlines have ever been hit by ransomware'.
Schema valid · SHA-256 94b5f131ad47…
View input schema
{ "type": "object", "properties": { "query": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "description": "optional keyword over entity, title, summary, actor and data types; omit to browse the whole archive", "title": "Query" }, "year_from": { "anyOf": [ { "minimum": 2000, "type": "integer" }, { "type": "null" } ], "default": null, "description": "earliest incident year to include, e.g. 2013", "title": "Year From" }, "year_to": { "anyOf": [ { "minimum": 2000, "type": "integer" }, { "type": "null" } ], "default": null, "description": "latest incident year to include, e.g. 2020", "title": "Year To" }, "sector": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "description": "industry keyword filter, e.g. 'bank', 'health', 'gaming'", "title": "Sector" }, "data_type": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "description": "require an exposed data type, e.g. 'passwords', 'credit card', 'health'", "title": "Data Type" }, "min_accounts": { "default": 0, "description": "only incidents exposing at least this many accounts", "minimum": 0, "title": "Min Accounts", "type": "integer" }, "order": { "default": "newest", "description": "'newest' (default), 'oldest' or 'largest' (by accounts exposed)", "title": "Order", "type": "string" }, "limit": { "default": 10, "description": "maximum incidents to return (default 10; raise it deliberately, large pages are heavy for an agent loop)", "maximum": 100, "minimum": 1, "title": "Limit", "type": "integer" }, "offset": { "default": 0, "description": "how many matching incidents to skip before the page starts; count can run to five figures over the ~16k-post archive, so this is how the tail is reached", "minimum": 0, "title": "Offset", "type": "integer" } }, "title": "breach_historyArguments" }
Connections
streamable-http
https://breach.seiche.info/mcp