Remote MCP · Endpoint
LeakData MCP server
No. LeakData answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://leakdata.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.leakdatahq/leakdata-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 680 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Check breach exposure for your verified email and check locally computed password hash prefixes.
- Website
- https://leakdata.io/docs
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 680 ms |
| 2 days ago | Handshake completed | 543 ms |
| 4 days ago | Handshake completed | 612 ms |
| 5 days ago | Handshake completed | 588 ms |
| 7 days ago | Handshake completed | 782 ms |
| 8 days ago | Handshake completed | 568 ms |
| 9 days ago | Handshake completed | 596 ms |
| 12 days ago | Handshake completed | 611 ms |
| 13 days ago | Handshake completed | 659 ms |
| 15 days ago | Handshake completed | 586 ms |
| 17 days ago | Handshake completed | 574 ms |
| 18 days ago | Handshake completed | 566 ms |
| 19 days ago | Handshake completed | 175 ms |
| 20 days ago | Handshake completed | 586 ms |
| 20 days ago | Handshake completed | 529 ms |
| 21 days ago | Handshake completed | 546 ms |
| 23 days ago | Handshake completed | 612 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 LeakData and makes no claim about it beyond what these checks measured.