Email Verifier vs Deliveriq MCP

A side-by-side look at the Email Verifier and Deliveriq MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Email Verifier logoEmail VerifierCommunication · Local subprocess (stdio)Verify email deliverability & find business emails (single or bulk) via the Verifox API.55GoodAuth: not declaredDeliveriq MCP logoDeliveriq MCPCommunication · Local subprocess (stdio)Email deliverability for AI agents. 12 tools: verify, DNSBL, DMARC, spam-trap, finder.41FairAuth: api key required

Verdict: choose Email Verifier for communication work as a local process; choose Deliveriq MCP for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Email Verifier logoChoose Email Verifier when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: VERIFOX_API_KEY.
  • You want tools like verify_email, verify_emails, find_email.
Explore Email Verifier

Deliveriq MCP logoChoose Deliveriq MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: DELIVERIQ_API_KEY.
Explore Deliveriq MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEmail Verifier logoEmail VerifierDeliveriq MCP logoDeliveriq MCP
CategoryCommunicationCommunication
Quality signal55/100 · Good41/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFreemium
Required env varsVERIFOX_API_KEYDELIVERIQ_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars01
Directory activity 5 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools6Not listed

Tools & capabilities

Email Verifier tools 6

  • verify_emailVerify whether ONE email address is deliverable. Checks syntax, MX, SMTP, catch-all, disposable, free-provider and role detection, and returns a 0-100 quality score. Charges 1 Fox Credit per uncached email.
  • verify_emailsBulk-verify a LIST of email addresses. Submits the whole list, waits for completion, and returns one result per email (same fields as verify_email). Best for cleaning lead lists. Charges 1 Fox Credit per email. Large lists that don't finish quickly return a jobId to poll with get_job.
  • find_emailFind ONE person's business email from their name and company domain. Generates ~50 permutations and SMTP-verifies each, waits for the result, and returns the best match (or not_found). Charges 10 Fox Credits per find.
  • find_emailsBulk-find business emails for a LIST of contacts (name + company domain each). Submits the list, waits for completion, and returns the found email per contact. Up to 1000 contacts. Charges 10 Fox Credits per contact. Large lists that don't finish quickly return a jobId to poll with get_job.
  • get_creditsGet the current Fox Credit balance for the Verifox account tied to the API key. Free — no credits charged. Use it to check remaining balance before a big verify/find run (verify = 1 credit/email, find = 10 credits/contact).
  • get_jobCheck an async job started by verify_emails, find_email, or find_emails. Returns results if finished, otherwise the current status. Use the type shown in the submitting tool's response.

Deliveriq MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Email Verifier

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "email-verifier": {
      "command": "npx",
      "args": [
        "-y",
        "verifox-mcp"
      ],
      "env": {
        "VERIFOX_API_KEY": "YOUR_VERIFOX_API_KEY_HERE"
      }
    }
  }
}

Deliveriq MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "deliveriq-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@deliveriq/mcp"
      ],
      "env": {
        "DELIVERIQ_API_KEY": "YOUR_DELIVERIQ_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Email Verifier is categorized under Communication and uses a local stdio subprocess. Deliveriq MCP belongs to Communication and uses a local stdio subprocess. Pick Email Verifier for communication work and Deliveriq MCP for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Email Verifier has no declared pricing — check the project's own site. Deliveriq MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add email-verifier and deliveriq-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Email Verifier has a quality signal of 55/100 (Good) with 5 views, 0 installs and 0 GitHub stars. Deliveriq MCP has 41/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.