Email Verifier

What the email-verifier MCP server does

The email-verifier MCP server exposes Verifox email verification and business-email discovery through Model Context Protocol tools. It supports both individual requests and list-based workflows, making it suitable for checking an address before sending mail or processing a larger contact list.

Email verification returns deliverability-related information, including whether an address is associated with a catch-all domain, disposable service, role account, or free provider, along with a score from 0 to 100. Business-email lookup uses a person's name and company domain to return the best match or indicate that no result was found.

How it works

The server forwards tool calls to the Verifox API and authenticates them with a Verifox API key. Single verification uses one credit per email. Bulk verification also costs one credit per email, while finding an address costs ten credits per contact. Cached verifications cost zero credits. The credit-balance tool does not consume credits.

Bulk operations and some lookup requests are asynchronous. The server waits about 55 seconds for bulk work when possible. If the API continues processing, the tool returns a job ID that can be passed to the job-polling tool to retrieve results later.

The email-verifier MCP server can run over standard input/output for local MCP clients or as a streamable HTTP endpoint. HTTP mode accepts the API key on each request through an Authorization bearer header, with x-api-key and api_key query parameters also supported.

Setup and configuration

The published package can be launched with npx from an MCP client configuration, so a separate package installation is not required. Add the server command with npx -y verifox-mcp and provide VERIFOX_API_KEY. The key can be generated from the Verifox dashboard, which provides an initial allocation of 1,000 credits according to the supplied documentation.

For local development, the repository uses Bun and can be run directly from source. VERIFOX_API_URL defaults to https://api.verifox.ai; set it to another address when testing against a local API instance. HTTP deployments use MCP_TRANSPORT=http or a configured PORT, expose MCP requests at /mcp, and provide a health check at /health.

Tools and capabilities

• verify_email: checks one email address for deliverability and related classifications.
• verify_emails: submits a list for bulk verification and returns one result per email.
• find_email: searches for one business email using a name and company domain.
• find_emails: searches for multiple contacts, with a name and domain for each.
• get_credits: reports the account's remaining Fox Credit balance.
• get_job: retrieves results for an asynchronous verification or email-finding job.

Limitations and notes

A valid Verifox API key is needed for authenticated operations, and verification or discovery requests consume credits according to their operation and input size. Long-running work may not finish during the initial tool call, so callers must retain and poll the returned job ID. The documentation names Claude Desktop and Claude Code configuration examples; other clients must support the relevant MCP transport and configuration format.