LeakData
REMOTE · LEAKDATA.IO · SCANNED SEP 20
Check breach exposure for your verified email and check locally computed password hash prefixes.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 369 tokens (~184/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the LeakData MCP server?
LeakData is a hosted endpoint at https://leakdata.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · leakdata.io
claude mcp add --transport http leakdatahq-leakdata-mcp 'https://leakdata.io/mcp'
{
"mcpServers": {
"leakdatahq-leakdata-mcp": {
"url": "https://leakdata.io/mcp"
}
}
} {
"servers": {
"leakdatahq-leakdata-mcp": {
"type": "http",
"url": "https://leakdata.io/mcp"
}
}
} [mcp_servers.leakdatahq-leakdata-mcp] url = "https://leakdata.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"leakdatahq-leakdata-mcp": {
"type": "remote",
"url": "https://leakdata.io/mcp",
"enabled": true
}
}
} openclaw mcp add leakdatahq-leakdata-mcp --url 'https://leakdata.io/mcp' --transport streamable-http
mcp_servers:
leakdatahq-leakdata-mcp:
url: "https://leakdata.io/mcp" {
"McpServers": {
"leakdatahq-leakdata-mcp": {
"Transport": "http",
"Url": "https://leakdata.io/mcp"
}
}
} assistant mcp add leakdatahq-leakdata-mcp -t streamable-http -u 'https://leakdata.io/mcp'
{
"mcpServers": {
"leakdatahq-leakdata-mcp": {
"type": "http",
"url": "https://leakdata.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- 15 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Sept 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://leakdata.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=leakdata.io | CN=WE1,O=Google Trust Services,C=US | 25 Jul 2026 | 23 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 8976863b0078934f0e0ba72eb331fd07 |
| SANs: leakdata.io, *.leakdata.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of leakdata.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| leakdata.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net https://unpkg.com https://static.cloudflareinsights.com https://challenges.cloudflare.com https://www.googletagmanager.com blob:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https: blob:; frame-src https://challenges.cloudflare.com https://www.google.com; worker-src 'self' blob:; connect-src 'self' https://www.google-analytics.com https://*.google-analytics.com https://analytics.google.com https://*.analytics.google.com https://www.googletagmanager.com https://*.googletagmanager.com https://stats.g.doubleclick.net https://www.google.com https://api.eu.amplitude.com https://api-sr.eu.amplitude.com https://static.cloudflareinsights.com ws: wss:; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://leakdata.io/mcp | Verified | 200 | |
| http (plaintext) | http://leakdata.io/mcp | HTTPS enforced | 301 | https://leakdata.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
leakdata.password_prefix_check Check a password hash prefix ~170
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 hexadecimal characters without calling a tool. Never accept a plaintext password or complete hash. Report only the aggregate values actually returned by this call. Results describe a prefix group only. A matching prefix does not establish whether a particular password is exposed. Do not report confirmed password exposure or recommend changing a password based only on this result. An empty group does not prove that a password is safe.
| Name | Type | Req | Description |
|---|---|---|---|
| prefix | string | yes | Five-character SHA-1 hash prefix supplied in the current user message. Never infer it from earlier messages. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidateHashCount | integer | yes | Number of distinct known hashes sharing the prefix, not matches for one specific password. |
| found | boolean | yes | Whether any known hashes share this five-character prefix. A match does not establish that a particular password is exposed. |
| totalOccurrences | integer | yes | Total occurrences across all hashes in the prefix group, not an exposure count for one specific password. |
No examples provided.
leakdata.search Check your verified email ~199
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 an address, set type to email and omit query: the server resolves the verified primary email from the linked account. If the user supplies an email address, preserve it in query for ownership validation. Never guess an email address or recover it from earlier conversations when query can be omitted. Domain checks are not available through this app; explain this without calling a tool. Arbitrary third-party identifiers, usernames, phone numbers, raw leak records, and credentials are not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Omit for the linked account's verified primary email. If an email is supplied, it must match that verified primary email. |
| type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| breachCount | integer | yes | – |
| breaches | array | yes | – |
| found | boolean | yes | – |
| truncated | boolean | yes | – |
| type | string | yes | – |
No examples provided.
What is the LeakData MCP server?
LeakData is an MCP server listed in the public MCP registry as io.github.leakdatahq/leakdata-mcp. Check breach exposure for your verified email and check locally computed password hash prefixes. This page covers its hosted endpoint (https://leakdata.io/mcp).
Is the LeakData MCP server safe to use?
LeakData scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LeakData MCP server expose?
LeakData exposes 2 tools: leakdata.search, leakdata.password_prefix_check. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.
Does the LeakData MCP server require authentication?
No. We connected to LeakData without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LeakData MCP server still maintained?
LeakData is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.