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.
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add verifox-mcp -- npx -y verifox-mcp@1.2.2Execute em um terminal.
{ "mcpServers": { "verifox-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
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.
Verifox MCP server — verify email deliverability and find business emails (single + bulk) for Claude and any MCP client.
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".
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.
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.
The tools will appear in Claude's tool list.
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.
In Claude Desktop, just ask:
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).
Verifox MCP server — verify email deliverability and find business emails (single + bulk) for Claude and any MCP client.
{ "mcpServers": { "verifox-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Verifox roda localmente via stdio.
Última verificação: 2026-11-16. Verifox MCP server — verify email deliverability and find business emails (single + bulk) for Claude and any MCP client.