# LeakData (remote · leakdata.io)

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

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `leakdata.io`: 75/100 (this document), [markdown](https://verifymcp.io/servers/leakdatahq-leakdata-mcp/leakdata.md), [page](https://verifymcp.io/servers/leakdatahq-leakdata-mcp/leakdata)

## Channel facts

- Endpoint: `https://leakdata.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http leakdatahq-leakdata-mcp 'https://leakdata.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "leakdatahq-leakdata-mcp": {
      "url": "https://leakdata.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "leakdatahq-leakdata-mcp": {
      "type": "http",
      "url": "https://leakdata.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.leakdatahq-leakdata-mcp]
url = "https://leakdata.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "leakdatahq-leakdata-mcp": {
      "type": "remote",
      "url": "https://leakdata.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add leakdatahq-leakdata-mcp --url 'https://leakdata.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  leakdatahq-leakdata-mcp:
    url: "https://leakdata.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "leakdatahq-leakdata-mcp": {
      "Transport": "http",
      "Url": "https://leakdata.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add leakdatahq-leakdata-mcp -t streamable-http -u 'https://leakdata.io/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 75, +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.

### 2026-09-16 (score 74, +1)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20

### 2026-09-15 (score 73, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-14 (score 73, +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.

### 2026-09-12 (score 72, +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.

### 2026-09-11 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-10 (score 71)

First indexed and scored.

## MCP tools (2)

### `leakdata.search` (~199 tokens)

Check your verified email

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.

Input parameters:

- `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, required)

Output parameters:

- `breachCount` (integer)
- `breaches` (array)
- `found` (boolean)
- `truncated` (boolean)
- `type` (string)

### `leakdata.password_prefix_check` (~170 tokens)

Check a password hash prefix

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.

Input parameters:

- `prefix` (string, required): Five-character SHA-1 hash prefix supplied in the current user message. Never infer it from earlier messages.

Output parameters:

- `candidateHashCount` (integer): Number of distinct known hashes sharing the prefix, not matches for one specific password.
- `found` (boolean): Whether any known hashes share this five-character prefix. A match does not establish that a particular password is exposed.
- `totalOccurrences` (integer): Total occurrences across all hashes in the prefix group, not an exposure count for one specific password.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/leakdatahq-leakdata-mcp/leakdata#diagnostics

## Score history

- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 75
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://leakdata.io/mcp
- Website: https://leakdata.io/docs
- Changelog RSS feed: https://verifymcp.io/servers/leakdatahq-leakdata-mcp/leakdata.xml
- Changelog JSON feed: https://verifymcp.io/servers/leakdatahq-leakdata-mcp/leakdata.json
- HTML version of this page: https://verifymcp.io/servers/leakdatahq-leakdata-mcp/leakdata