Reverse Email Lookup with MCP

Paste an email into Claude or Cursor and the agent calls get_lead to name the person behind it. One URL, OAuth sign-in, 1 record per hit, nothing for a miss.

This page covers client setup and prompts. For the REST endpoint, field tables and coverage, see Reverse Email Lookup. Other clients are on the MCP hub. For tool comparisons, read the best reverse email lookup tools.

Connect the server

The server is https://api.leadocean.io/mcp. It signs in with OAuth 2.1, so there is no key to paste. Create a free account first.

Claude Code. The command format is from the Claude Code MCP docs, September 2026:

claude mcp add --transport http leadocean https://api.leadocean.io/mcp
claude mcp login leadocean

You can also run /mcp inside a session and finish the browser sign-in.

Cursor. Add a remote server to mcp.json, in the url form from the Cursor MCP docs, September 2026:

{
  "mcpServers": {
    "leadocean": {
      "url": "https://api.leadocean.io/mcp"
    }
  }
}

Cursor starts the sign-in the first time the server is used. Other clients follow the same pattern, see the LeadOcean MCP docs.

The tool

There is no tool named for reverse lookup. Use get_lead and pass email. The server lists it as leadocean_get_lead. It costs 1 record per call.

Send one identifier per call. The docs say sending two is a 400. The REST twin for email is GET /v2/people/reverse, which returns a thinner identity block.

Prompts that work

Put the record limit in the prompt. The agent holds a batch when you tell it where to stop.

Pass work addresses. The tool describes the email input as a work address, and the docs publish no match rate for webmail. Test a small sample before a large run.

What the agent gets back

get_lead returns one leadocean.person.v1 record plus a meta block. Shape from the enrich docs, September 2026. Values are placeholders.

{
  "person": {
    "profile_data": {
      "profile_full_name": "Jane Doe",
      "profile_headline": "Finance Manager at Acme",
      "profile_url": "https://www.linkedin.com/in/jane-doe"
    },
    "contact_data": {
      "has_email": true,
      "email_status": "verified",
      "contact_emails": [
        { "email": "jane.doe@acme.com", "type": "work", "status": "verified" }
      ],
      "contact_current_experiences": [{
        "company_name": "Acme",
        "company_domain": "acme.com",
        "job_title": "Finance Manager"
      }]
    }
  },
  "meta": { "source": "...", "schema": "leadocean.person.v1" }
}

contact_emails and contact_phones stay empty unless reveal_email is true. Unknown values are null. About one person in five has no LinkedIn URL, so tell the agent to report "no profile URL" rather than guess. Read email_status before anyone sends.

Free checks first

count_leads, list_enum_values and get_account spend no records. get_account shows your balance before a batch, and count_leads sizes an audience without pulling anyone.

count_leads counts mailable people (verified, catch_all_valid or catch_all) unless you widen it. We tried to run a fresh count for this page and the people-search source returned a 503, so there is no count here. Run your own and let the agent report the date.

Troubleshooting

FAQ