Claude custom connector

Check your email exposure with Claude

Connect Claude to check breach exposure for your LeakData account's verified primary email, or check a locally computed password hash prefix.

Status
Validation pending; not listed in the Connectors Directory.
LeakData access
Your primary email verified. Every plan includes the connector with a daily request limit.
Provider
A Claude account or workspace that allows custom connectors; workspace policy may require admin approval.
Add to Claude Read the documentation
  • Read-only tools
  • Consent-based OAuth
  • No raw leak records

Claude validation is pending

Live Claude testing is still in progress. This connector is not listed in Anthropic's Connectors Directory.

How it works

A narrow connection you control

Claude discovers two read-only tools and sends you to LeakData to sign in and give explicit consent.

  1. 01

    Add the server

    Review the prefilled LeakData.io name and https://leakdata.io/mcp server URL in Claude before adding the custom connector.

  2. 02

    Approve the scopes

    Sign in only on LeakData.io and approve the search and password-check scopes shown on the consent screen.

  3. 03

    Ask within the boundary

    Check your verified primary email or a five-character SHA-1 hash prefix you computed locally. Domain searches are not available.

Tools

Two focused, read-only operations

The connector does not expose a catch-all request tool, resources, prompts, browser controls, or account-changing actions.

leakdata.search

Check your verified email

Returns a brief exposure summary for the linked account's verified primary email. Domain searches are not available through this connector.

scope: search
leakdata.password_prefix_check

Check a hash prefix

Accepts exactly five hexadecimal characters from a SHA-1 hash computed locally. It never accepts a plaintext password or a complete hash.

scope: password-check

What the connector can return

  • Breach source summaries for your verified primary email
  • Hash counts and recorded occurrences in a five-character prefix group
  • Clear no-match results, without treating them as a guarantee of safety

What stays unavailable

  • Raw leak records, plaintext passwords, complete hashes, credentials or tokens
  • Domain searches and checks on third-party emails, usernames or phone numbers
  • Actions that change accounts, send notifications, purchase services or modify files
Setup

Connect from Claude

A LeakData account with a verified primary email is required. Every plan, including Free, can connect, with a daily request limit.

  1. 1

    Open the prefilled Claude connector form and verify the server URL is exactly https://leakdata.io/mcp.

  2. 2

    Add the connector, select Connect, and continue to LeakData.io for authentication.

  3. 3

    Review the requested scopes and approve only when they match the operation you intend to use.

  4. 4

    Enable LeakData.io in a conversation, and disconnect it from Claude when access is no longer needed.

Review the connection before granting access

The install link only prefills the public server name and URL. Claude still asks you to confirm the connector and complete LeakData OAuth consent.

Add to Claude