Email Finder API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

Find email addresses from name and company domain. x402 paid.

The publisher's own server: Finder Jobs

Overview

AI-generated overview

A remote, pay-per-call email finder that lets an assistant guess a person's professional email address from their name and company domain.

What you can do
Find a person's likely professional email from first name, last name and company domain, returned with a confidence score and ranked candidate list after testing 15+ patterns against MX records.
When to use it
Useful for sales outreach, cold emailing or building prospect contact lists when you only know a person's name and company domain and want a likely work email.
Requirements
A remote MCP endpoint; no API key or signup. Each call is paid per use via x402 in USDC on Base L2, so an x402-capable client and a funded wallet are needed.
Before you install
Every lookup costs money (about $0.012 per call) and is settled in USDC on Base; the wallet signs payments automatically. Names and company domains are sent to a third-party service, and results are guesses with confidence scores, not verified addresses.

Installation

In SourceWeft

  1. Open Email Finder API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Femail-finder/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

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.):

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

Quickstart -- HTTP (x402)

bash
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:

json
{"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:

json
{"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

Source: README.md at commit f041bdf

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Finder integrations