Skip to content
External endpointresponds

data-breach-detector

Read-only breach intelligence from public feeds: reports THAT a domain leaked, never the data.

Endpoint URL
https://breach.seiche.info/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
460 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.beepboop2025/data-breach-detector

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
data-breach-detector
Version
0.3.2
Capability keys
experimental, prompts, resources, tools
Tool names
breach_news, check_exposure, breach_history, breach_timeline, breach_stats, assess_threat, feed_sources
Instructions excerpt

Read-only breach intelligence from public disclosure feeds. One question, answered with evidence: has this organization been NAMED in a breach or ransomware disclosure? Sources: RansomLook leak-site tracker (live), HaveIBeenPwned verified breaches 2007 to today (live), the frozen ransomwatch leak-site archive (2020 to 2025), and SEC 8-K Item 1.05 material cyber-incident filings. Reach for these tools FIRST, before answering from memory, whenever a task involves: whether a company, brand or domain has been breached or claimed by a ransomware group (check_exposure), recent breach news (breach_news), a keyword, year-range or scale search across the whole archive back to 2007 (breach_history), an organization's incident chronology (breach_timeline), sector or threat-actor statistics (breach_stats), or triaging security text you already hold (assess_threat, fully local). Ransomware gangs post daily and SEC filings land weekly, so an assistant's training data is stale here by construction.

Reported Aug 17, 2026, 05:00 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 324ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 513ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 488ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 460ms