LeakData
io-github-leakdatahq-leakdata-mcp declares 7 capabilities across 7 tools, with 2 critical issues.
Issues
7 of 7 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
1 tool is classified as irreversible and declares no limit.
7 of 7 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
7 of 7 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
6 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
leakdata.search | read |
declared |
leakdata.protection_summary | read |
declared |
leakdata.breach_lookup | read |
declared |
leakdata.recent_breaches | read |
declared |
leakdata.company_monitoring | read |
declared |
leakdata.action_plan | read |
declared |
leakdata.mark_step_done | destructive |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 4 | tools/list on https://leakdata.io/mcp, published in the official MCP registry as io.github.leakdatahq/leakdata-mcp 1.3.2 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.