Your first 100,000 email verifications or 10,000 work emails found are on us.100K verifications or 10K finds, free.Sign up today

HomeWho it's forAI automation agencies

Email find and verify, ready for your next build

Email Finder Verifier is two plain GET requests and one MCP server. Use the HTTP node in n8n or Make for client workflows, and point Claude or any agent at the MCP server when you build one. Build the step once, then reuse it on every client.

Free while in beta. No card needed.

Key takeaways

  • Your job: ship lead gen and CRM automations that clients trust.
  • The result: a find step and a verify step you build once and copy into every project.
  • Time: the HTTP node takes about five minutes the first time.

Last updated 16 Nov 2026

01The problem

Your problem, and what EFV does

Your problem What EFV does
Every client project needs an email step and a trusted check after it. Find and verify are two requests on one key. Copy the same two nodes into each build.
Too many vendor keys across client accounts. One key per client build. Delete it when the project ends.
An agent needs a tool it can call in plain words. The MCP server gives Claude find_email, verify_email, team inbox lookup and domain lookup.
Your flow needs a simple branch. verified is true or false. No maybe pile to sort.
A client wants to see what's used. The dashboard shows usage day by day.

02The workflow

Three ways to build it

1. In n8n or Make

Add an HTTP Request node (n8n) or HTTP, Make a request module (Make). Method GET. URL https://api.emailfinderverifier.com/api/v1/verify. Add email as a query parameter, and put your key in a header named X-API-Key. Add an IF node or router on verified. For finding, call /api/v1/find first with first_name, last_name and domain, then verify what comes back.

2. In an agent, with MCP

Add the server at https://mcp.emailfinderverifier.com/mcp. In Claude on the web, add it as a custom connector with your key. In Claude Code, run:

claude mcp add --transport http efv https://mcp.emailfinderverifier.com/mcp --header "X-API-Key: YOUR_API_KEY"

Then ask: "Find the work email for Jane Doe at acme.com, then verify it." Claude calls find_email, then verify_email.

3. In any other agent tool

Give the agent your key and the OpenAPI file at https://emailfinderverifier.com/docs/openapi.json. Tell it to go one request at a time.

03Hand-off

Make it safe to hand over

  • Use one key per client build and name it after the client.
  • Handle 429 with a short wait and a retry. New accounts can send one request a second and have five at once.
  • Set a timeout of at least 60 seconds. Some checks take a few seconds.
  • Write the result back to the client's sheet or CRM, and keep the Verified column so they can see it.

04Example

Example: a lead flow you can copy

Made-up client flow in n8n or Make. Each step is one node or module.

Step In Out
New row in the client's sheet Maya Patel, northwind.example The row
HTTP: find first_name, last_name, domain maya@northwind.example
HTTP: verify maya@northwind.example verified: true
IF verified is true Write "Verified" back to the sheet
Else verified is false or the call failed Write "Check later" and carry on

Save these as a template. For the next client, change the key and the sheet.

Build the node once and reuse it. Free while in beta.

Sign up for free

05FAQ

Questions, answered

01Does the MCP server work with ChatGPT and other agents?

Claude is the path we've written up, step by step. Any agent that can call an API can use the plain GET requests with the OpenAPI file. See the help page on AI agents.

02Which tools does the MCP server give Claude?

verify_email, find_email, find_generic_inboxes (team inboxes like info@), lookup_domain (mail provider and catch-all status), check_allowance and check_rate_limits.

03How should a client workflow handle errors?

Treat 401 as a key problem, 429 as wait and retry, and a timeout as check later. Write the problem to a log column so the rest of the flow keeps moving.

04How do I stop an agent hitting the rate limit?

Tell it to go one request at a time. New accounts can send one request a second.

05Can I use it for a client's CRM or signup form?

Yes. The same verify request works in a CRM workflow, or from a signup form's backend. See the use-case pages linked below.

06What if a client needs more than the free allowance?

Each account gets 100,000 verification requests or 10,000 found emails while we're in beta. Ask in Slack for more.

07Start today

Build the step once, use it everywhere

Sign up with email or Google. No card. Your key and a ready-made first request are waiting. Need more later? Message us on Slack.