Search DevTools

Jump to any tool or page

email-verifier

Verify email deliverability & find business emails (single or bulk) via the Verifox API.

verifoxturnix10 stars0 forksDeveloper Tools
View source

Install

Terminal

$npx -y verifox-mcp

mcp_config.json

{
  "mcpServers": {
    "ai-verifox-email-verifier": {
      "env": {
        "VERIFOX_API_KEY": "${VERIFOX_API_KEY}"
      },
      "args": [
        "-y",
        "verifox-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

Verifox MCP Server

MCP (Model Context Protocol) server that gives Claude and other AI assistants the Verifox API — verify email deliverability and find business emails, both single and in bulk.

Quick start (published package)

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json) or Claude Code MCP config — no install needed, npx fetches it:

{
  "mcpServers": {
    "verifox": {
      "command": "npx",
      "args": ["-y", "verifox-mcp"],
      "env": {
        "VERIFOX_API_KEY": "foxkey_your_key_here"
      }
    }
  }
}

Get a free API key (1,000 credits) at https://verifox.ai/dashboard/api. Restart Claude Desktop and ask it to "verify these emails".

Tools

ToolDoesCredits
verify_emailVerify ONE email — SMTP deliverability, catch-all, disposable, role, free + 0-100 score1 / email
verify_emailsBulk-verify a LIST — submits, waits, returns one result per email1 / email
find_emailFind ONE business email from name + company domain (best match or not_found)10 / find
find_emailsBulk-find emails for a LIST of contacts (name + domain each)10 / contact
get_creditsCheck the account's remaining Fox Credit balancefree
get_jobPoll a long-running verify_emails / find_email / find_emails job for results

Verify and find are async for large lists: the bulk tools wait ~55s inline, and hand back a jobId to finish via get_job if a job runs longer. Cached verifications cost 0 credits.

Local development

Run straight from source with Bun (no build):

cd mcp
bun install
{
  "mcpServers": {
    "verifox": {
      "command": "bun",
      "args": ["run", "/FULL/PATH/TO/Verifox-api/mcp/src/index.ts"],
      "env": {
        "VERIFOX_API_URL": "https://api.verifox.ai",
        "VERIFOX_API_KEY": "foxkey_your_key_here"

```json
{
  "mcpServers": {
    "verifox": {
      "command": "bun",
      "args": ["run", "/FULL/PATH/TO/Verifox-api/mcp/src/index.ts"],
      "env": {
        "VERIFOX_API_URL": "https://api.verifox.ai",
        "VERIFOX_API_KEY": "foxkey_your_key_here"
      }
    }
  }
}

VERIFOX_API_URL defaults to https://api.verifox.ai when unset. For local development against the API on port 8001, set it to http://localhost:8001.

3. Restart Claude Desktop

The tools will appear in Claude's tool list.

Remote (HTTP) mode

The same server also runs as a streamable-HTTP MCP endpoint (for Smithery, claude.ai connectors, and other remote MCP clients). Set MCP_TRANSPORT=http (or a PORT) and it listens on POST /mcp with a GET /health check:

MCP_TRANSPORT=http PORT=8080 node dist/index.js
# or: docker build -t verifox-mcp . && docker run -p 8080:8080 verifox-mcp

In HTTP mode the Verifox API key is read per request from the Authorization: Bearer <foxkey> header (also accepts x-api-key or ?api_key=) — so one hosted endpoint serves many users, each on their own credits.

Usage Examples

In Claude Desktop, just ask:

Environment Variables

VariableDefaultDescription
VERIFOX_API_URLhttps://api.verifox.aiVerifox API base URL
VERIFOX_API_KEY(empty)Per-user API key (foxkey_*), sent as x-api-key

Generate a foxkey_* key from the Verifox dashboard (API Keys). The key authenticates every tool call and is the account whose Fox Credits are charged (verify and find cost 1 credit each; scoring and DNS scans are free).

Sourced from the repository README.

More in Developer Tools