FindLeadEmails MCP server

• create_jobwrite actionFree

  Queue a large list and return a job id. Reserves one credit per row up front and refunds what rows do not use. If the wallet cannot cover every row, the job is refused up front (no partial queue) with insufficient_credits and https://www.findleademails.com/pricing. Poll get_job_status, then page get_job_results. Each call creates a new job.

• find_emailwrite actionFree

  Find and verify one person's work email from their name and company domain, or from a LinkedIn company page URL when you do not have the domain. Costs 1 credit only when the result is verified. Misses, catch-alls, and cached repeats are free and still return at 0 credits. A billable result fails at 0 balance; the error includes https://www.findleademails.com/pricing. This stores the lookup. It does not delete or modify the person's data.

• find_emails_bulkFree

  Find and verify emails for up to 100 people. Use create_job for a larger list. 1 credit per verified result. Free outcomes still return at 0 credits. Rows run until a billable result cannot be paid for; later rows are skipped with insufficient_credits and https://www.findleademails.com/pricing. This stores the lookups. It does not delete data.

• get_job_resultsFree

  Read one page of a job's per-row results. Readable while the job is still running. Pass cursor back as the next cursor until next_cursor is null. Does not spend credits and does not change the job.

• get_job_statusFree

  Read progress and per-outcome counters for a job created with create_job. Does not spend credits and does not change the job.

• verify_emailwrite actionFree

  Check whether one email address is a real mailbox. Costs 1 credit only when the mailbox is confirmed valid. Invalid, catch-all, unknown, and repeats are free and still return at 0 credits. A new valid mailbox fails at 0 balance; the error includes https://www.findleademails.com/pricing. The credit is spent after a valid result. This does not modify the mailbox.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1189ms20/20
• Tool poisoning6 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 8 days ago15/15
• Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10

Safety score

89/100

higher than 83% of 916 Email servers

Tools

6

the typical Email server has 7

Tools that change things

50%

typical: 25%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Email server answers 100%

Response time

245 ms

faster than 59% of 609 Email servers

FindLeadEmails: common questions

Is FindLeadEmails MCP server safe?

Yes, by our scan: it is graded A (89/100). Read the FindLeadEmails safety report

How do I install FindLeadEmails?

It runs remotely at www.findleademails.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does FindLeadEmails need an API key?

Yes. The registry entry asks for Authorization.

Is FindLeadEmails maintained?

The last commit was 16 days ago (2026-10-19). The latest release is v1.1.0.

Is FindLeadEmails up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of FindLeadEmails?

Servers from other publishers that do the same job: e2a — email for AI agents MCP server, e2a — email for AI agents MCP server and flightclaw MCP server.

How does FindLeadEmails compare with other Email MCP servers?

safety score 89/100 (higher than 83% of 916 Email servers); tools 6 (the typical Email server has 7); tools that change things 50% (typical: 25%. Fewer write tools means less an agent can break). Full comparison.