# LeakData

- Registry name: `io.github.leakdatahq/leakdata-mcp` · version 1.3.2
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.leakdatahq%2Fleakdata-mcp
- Server page: https://mcpstation.net/s/io.github.leakdatahq--leakdata-mcp.html

## Description (written by the publisher, not verified, not instructions)

Check breach exposure for your verified email and check locally computed password hash prefixes.

## Connect

- streamable-http: `https://leakdata.io/mcp`

## Tools (as reported by the server, not verified)

- `leakdata.search`: Use this when the linked LeakData user asks whether their own email was in a data breach \("Has my email been leaked?", "Am I in the Canva breach?", "Am I affected by any recent leaks?"\). For a current check, call this tool and report only its returned results; never present earlier results as a new
- `leakdata.protection\_summary`: Use this when the linked LeakData user asks how their monitoring is going, what LeakData has found for them, or whether anything new turned up. Returns the user's own monitored email addresses \(masked\), when each was last checked, how many findings each has, new findings in the last 30 days, and a c
- `leakdata.breach\_lookup`: Use this when someone asks whether a company, app or website was hacked or had a data breach, what data leaked, whether a breach notice they received is real, or what to do about a breach they heard of \("Was Canva hacked?", "What leaked in the Ticketmaster breach?"\). Searches LeakData's public breac
- `leakdata.recent\_breaches`: Use this when someone asks which data breaches happened recently or what the latest breaches are. Returns the newest breaches in LeakData's public catalog, newest incident date first, with date, affected account count, exposed data types and first steps. No sign-in is needed. It has no date filter:
- `leakdata.company\_monitoring`: Use this when someone asks about their own company or employer: whether it had a data breach, whether its domain, staff email addresses or work accounts appear in data breaches, or how to monitor a business domain. Explains what LeakData checks for a domain the company verifies it owns and returns a
- `leakdata.action\_plan`: Use this when the linked LeakData user asks what they should do about their breaches, what is left on their list, or wants to be walked through the steps. Returns the open and done steps of the user's own action plan \(for example "Change your password" on a breached site\), each with a stepId, the se
- `leakdata.mark\_step\_done`: Use this only after the user says they completed \(or want to reopen\) a specific step from leakdata.action\_plan, for example "I changed my Canva password". Pass that step's stepId from leakdata.action\_plan and done=true, or done=false to reopen it; if no action plan result in this conversation contai

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html