Email Finder API
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Email Finder APIfind email for John Doe at stripe.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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"
}
}
}Related MCP server: Prospector 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 |
| GET |
| $0.012 | Find a person's email from their name and company domain |
| POST |
| $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 |
| string | yes | Company domain (e.g. company.com) |
| string | yes | Person's first name (e.g. John) |
| 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 |
| string | yes | Company domain (e.g. company.com) |
| string | yes | Person's first name (e.g. John) |
| 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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Br0ski777/email-finder-x402'
If you have feedback or need assistance with the MCP directory API, please join our Discord server