mcpField
E
Email Finder X402

Email Finder X402

Remote
github.comCommunication0Updated 8w ago

About Email Finder X402

Email Finder X402 is an API and MCP server for sales teams and AI agents that need professional email addresses from a person’s name and company domain. It tests address patterns against MX records and returns a confidence score; calls use x402 micropayments.

Key features

  1. 01Find email from name and domain
  2. 02Test 15+ address patterns against MX records
  3. 03Return confidence scores and candidates
  4. 04HTTP API and MCP access
  5. 05x402 pay-per-call

Use cases

  1. 01Finding contacts for sales outreach
  2. 02Building prospect contact lists

MCP support

The remote MCP server exposes the `email_find_by_name` tool, which takes a company domain and first and last name and returns likely email candidates with confidence scores. Access is listed as pay-per-call via x402.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://email-finder.api.klymax402.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Email Finder API

MCP Server x402 License: MIT

Find professional email addresses from name + company domain. Tests 15+ patterns against MX records with confidence scoring. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "email-finder": {
      "url": "https://email-finder.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl "https://email-finder.api.klymax402.com/api/find?domain=...&firstName=...&lastName=..."
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
email_find_by_nameGET/api/find$0.012Find a person's email from their name and company domain
email_find_by_namePOST/api/find$0.012Find a person's email from their name and company domain (POST variant)
email_find_by_name

Search for people/contacts matching criteria and find their professional email address from name and company domain. Alternative to Apollo people-search at 4x lower cost. Returns the most likely email with confidence score after testing 15+ patterns against MX records.

Parameters

NameTypeRequiredDescription
domainstringyesCompany domain (e.g. company.com)
firstNamestringyesPerson's first name (e.g. John)
lastNamestringyesPerson's last name (e.g. Doe)

Example response:

{"email":"[email protected]","confidence":92,"pattern":"first.last","allCandidates":[{"email":"[email protected]","score":92},{"email":"[email protected]","score":75},{"email":"[email protected]","score":60}],"domain":"stripe.com","mxValid":true}

When to use: sales outreach, cold emailing, or building prospect contact lists. Essential for searching for people/contacts and finding decision-maker emails when you only know their name and company. Drop-in replacement for Apollo people search.

Not for: email validation (use email_verify_address), company data (use company_enrich_from_domain), person data from email (use person_enrich_from_email).

email_find_by_name

Search for people/contacts matching criteria and find their professional email address from name and company domain. Alternative to Apollo people-search at 4x lower cost. Returns the most likely email with confidence score after testing 15+ patterns against MX records. POST variant of email_find_by_name -- same params passed as JSON body instead of query string.

Parameters

NameTypeRequiredDescription
domainstringyesCompany domain (e.g. company.com)
firstNamestringyesPerson's first name (e.g. John)
lastNamestringyesPerson's last name (e.g. Doe)

Example response:

{"email":"[email protected]","confidence":92,"pattern":"first.last","allCandidates":[{"email":"[email protected]","score":92},{"email":"[email protected]","score":75},{"email":"[email protected]","score":60}],"domain":"stripe.com","mxValid":true}

When to use: sales outreach, cold emailing, or building prospect contact lists. Essential for searching for people/contacts and finding decision-maker emails when you only know their name and company. Drop-in replacement for Apollo people search.

Not for: email validation (use email_verify_address), company data (use company_enrich_from_domain), person data from email (use person_enrich_from_email).

Example agent prompts

  • "Search for people/contacts matching criteria and find their professional email address from name and company domain"
  • "Search for people/contacts matching criteria and find their professional email address from name and company domain"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.