Tools / Email finder / Tool
Paste an email address. contact.verify asks the mail server whether that mailbox exists and returns valid, invalid or unknown, with the catch-all flag, the mail provider (Google Workspace, Microsoft 365) and the company behind the domain. When one verifier has no answer, the next one tries in the same call.
Ask your agent
Check these five addresses and tell me which ones are safe to email.
Connect RouterGrowth once, then ask in plain words. New workspaces start with $1 of credit. Get a key or read the setup guide.
A real run
One call to contact.verify (email deliverability check), run through RouterGrowth on October 26, 2026. These are the first rows it returned; fields that name a person are masked.
| status | mx_provider | |
|---|---|---|
| p***@***.com | invalid | Google Workspace |
A press mailbox printed on a company site: two verifiers gave no verdict, the third returned invalid on Google Workspace.
Step by step
One address per call. For a list, run the calls as a batch.
The verifiers are tried in turn until one gives a verdict.
valid means the mailbox accepts mail, invalid means the server refused it, unknown means no verifier could decide.
Send to valid, drop invalid, and recheck unknown later or ask for another address.
Price
List prices on this call, read from the catalog when this page was built. The exact figure is quoted before every run, and a monthly plan lowers it.
In practice
You describe the job; the agent picks the calls, shows the price and runs them.
Check these five addresses and tell me which ones are safe to email.
Find the work email of Alex Rivera at example.com, then check it before I write.
Connect
One MCP server for Claude, ChatGPT, Claude Code, Codex and Cursor, or the same call over the CLI and REST with the input above.
claude mcp add --transport http routergrowth https://api.routergrowth.com/mcp
npm install -g routergrowth && routergrowth setup
routergrowth run -c contact.verify -i '{"email": "press@example.com"}'curl -X POST https://api.routergrowth.com/v1/run \
-H "Authorization: Bearer $ROUTERGROWTH_API_KEY" \
-d '{"capability": "contact.verify", "input": {"email": "press@example.com"}}'Worth knowing
A press or support address printed on a site can still come back invalid, because group mailboxes often do not answer like a personal inbox. Treat invalid as do not send, and confirm a key address another way.
Only a valid or invalid verdict is charged. When a verifier cannot decide, the next one tries at no cost.
The check talks to the mail server; nothing lands in the inbox.
FAQ
The mail server said the mailbox does not exist or will not take mail. A send to it would most likely bounce.
A domain whose server accepts every address, so a single mailbox cannot be confirmed. The catch_all field flags it when the verifier reports it.
The first two had no verdict for this address. The router moved on until one answered, all in one call.
Yes. In this run two verifiers had no verdict for a role address and the third one answered.
More on Email finder
Reading this as an agent? This page as markdown: /tools/email-finder/checker.md
Connect your agent once. The first calls run on the $1 that comes with signup.