Verify email deliverability & find business emails (single or bulk) via the Verifox API.
MCPpedia last refreshed this data
ai.verifox/email-verifier is an MCP server that verify email deliverability & find business emails (single or bulk) via the Verifox API. Its tool list has not been published yet, requires no API key, and scores 63/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"verifox": {
"env": {
"VERIFOX_API_KEY": "foxkey_your_key_here"
},
"args": [
"-y",
"verifox-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.
A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
The official MCP server to send emails and interact with Resend
MCP Security Weekly
Get CVE alerts and security updates for ai.verifox/email-verifier and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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".
| Tool | Does | Credits |
|---|---|---|
verify_email | Verify ONE email — SMTP deliverability, catch-all, disposable, role, free + 0-100 score | 1 / email |
verify_emails | Bulk-verify a LIST — submits, waits, returns one result per email | 1 / email |
find_email | Find ONE business email from name + company domain (best match or not_found) | 10 / find |
find_emails | Bulk-find emails for a LIST of contacts (name + domain each) | 10 / contact |
get_credits | Check the account's remaining Fox Credit balance | free |
get_job | Poll 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.
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:
| Variable