Email Finder X402

What is Email Finder X402?

Email Finder X402 is a pay-per-call MCP server that finds professional email addresses from a person's name and company domain. It tests 15+ email patterns against MX records and returns the most likely email with a confidence score. It uses the x402 payment protocol (USDC on Base L2) with no API key, no signup, and no rate‑limit wall.

How to use Email Finder X402?

Add the server URL to your MCP client configuration (Claude Desktop, Cursor, ElizaOS, etc.) as shown in the README. Then use the email_find_by_name tool with parameters domain, firstName, and lastName. HTTP calls require an x402‑aware client (e.g., @x402/fetch) to automatically handle payment challenges.

Key features of Email Finder X402

• Pay‑per‑call via x402 (USDC on Base L2) – no API key or signup.
• Tests 15+ email patterns against MX records.
• Returns confidence scores (0–100) for each candidate email.
• Drop‑in replacement for Apollo people search at 4x lower cost.
• Part of the klymax402 marketplace of 100 x402 micropayment APIs.
• Works with any MCP client (Claude Desktop, Cursor, ElizaOS, etc.).

Use cases of Email Finder X402

• Sales outreach: find decision‑maker emails from name + company domain.
• Cold emailing: build prospect contact lists with verified email patterns.
• Lead generation: replace Apollo people search for professional email discovery.
• AI agent workflows: programmatically find contacts with a single tool call.

FAQ from Email Finder X402

How does payment work?

Email Finder X402 uses the x402 protocol for HTTP‑native pay‑per‑call. Each email_find_by_name call costs $0.005 USDC on Base L2 (chain ID eip155:8453). No API key or signup is needed; the x402‑aware client handles the 402 → sign → retry cycle automatically.

What are the required parameters?

Three parameters are required: domain (company domain, e.g., stripe.com), firstName, and lastName (the person’s first and last name).

What data does the server return?

It returns the most likely email, a confidence score (0–100), the pattern used (e.g., “first.last”), a list of all candidate emails with scores, the domain, and whether MX records are valid.

What alternatives does this replace?

It is a drop‑in replacement for Apollo people search at 4x lower cost. It is not intended for email validation, company enrichment, or person enrichment from email – the README notes dedicated tools for those tasks.

Are there any runtime dependencies?

No. The server uses standard MCP over HTTP. Clients only need to be MCP‑compatible and, for HTTP usage, x402‑aware. The payment facilitator is Coinbase CDP (primary) or PayAI (fallback).