beepboop2025-data-breach-detectorSAFE
Read-only breach intelligence for defenders: exposure checks, breach news, and threat assessment over MCP. Never leaked records.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A read-only breach-intelligence MCP server. It answers "has this organization ever been breached, what's the recent breach news, what does two decades of breach history look like, how severe is this threat text" from public disclosure feeds — and reports intelligence, not contents: the existence, timing, scale, category and exposed data-types of a breach, never the leaked records themselves.
Built for defenders and for agents that work on their behalf.
Why this instead of the alternatives
Most breach tooling sits in one of three camps, and each has a structural gap:
- Consumer checkers (HaveIBeenPwned's site) answer one question — "is my
email in a breach" — one account at a time, one source at a time.
- Leak-data brokers (DeHashed, IntelX, LeakCheck and the like) sell access
to the leaked records themselves. Wiring one into an AI agent hands the agent stolen credentials.
- Enterprise intel platforms (SpyCloud, Recorded Future, Flashpoint) do
the join properly — behind five-figure contracts and closed APIs.
This server takes a fourth position:
- Four primary sources, one queryable surface. The verified breach
directory (HIBP), a live ransomware leak-site tracker (RansomLook), a ~16k-victim leak-site archive back to 2020 (ransomwatch), and SEC 8-K Item 1.05 filings — companies' own legally mandated "material cybersecurity incident" disclosures. Regulator-grade and criminal-infrastructure-grade evidence in the same index. No key, no contract.
- History is first-class.
breach_history,breach_timelineand
breach_stats treat 2007→today as the product, not a cache: every breach of 2013, an organization's full incident chronology, repeat-victim flagging, per-year and per-actor aggregates.
- The ethical boundary is in the code, not the terms of service. No
fetch/crawl/proxy primitives, no .onion
7f540e51d435OBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add data-breach-detector -- None data-breach-detector==0.3.1
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (6 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (4)
"insider trading", "insider threat", "data exfiltration",
+ ""
+ ""
Gates applied: no_behavioural_pass.
7f540e51d435full audit observations/trust-audit/mcp-server/beepboop2025__data-breach-detector.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 7f540e51d435 | SAFE | B | 89 | first audit |
Questions
What is the beepboop2025-data-breach-detector MCP server?
Read-only breach intelligence for defenders: exposure checks, breach news, and threat assessment over MCP. Never leaked records.
Is beepboop2025-data-breach-detector safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does beepboop2025-data-breach-detector need?
No credential environment variables were found in its source, so it appears to need none.
How does beepboop2025-data-breach-detector run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on PyPI as data-breach-detector.
How current is this page?
The grade is for one exact copy of the source (7f540e51d435), read on 2026-10-10. The repository is watched and re-audited when it changes.