mcpbeat Sign in

Email Finder API MCP Server

not responding

Email Finder API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 2 Sep 2026.

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

Uptime history 51 days of history · worst day 0%
51 days agonow
0.0%
Uptime 24h
0 of 91 checks
1
Tools
read from the server
9 ms
Response time
average over 24h
0
Stars
last commit 2 Sep 2026

What changed 3652

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 August 2026. No other catalogue keeps this.

17 Sep a tool description was rewritten71 times that day email_find_by_name
16 Sep a tool description was rewritten92 times that day email_find_by_name
15 Sep a tool description was rewritten91 times that day email_find_by_name
14 Sep a tool description was rewritten91 times that day email_find_by_name
13 Sep a tool description was rewritten92 times that day email_find_by_name
12 Sep a tool description was rewritten91 times that day email_find_by_name
11 Sep a tool description was rewritten90 times that day email_find_by_name
10 Sep a tool description was rewritten93 times that day email_find_by_name
9 Sep a tool description was rewritten91 times that day email_find_by_name
8 Sep a tool description was rewritten91 times that day email_find_by_name
and 3642 more, back to 8 August 2026

Email Finder API does not always answer

Over the last week it answered 30.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add email-finder --transport http https://email-finder.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "email-finder": {
      "url": "https://email-finder.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.email-finder]
url = "https://email-finder.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "email-finder": {
      "url": "https://email-finder.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "email-finder": {
      "url": "https://email-finder.api.klymax402.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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. 1. email (string) -- best matching email address found 2. confidence (number 0-100) -- likelihood the email is correct 3. pattern (string) -- the pattern that matched (e.g. "first.last", "flast", "first") 4. allCandidates (array) -- all tested patterns with individual scores 5. domain (string) -- company domain used 6. mxValid (boolean) -- whether domain has valid MX records Example output: {"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} Use this BEFORE 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. Do NOT use for email validation -- use email_verify_address instead. Do NOT use for company data -- use company_enrich_from_domain instead. Do NOT use for person data from email -- use person_enrich_from_email instead.

Endpoints

URLTransportStateLatencyChecked
https://email-finder.api.klymax402.com/mcp sse answering 9 ms 3 min ago

Alternatives to Email Finder API

same job, measured the same way
Pii Redact
by x402supply

Detects and redacts PII (emails, phones, SSNs, names, addresses) from text. $0.02/call via x402.

1 tools answering
Anymail Finder
by anymailfinder

Find verified work emails from a name, company, role or LinkedIn URL, and verify emails you have.

27 installs/wk answering
MCP Company Contact Details Extractor
by mambabuilt

Find a company contact page and extract role emails, a phone number and a postal address.

26 installs/wk local only
Email Finder
by superagnt

Email finder + verifier for AI agents: find work emails by name and company, check deliverability.

answering
Email Finder Server
by admosolutionsgo-star

Extract emails and phones from any website via Apify.

answering
Lorem
by ryudi84

MCP server for placeholder text, fake names, emails, and addresses.

local only
Shaka
by shaka

Company email for Rwanda. Read and send mail from a Shaka mailbox over OAuth or an API key.

answering
Emailkind
by emailkind

Classify email addresses and domains by provider and type (business, personal, disposable).

answering

Email Finder API — questions

Answers built from our own checks of this server.

What can Email Finder API do?
It exposes 1 tools, read directly from the server on our last check. Among them: email_find_by_name. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Email Finder API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 9 ms. The bar chart above shows every period we have measured.
The registry lists Email Finder API as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Email Finder API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Email Finder API need an API key?
No. Email Finder API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
Is Email Finder API open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.