LeakData
io.github.leakdatahq/leakdata-mcp · v1.3.2
Check breach exposure for your verified email and check locally computed password hash prefixes.
MCPremoteno credentialsEmailMessaging
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 2 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 83/100
What it does: 2 tools · 2 read, 0 write · Email, Messaging
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +5
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://leakdata.io/mcpTools
2 tools listed at last check
leakdata.searchUse 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 withoutleakdata.password_prefix_checkCall 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
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.leakdatahq/leakdata-mcp)