mcp-registry/io.github.leakdatahq/leakdata-mcp · v1.4.0
As of 2026-10-20 05:11 UTC, the Leakdatahq Leakdata MCP server is up with a Glimind reliability score of 73/100 (grade C). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 31 outages in 90 days, with a median recovery of 7 minutes.
Check breach exposure for your verified email and check locally computed password hash prefixes.
Claude Code
claude mcp add --transport http leakdatahq-leakdata-mcp-server https://leakdata.io/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"leakdatahq-leakdata-mcp-server": {
"type": "http",
"url": "https://leakdata.io/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
7 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~2,534 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 1 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.leakdatahq%2Fleakdata-mcp/fixes
{
"name": "leakdata_action_plan",
"description": "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 service it applies to, the masked monitored address and whether it is done. Walk the user through open steps one at a time, in the order returned (most urgent first). Report only the returned steps; nev",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"title": "Your action plan",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Your action plan"
}{
"name": "leakdata_breach_lookup",
"description": "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 breach catalog by company, service or domain name and returns each matching breach's date, affected account count, exposed data types, a short summary and the first steps to take. No sign-in is needed. It ",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Company, app, website or domain name, for example \"Canva\" or \"canva.com\". Never an email address, person's name or password."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Look up a data breach",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Look up a data breach"
}{
"name": "leakdata_company_monitoring",
"description": "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 any public catalog breaches listed for exactly that domain with their details. Explain setup using the returned checks and requirements; do not offer plans, prices or sales links. No sign-in is needed.",
"inputSchema": {
"type": "object",
"properties": {
"domain": {
"type": "string",
"maxLength": 253,
"minLength": 3,
"description": "The company domain the user gave, for example \"acme.com\". Omit when the user gave no domain; never infer it from a company name."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Understand company monitoring",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Understand company monitoring"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.leakdatahq/leakdata-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.leakdatahq/leakdata-mcp"}) over MCP.
leakdata.search ~256 tokensleakdata.mark_step_done ~241 tokensleakdata.breach_lookup ~237 tokensleakdata.company_monitoring ~232 tokensleakdata.recent_breaches ~205 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.leakdatahq%2Fleakdata-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.leakdatahq%2Fleakdata-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.leakdatahq%2Fleakdata-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.leakdatahq%2Fleakdata-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.leakdatahq%2Fleakdata-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8e842e1f9180d78d…, first seen 2026-10-19, included at leaf 28931 of 30,902. Version history · verify what your client received.
Compare: most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 05:11 UTC, the Leakdatahq Leakdata MCP server is up with a Glimind reliability score of 73/100 (grade C). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 31 outages in 90 days, with a median recovery of 7 minutes.
Leakdatahq Leakdata MCP server advertises 7 tools, including leakdata.action_plan, leakdata.breach_lookup, leakdata.company_monitoring, leakdata.mark_step_done, leakdata.protection_summary.
Point your MCP client at this streamable-http endpoint: https://leakdata.io/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.