Email Finder API
Find email addresses from name and company domain. x402 paid.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport sse email-finder-api 'https://email-finder.api.klymax402.com/mcp'{
"mcpServers": {
"email-finder-api": {
"type": "sse",
"url": "https://email-finder.api.klymax402.com/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Email Finder API
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 bodyAny x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
email_find_by_name | GET | /api/find | $0.012 | Find a person's email from their name and company domain |
email_find_by_name | POST | /api/find | $0.012 | Find 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
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | yes | Company domain (e.g. company.com) |
firstName | string | yes | Person's first name (e.g. John) |
lastName | string | yes | Person's last name (e.g. Doe) |
Example response:
{"email":"john.doe@stripe.com","confidence":92,"pattern":"first.last","allCandidates":[{"email":"john.doe@stripe.com","score":92},{"email":"jdoe@stripe.com","score":75},{"email":"john@stripe.com","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
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | yes | Company domain (e.g. company.com) |
firstName | string | yes | Person's first name (e.g. John) |
lastName | string | yes | Person's last name (e.g. Doe) |
Example response:
{"email":"john.doe@stripe.com","confidence":92,"pattern":"first.last","allCandidates":[{"email":"john.doe@stripe.com","score":92},{"email":"jdoe@stripe.com","score":75},{"email":"john@stripe.com","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.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Frequently asked questions
What is Email Finder API?
Find email addresses from name and company domain. x402 paid.
How do I install Email Finder API?
It runs as a remote server. In Claude Code: claude mcp add --transport sse email-finder-api 'https://email-finder.api.klymax402.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Email Finder API need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Email Finder API open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Email Finder API?
It is published by Br0ski777. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.