mcp-registry/io.github.beepboop2025/data-breach-detector · v0.3.2
Also listed as glama/beepboop2025/data-breach-detector
As of 2026-10-18 14:41 UTC, the Beepboop2025 Data Breach Detector MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 2 minutes.
Read-only breach intel, full history 2007-today: reports THAT an org was breached, never the data.
Claude Code
claude mcp add --transport http beepboop2025-data-breach-detector-mcp-se https://breach.seiche.info/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"beepboop2025-data-breach-detector-mcp-se": {
"type": "http",
"url": "https://breach.seiche.info/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Handshake + tools/list takes ~1,931 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.beepboop2025/data-breach-detector"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.beepboop2025/data-breach-detector"}) over MCP.
breach_history ~622 tokensbreach_news ~459 tokenscheck_exposure ~372 tokensbreach_timeline ~338 tokensbreach_stats ~328 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.beepboop2025%2Fdata-breach-detector?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.beepboop2025%2Fdata-breach-detector?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.beepboop2025%2Fdata-breach-detector.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.beepboop2025%2Fdata-breach-detector.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.beepboop2025%2Fdata-breach-detector?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6643607ee65e136c…, first seen 2026-10-17, included at leaf 2515 of 22,335. Version history · verify what your client received.
Compare: most reliable security servers · most reliable search servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 14:41 UTC, the Beepboop2025 Data Breach Detector MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 2 minutes.
Beepboop2025 Data Breach Detector MCP server advertises 7 tools, including assess_threat, breach_history, breach_news, breach_stats, breach_timeline.
Point your MCP client at this streamable-http endpoint: https://breach.seiche.info/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.