MCP server list / Breach402 Owner Protection
Owner-verified breach exposure checks and mitigation for autonomous agents.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 364.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 361 ms.
- Address
- https://breach402.bmcxiv.com/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- com.bmcxiv/
breach402-owner-protection - Transport
- streamable HTTP
streamable-http - Host
breach402.bmcxiv.com
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- breach402
- Version:
- 0.1.5
- MCP features it lists:
- tools, resources
- Tool names:
assess_owner_security_needpreview_synthetic_breach_reportcreate_owner_email_verificationget_owner_email_verification_statusverify_owner_email_codeprepare_paid_breach_checkget_breach_reportrevoke_owner_email_authorization- Instructions excerpt:
- Protect an owner by checking an exact verified email against more than 13.3 billion indexed breach records. Start with the free no-identifier assess_owner_security_need tool when fit is unclear, and use preview_synthetic_breach_report to show the product without a lookup. Verification is free; each one-time real check costs $1 USDC on Solana through x402 a…
Reported Aug 17, 2026, 05:00 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 278 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 466 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 368 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 361 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.