data-breach-detector
Read-only breach intel, full history 2007-today: reports THAT an org was breached, never the data
Reviews
No review yet. Used data-breach-detector? Be the first to help others choose.What it does
data-breach-detector is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://breach.seiche.info/mcpstreamable-http
In Claude Code: claude mcp add --transport http data-breach-detector https://breach.seiche.info/mcp
Install package
- PYPI
data-breach-detectorv0.3.1 · runs locally (stdio)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"data-breach-detector": {
"url": "https://breach.seiche.info/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE data-breach-detector answered an MCP connection on 16 Nov 2026 and introduced itself as data-breach-detector 0.3.2 (MCP protocol 2025-06-18).
7 tools offered to AI assistants
breach_news· Read recent breach and ransomware DISCLOSURES from public threat-intel feeds (HaveIBeenPwned, the RansomLook live leak-site tracker and SEC 8-K Item 1.05 filings), newest first. Every row is metadata only — entity, date, scale, exposed datacheck_exposure· Answer whether a domain, company or brand appears in public breach or ransomware DISCLOSURES across ALL history (2007 → today): yes/no with mention count, worst threat level, total accounts exposed across matches, the exposed data TYPES, anbreach_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-breach_timeline· Build the incident-by-incident CHRONOLOGY of one organization across every source and all history, with judgment on top: first and latest incident, incidents per year, whether the organization is a repeat victim, worst threat level and totabreach_stats· Aggregate the full breach archive into analyst-grade statistics: incidents and accounts exposed per year, per source, per exposed data type, per threat level, or per ransomware actor — plus the five largest incidents ever recorded. Use it tassess_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, storesfeed_sources· List the public disclosure feeds this server aggregates, how many disclosures are cached per source, each source's newest item and an honest staleness flag, plus cache ages. Takes no arguments. Also states the scope plainly: public feeds on
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | data-breach-detector | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://breach.seiche.info/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Package registries | pypi | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/beepboop2025/data-breach-detector | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 0.3.2 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is data-breach-detector still online?
Free alerts · no account▲ 0Do you run data-breach-detector? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about data-breach-detector
How do I connect data-breach-detector?
Use the hosted endpoint https://breach.seiche.info/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does data-breach-detector offer?
When Electra Index connected on 16 Nov 2026, it listed 7 tools: breach_news, check_exposure, breach_history, breach_timeline, breach_stats, assess_threat, feed_sources. The full list is in "Live check" above.
Is data-breach-detector online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.