io.github.leakdatahq/leakdata-mcp · v1.3.2 · communication
LeakData is healthy: it completed an MCP handshake in 4668 ms and exposes 2 tools. It scores 57/100.
Check breach exposure for your verified email and check locally computed password hash prefixes.
Endpoint: https://leakdata.io/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| health | 17 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 5 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 5 / 10 |
Scoring v0.3, computed 2026-10-15T04:45:49.261Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T04:45:40.108Z | Healthy | 4668 |
leakdata.search | Use this when the linked LeakData user asks to check their verified primary email. For a current check, call this tool and report only its returned results. Never present earlier conversation results as a new check; if the call fails, say the check could not be completed. For their own email without |
leakdata.password_prefix_check | Call this only when the current user message supplies a locally computed five-character SHA-1 hash prefix and asks to check it. Never invent a prefix or reuse one from an earlier message. For general questions about password checks, explain local SHA-1 computation and sharing only its first five hex |