Connect-MCP

data-breach-detector

io.github.beepboop2025/data-breach-detector · v0.3.2

Read-only breach intel, full history 2007-today: reports THAT an org was breached, never the data.

MCPremotelocal · pypino credentialsSecurity

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 7 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 100/100

What it does: 7 tools · 7 read, 0 write · Security

Test call breach_news: worked (2,632 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://breach.seiche.info/mcp
Package
registry:   pypi
identifier: data-breach-detector
version:    0.3.1
transport:  stdio

Tools

7 tools listed at last check
  • 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 data TYPES, threat level and source — never the
  • check_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, and the matching disclosure metadata — never the
  • 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 ran
  • 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 total accounts ever exposed. Those summary fields
  • breach_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 to answer 'how has breach volume trended sinc
  • 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
  • feed_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 only — no .onion access, no arbitrary fetching or

Badge

Connect-MCP badge for io.github.beepboop2025/data-breach-detector

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.beepboop2025/data-breach-detector.svg)](https://clawy.uk/mcp/s/io.github.beepboop2025/data-breach-detector)

Repository