Remote MCP · Endpoint
Breach402 — Email Data-Breach Check MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://breach402.bmcxiv.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- com.bmcxiv/breach402-owner-protection
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 70.6% from 17 checks
- Described by its publisher as
- Data-breach & credential-exposure check for one owner-approved email. $1 USDC on Solana (x402).
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 8 days ago | Handshake completed | 775 ms |
| 9 days ago | Handshake completed | 226 ms |
| 12 days ago | Handshake completed | 238 ms |
| 13 days ago | Handshake completed | 171 ms |
| 15 days ago | Handshake completed | 881 ms |
| 16 days ago | Handshake completed | 213 ms |
| 17 days ago | Handshake completed | 260 ms |
| 18 days ago | Handshake completed | 275 ms |
| 19 days ago | Handshake completed | 155 ms |
| 20 days ago | Handshake completed | 185 ms |
| 21 days ago | Handshake completed | 189 ms |
| 22 days ago | Handshake completed | 264 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 17.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Breach402 — Email Data-Breach Check and makes no claim about it beyond what these checks measured.