Security & Testing

leakdata.io

Checks LeakData breach intelligence to verify linked emails and test password SHA-1 hash prefixes.

1 endpoint2 known toolsFirst detected September 10, 2026Last detected September 10, 2026

ENDPOINT 1

https://leakdata.io/mcp

No auth detected

Capabilities

tools

Use this when the linked LeakData user asks to check their verified primary email.

Potential side effects

Call this only when the current user message supplies a locally computed five-character SHA-1 hash prefix and asks to check it.

Potential side effects

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.leakdata-io]
url = "https://leakdata.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "leakdata-io": {
      "type": "http",
      "url": "https://leakdata.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: leakdata-io
Remote MCP URL: https://leakdata.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "leakdata-io",
  "transport": "streamable-http",
  "url": "https://leakdata.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.