Email Finder & Verifier MCP Server — Find & Verify Emails from Claude, Cursor & ChatGPT

Give your AI assistant email superpowers. This Actor runs as a hosted MCP server (Model Context Protocol): connect Claude, Cursor, ChatGPT, VS Code or any MCP client and it can find a company's contact emails (from a website or just a company name) and verify any email list — syntax, MX/mail-server, disposable-domain, role and free-provider checks — with a clean valid / risky / invalid verdict. No API keys, no third-party email-finder subscription, nothing to host.

Apify hosts it, authenticates it with your Apify token, and bills it per lookup / per email — you don't run or host anything.

---

🧰 Tools

Four tools, all returning clean, typed JSON — ready for an LLM to reason over.

Tool	What it does	Key arguments
verify_email	Verify one email address: syntax, MX/mail-server presence, disposable-domain, role-based and free-provider checks. Returns a valid / risky / invalid verdict.	email (required)
verify_emails	Verify a list of emails in bulk (up to 100 per call). Each gets the full check set plus a verdict; returns a summary count + per-email results.	emails (required, list, 1–100)
find_company_emails	Find a company's contact emails. Pass a website when you know it (most accurate — the site is scraped directly), or just the company name (the domain is discovered first). Optionally verify the results in one call.	website and/or company (one required), city, state, verify (bool)
find_company_domain	Discover the most likely website domain for a company name — no scraping, just the domain. Cheap and fast; useful as a first step.	company (required)

Pricing is per-call: verify_email / each email in verify_emails is billed per email verified, find_company_emails per lookup, and find_company_domain per domain lookup (the cheapest). Adding verify: true to find_company_emails also bills the returned emails as verifications.

---

🔌 Connect it

This Actor runs in Standby mode and exposes an MCP endpoint at /mcp over the Streamable HTTP transport. Point your MCP client at the Actor's Standby URL and authenticate with your Apify API token as a bearer token.

Add this to your MCP client config (Claude Desktop, Cursor, VS Code, Windsurf, …):

{
  "mcpServers": {
    "email": {
      "url": "https://<YOUR-STANDBY-URL>/mcp",
      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
    }
  }
}

• Your Standby URL is shown on the Actor's page once you enable Standby (looks like https://<user>--email-mcp-server.apify.actor).
• Your Apify API token is under Settings → Integrations in the Apify Console.

That's it — your assistant will discover the four tools automatically and pick the right one.

---

💬 Example prompts

Once connected, just ask your assistant naturally:

• “Find the contact email for apify.com.”
• “What's the website domain for Stripe?”
• “Here's a list of 40 emails from a lead export — verify them and tell me which are safe to send to.”
• “Find emails for ‘Acme Roofing’ in Austin, Texas, and verify them.”
• “Is ceo@stripe.com a deliverable address?”

---

📦 Example tool calls & output

verify_emails

{ "emails": ["ceo@stripe.com", "info@shopify.com", "fake@nope.invalid"] }

{
  "summary": { "total": 3, "valid": 1, "risky": 1, "invalid": 1 },
  "results": [
    {
      "email": "ceo@stripe.com",
      "syntaxValid": true,
      "domain": "stripe.com",
      "mxFound": true,
      "isDisposable": false,
      "isRoleBased": false,
      "isFreeProvider": false,
      "verdict": "valid"
    },
    {
      "email": "info@shopify.com",
      "syntaxValid": true,
      "domain": "shopify.com",
      "mxFound": true,
      "isDisposable": false,
      "isRoleBased": true,
      "isFreeProvider": false,
      "verdict": "risky"
    },
    {
      "email": "fake@nope.invalid",
      "syntaxValid": true,
      "domain": "nope.invalid",
      "mxFound": false,
      "isDisposable": false,
      "isRoleBased": false,
      "isFreeProvider": false,
      "verdict": "invalid"
    }
  ]
}

• valid — syntax + MX both pass and it's not disposable/role/free.
• risky — deliverable domain, but role-based (info@, sales@…) or a free provider — reaches an inbox but may not be the person you want.
• invalid — bad syntax, no mail server (MX), or a disposable domain.

verify_email

{ "email": "ceo@stripe.com" }

Returns a single object with the same fields as one results[] entry above.

find_company_emails

{ "website": "apify.com" }

{
  "company": null,
  "website": "apify.com",
  "emails": ["hello@apify.com"],
  "emailCount": 1,
  "source": "website",
  "confidence": "high"
}

Pass company instead of website to discover the domain first, or add "verify": true to attach a verifications block with a verdict per email.

find_company_domain

{ "company": "Stripe" }

{ "company": "Stripe", "domain": "stripe.com", "found": true }

---

✅ Why use it

• Two jobs, one server. Find emails and verify them — no separate email-finder and email-verifier subscriptions.
• No API keys. No Hunter/NeverBounce/ZeroBounce account, no OAuth, no per-service billing to wire up.
• Built for agents. Clean, typed tools with descriptions LLMs understand, so your assistant picks the right one and gets structured JSON back.
• Website-first accuracy. When you know the site, find_company_emails scrapes it directly for the truest contacts; when you only have a name, it discovers the domain first.
• Pay per call. Billed per email / per lookup — no subscription, no idle server cost, nothing to host.
• Works everywhere. Standard Streamable HTTP MCP transport — Claude, Cursor, ChatGPT, VS Code, Windsurf, or your own agent.

---

🎯 Great for

• Lead-list hygiene — verify a scraped or exported list before you send, to protect sender reputation.
• Outbound & sales prospecting — turn a company name or website into a real contact email inside your agent.
• CRM enrichment — fill in missing emails and flag stale / risky addresses.
• Sign-up / form validation — check an address is deliverable (syntax + MX) at the point of capture.

---

⚙️ Notes & limitations

• Verification is heuristic, not an SMTP mailbox ping. Checks are syntax + MX (mail-server) presence + disposable-domain + role-based + free-provider — it confirms the address is well-formed and the domain can receive mail, and flags likely-low-quality addresses. It does not open an SMTP session to confirm a specific mailbox exists, so a valid verdict means deliverable-looking, not guaranteed to exist.
• Role & free addresses are risky, not invalid — info@, support@, sales@ and Gmail/Outlook-style addresses reach an inbox but may not be the individual you want.
• find_company_emails returns public contact addresses published on the company's own site (or the discovered domain). Coverage depends on what the business exposes; some sites list none.
• Bulk verify_emails is capped at 100 emails per call — split larger lists across calls.

---

⚠️ Disclaimer

This Actor accesses only publicly available data (public company websites and public DNS/MX records) and performs no login or private-account access. Email verification is heuristic and provided as-is with no guarantee that any address is deliverable. You are responsible for using the output — including any outreach — in compliance with anti-spam laws (CAN-SPAM, GDPR, CASL…) and applicable terms. Not affiliated with, endorsed by, or sponsored by any company named in examples.

---

🔎 SEO keywords

email MCP, email MCP server, email finder MCP, email verifier MCP, email verification API, find company email, company email finder, email verifier for Claude, email finder for Cursor, email finder for ChatGPT, MCP server, Model Context Protocol, verify email address, bulk email verification, MX record check, disposable email detection, role-based email check, lead enrichment MCP, no-auth email finder, email tool for AI agents, hosted MCP server, Streamable HTTP MCP.