AI integrations
The MCP (Model Context Protocol) server connects your assistant to LeakRadar to search, monitor and unlock results with your account.
No API key to copy
Connect your assistant
Choose your client to see its configuration.
https://mcp.leakradar.io/mcp
You need a LeakRadar account and a client that supports remote MCP with OAuth. Features depend on your LeakRadar plan and your assistant or workspace settings.
Claude
In Claude on the web or Desktop, open Customize > Connectors > Add custom connector. Name it LeakRadar and paste the server URL. Choose OAuth and, if asked for an OAuth client, Register automatically. Connect, then enable the connector in your conversation.
When redirected, sign in to LeakRadar, review the requested access and approve. Return to your assistant to finish. Never paste your password or a token into the conversation.
Official client guideTry your first request
Check your plan, points and quotas first, without unlocking results.
Use LeakRadar to show my plan, points balance and current quotas. Do not unlock or change anything.
Requests to try
With LeakRadar, summarize exposure for my authorized domain example.com by category, without unlocking results.
With LeakRadar, list my monitors and summarize their latest alerts, without changing them or spending points.
With LeakRadar, prepare to unlock at most 10 results from the last search on my authorized domain. Show the selected results and cost, then wait for my approval before unlocking them.
Help with the connection
The connector acts on your behalf, within your account permissions. Access is granted as a whole; the categories below are explanations, not separate permission switches.
Search and read
Exposure, searches, profile, monitors, alerts and job status. Reads spend no points, remain subject to quotas and show masked credentials unless already unlocked.
Unlock with points
Unlock results with an explicit maximum. Points may be used depending on your plan; reads never unlock automatically.
Export and download
Queue exports and retrieve download links. Export and raw download allowances depend on your plan, unlocked data and any applicable GB balance.
Create and modify
Manage monitors, alert channels, lists, statuses and profile fields exposed by the public API. Auto-unlock monitors require a points budget.
Delete and revoke
Delete monitors, channels, lists or comments, revoke invitations and manage team access where your account permits it.
Send messages
Test alert channels and send or resend team invitations. These actions can notify other people.
The connector instructs the assistant to ask before spending, exporting, changing, deleting or sending. Actual approval prompts depend on your client settings; the server does not enforce a separate human approval for every action.
Revoke access at any time from LeakRadar > Settings > MCP > Connected applications. Data already shared with your assistant remains subject to that provider’s policies.
Reconnect from your assistant and sign in to the correct LeakRadar environment. A 401 can indicate expired or revoked access. Restart an invalid authorization request from the assistant.
Check your LeakRadar plan with account_status. Masked results need unlocking; a 402 indicates insufficient points or GB, and a 403 can indicate an account or plan restriction.
On a 429, respect Retry-After before retrying and reduce concurrent requests. Use smaller pages. Do not repeatedly replay failing requests.
Check client and workspace permissions, enable LeakRadar in the conversation and refresh its tools. Remote clients need to reach the MCP and OAuth endpoints; a VPN-only service or Cloudflare login challenge can block them.