data-breach-detector MCP
A read-only MCP server providing breach intelligence for defenders. It aggregates public disclosure metadata from sources like HaveIBeenPwned, RansomLook, and SEC EDGAR to perform exposure checks, breach news retrieval, and threat assessment without exposing leaked records.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://breach.seiche.info/mcpWhat its tools do
7 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Check if a domain or company appears in breach data
- Search the full breach archive back to 2007
- Retrieve recent breach news and disclosures
- Classify security text for threat level and categories
Source and maintenance
- Maintenance checked
Protocol and capabilities
- Server
- data-breach-detector 0.3.2
- MCP protocol negotiated in check
- 2025-11-25
- Tools
- 7 advertised
- Resources
- 0 advertised
- Resource templates
- 0 advertised
- Prompts
- 2 advertised
{
"tools": {
"listChanged": false
},
"prompts": {
"listChanged": false
},
"resources": {
"subscribe": false,
"listChanged": false
},
"experimental": {}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
7 advertised
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 leaked data, and a redaction pass strips anything credential-shaped before it is returned. Use sector to narrow to an industry keyword; for one specific organization use check_exposure; for all-time history use breach_history.
{
"type": "object",
"title": "breach_newsArguments",
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 10,
"maximum": 100,
"minimum": 1,
"description": "maximum disclosures to return (default 10; raise it deliberately, large pages are heavy for an agent loop)"
},
"offset": {
"type": "integer",
"title": "Offset",
"default": 0,
"minimum": 0,
"description": "how many matching disclosures to skip before the page starts; with limit this walks a result set larger than any single page (count reports the full total)"
},
"sector": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Sector",
"default": null,
"description": "optional keyword filter over entity, title, summary, categories and exposed data types, e.g. 'bank', 'health', 'crypto'"
},
"source": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Source",
"default": null,
"description": "optional source filter: 'HaveIBeenPwned', 'RansomLook', 'ransomwatch-archive' or 'SEC EDGAR 8-K 1.05'"
},
"since_days": {
"type": "integer",
"title": "Since Days",
"default": 30,
"minimum": 1,
"description": "look-back window in days over disclosure dates (default 30)"
}
}
}{
"title": "Recent breach disclosures",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}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 exposed records themselves. This is a triage signal built from disclosure feeds, not proof of compromise; confirm through authorized channels before acting. For the incident-by-incident chronology of one entity, use breach_timeline; for a recent-news sweep, use breach_news. mentions, the aggregates and the data types always cover every match; matches carries one page of them, sized by limit and walked with offset.
{
"type": "object",
"title": "check_exposureArguments",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 8,
"maximum": 100,
"minimum": 1,
"description": "maximum matching disclosures to return (default 8; the mention count and the aggregates always cover every match)"
},
"query": {
"type": "string",
"title": "Query",
"description": "domain, company or brand to look up, e.g. 'example.com' or 'Acme'"
},
"offset": {
"type": "integer",
"title": "Offset",
"default": 0,
"minimum": 0,
"description": "how many matches to skip before the page starts; with limit this reaches matches beyond the first page"
},
"since_days": {
"type": "integer",
"title": "Since Days",
"default": 100000,
"minimum": 1,
"description": "optional look-back window in days; the default covers all history"
}
}
}{
"title": "Entity exposure check",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}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'.
{
"type": "object",
"title": "breach_historyArguments",
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 10,
"maximum": 100,
"minimum": 1,
"description": "maximum incidents to return (default 10; raise it deliberately, large pages are heavy for an agent loop)"
},
"order": {
"type": "string",
"title": "Order",
"default": "newest",
"description": "'newest' (default), 'oldest' or 'largest' (by accounts exposed)"
},
"query": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Query",
"default": null,
"description": "optional keyword over entity, title, summary, actor and data types; omit to browse the whole archive"
},
"offset": {
"type": "integer",
"title": "Offset",
"default": 0,
"minimum": 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"
},
"sector": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Sector",
"default": null,
"description": "industry keyword filter, e.g. 'bank', 'health', 'gaming'"
},
"year_to": {
"anyOf": [
{
"type": "integer",
"minimum": 2000
},
{
"type": "null"
}
],
"title": "Year To",
"default": null,
"description": "latest incident year to include, e.g. 2020"
},
"data_type": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Data Type",
"default": null,
"description": "require an exposed data type, e.g. 'passwords', 'credit card', 'health'"
},
"year_from": {
"anyOf": [
{
"type": "integer",
"minimum": 2000
},
{
"type": "null"
}
],
"title": "Year From",
"default": null,
"description": "earliest incident year to include, e.g. 2013"
},
"min_accounts": {
"type": "integer",
"title": "Min Accounts",
"default": 0,
"minimum": 0,
"description": "only incidents exposing at least this many accounts"
}
}
}{
"title": "Historical breach search",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}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 cover EVERY incident on record. The timeline list carries a window of them, oldest first within the window, defaulting to the most recent limit incidents and paging backwards with offset, so an organization with a long history shows its current state first rather than only its ancient one. Repeat victimhood is a forward-looking risk signal: organizations named more than once have demonstrably not closed the gap. Metadata only; never the leaked data. For a yes/no presence check use check_exposure.
{
"type": "object",
"title": "breach_timelineArguments",
"required": [
"entity"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 12,
"maximum": 100,
"minimum": 1,
"description": "how many incidents the timeline list carries (default 12); the counts, span and judgment always cover every incident"
},
"entity": {
"type": "string",
"title": "Entity",
"description": "domain, company or brand to build the chronology for, e.g. 'yahoo.com' or 'Adobe'"
},
"offset": {
"type": "integer",
"title": "Offset",
"default": 0,
"minimum": 0,
"description": "pages backwards through the chronology from the recent end: 0 gives the newest window, 12 gives the window before that"
}
}
}{
"title": "Entity breach timeline",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}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 since 2015', 'which ransomware groups have the most victims' or 'how often are passwords part of a breach'. Aggregate counts only; no leaked records.
{
"type": "object",
"title": "breach_statsArguments",
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 40,
"maximum": 500,
"minimum": 1,
"description": "how many buckets to return, largest first (default 40); buckets_total reports how many exist, and grouping by actor over the ~16k-post archive produces far more"
},
"sector": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Sector",
"default": null,
"description": "optional industry keyword filter applied before aggregating"
},
"group_by": {
"type": "string",
"title": "Group By",
"default": "year",
"description": "aggregation axis: 'year' (default), 'source', 'data_type', 'threat_level' or 'actor' (ransomware group)"
}
}
}{
"title": "Breach archive statistics",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}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.
{
"type": "object",
"title": "assess_threatArguments",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"title": "Text",
"description": "the security text to classify — an advisory, alert or forum post"
}
}
}{
"title": "Threat-text triage",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true
}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 crawling, no credential or PII output. Check this first if another tool's answer looks thin: a stale live feed is a finding, not background noise.
{
"type": "object",
"title": "feed_sourcesArguments",
"properties": {}
}{
"title": "Feed sources & health",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}Prompts
2 advertised
breach_check — Breach exposure check
Evidence-backed breach history for one organization: live leak-site claims, the 2007-to-today archive, and SEC 8-K cyber filings.
- organization
- No description (required)
vendor_risk_sweep — Vendor risk sweep
Screen a comma-separated list of vendors against public breach and ransomware disclosures, ranked worst first.
- vendors
- No description (required)
Resources
0 advertised
90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-06: 1 of 1 checks answered
- 2026-11-07: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 1066 ms
- 95th percentile latency
- 1066 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 1066 ms · metadata changed · 7 tool(s), 0 resource(s), 0 resource template(s), 2 prompt(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http data-breach-detector-mcp-seiche https://breach.seiche.info/mcpCodex
codex mcp add data-breach-detector-mcp-seiche --url https://breach.seiche.info/mcpCursor
{
"mcpServers": {
"data-breach-detector-mcp-seiche": {
"url": "https://breach.seiche.info/mcp"
}
}
}Cline
{
"mcpServers": {
"data-breach-detector-mcp-seiche": {
"type": "streamableHttp",
"url": "https://breach.seiche.info/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"data-breach-detector-mcp-seiche": {
"type": "http",
"url": "https://breach.seiche.info/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http data-breach-detector-mcp-seiche https://breach.seiche.info/mcpClaude Desktop
https://breach.seiche.info/mcpWindsurf
{
"mcpServers": {
"data-breach-detector-mcp-seiche": {
"serverUrl": "https://breach.seiche.info/mcp"
}
}
}Let your agent find its tools
Find servers like data-breach-detector MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.