The Email Verification MCP

MCP is the Model Context Protocol, the open standard that lets an AI agent call external tools. An email verification MCP is a server that exposes email checks as those tools, so an agent can verify, score, and find addresses on its own instead of you copying results between a website and your chat.

Verifox ships exactly that as the verifox-mcp package, wired to the same engine behind our free email checker. Install it once and your agent gains 6 email tools, ready to call right away.

Any client that speaks MCP. The two we show config for are Claude Desktop and Cursor, and because verifox-mcp is a standard stdio server the same npx verifox-mcp command drops into any other MCP host the same way.

You point the client at the command, add your key as an environment variable, and the tools appear in that agent’s tool list with no extra glue code.

Add the JSON block from the install section aboveto your client’s config file, the one named claude_desktop_config.json for Claude Desktop or ~/.cursor/mcp.json for Cursor, then restart the app. The command is npx verifox-mcp, so there is nothing to clone or build.

The only value you change is VERIFOX_API_KEY. Paste your own key, save, and the 6 tools are live in your next session.

The server itself is free to install and run, and a free Verifox account comes with 1,000 verifications on signup, or 2,500 if you sign up with a work email. Every tool call draws from that same balance, so trying it out costs nothing.

Past the free balance, credits are pay-as-you-go and never expire, with volume pricing shown for your region. There is no separate MCP fee.

Open the API keys area of your dashboard — create a free account first if you do not have one — and generate a key. It looks like foxkey_..., and that is the exact value you drop into VERIFOX_API_KEY in your client config.

The server sends it as the x-api-key header on every request, so it stays on your machine and never ships in client-side code.

6 of them, grouped into three jobs. Verify and score (verify_email, verify_emails), find business emails (find_email, find_emails), and account and jobs (get_credits, get_job). Verify and find each work on one address or a whole list.

The full list with a one-line purpose for each sits in the tools section above, and the same endpoints are documented in the API reference. Two have a browser twin you can try without an agent: find_email powers the email finder, and verify_emails the bulk email checker, no install required.

verifox-mcp runs locally as a stdio process that your client starts. Your VERIFOX_API_KEY is read from the environment you set in the config and is sent only to api.verifox.ai over HTTPS as the request header. It is never written to the page or shared with the model.

Addresses are processed and discarded; nothing is retained or sold. Verifox is SOC 2 Type II compliant, with the full data handling covered in the privacy policy, so you always know what happens to an address you send.

Identical to the rest of Verifox, because the MCP server is a thin wrapper over the same API. That means 99.99% accuracy on a benchmark list, including catch-all domains, with median single-address latency around 380 ms and sub-50 ms on cached results.

A tool call from your agent runs the exact same checks the paid email verification API runs. No accuracy is traded for the convenience.

Yes. MCP is the agent-native path; the underlying engine is a plain REST API you can call from anywhere. If you are wiring a backend rather than an agent, skip the server and hit the endpoints directly.

The API reference documents every endpoint the 6 tools map to, and the free email checker lets you prototype a single check in the browser first.