@deliveriq/mcp
The @deliveriq/mcp server provides 12 tools for email deliverability verification and domain intelligence via the DeliverIQ API.
Verification Tools:
Verify a single email: Check deliverability with reachability status, 0–100 score, syntax/MX/SMTP/disposable/role-based checks, and optional HIBP breach detection
Submit batch verification: Asynchronously verify up to 10,000 emails with optional webhook callbacks
Check batch job status: Poll progress of a running batch verification job
Download batch results: Retrieve completed results as CSV, with optional filtering by category (safe/risky/invalid/unknown)
List verification jobs: Browse and filter past batch jobs with pagination
Intelligence Tools:
Find business email: Discover a person's work email by name and company domain using pattern generation and SMTP probing
DNSBL blacklist check: Check a domain's IP against 50 DNS-based blackhole list zones
Email infrastructure check: Analyze SPF, DKIM, DMARC, MTA-STS, BIMI, and TLS-RPT records with an infrastructure score
Spam trap analysis: Evaluate an email address for spam trap risk using 13 signals (domain age, entropy, disposability, etc.)
Domain intelligence: Get a full domain trust report covering MX records, DNSBL status, infrastructure, domain age, and ISP profile
Organization intelligence: Query email patterns, verified contact counts, and company info for a domain (free)
Account Tool:
Check credits: View remaining credit balance, plan tier, billing period, and usage breakdown by category (free)
@deliveriq/mcp
Official MCP (Model Context Protocol) server for the DeliverIQ email verification API by MiN8T. Provides 12 tools for AI agents in Claude Desktop, Claude Code, Cursor, and any other MCP-compatible client.
Installation
No separate install step needed — npx -y @deliveriq/mcp will fetch and run
the server on demand.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"deliveriq": {
"command": "npx",
"args": ["-y", "@deliveriq/mcp"],
"env": {
"DELIVERIQ_API_KEY": "lc_your_api_key"
}
}
}
}Restart Claude Desktop. You should see the 12 DeliverIQ tools available.
Claude Code
claude mcp add deliveriq npx -y @deliveriq/mcp \
-e DELIVERIQ_API_KEY=lc_your_api_keyCursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"deliveriq": {
"command": "npx",
"args": ["-y", "@deliveriq/mcp"],
"env": {
"DELIVERIQ_API_KEY": "lc_your_api_key"
}
}
}
}Get an API key
Sign up at min8t.com/deliveriq and grab a
key from your dashboard. The free tier covers the demo flow plus ongoing
low-volume use. Keys are issued in the format lc_prefix_secret.
Related MCP server: Mailchimp MCP
Environment Variables
Variable | Required | Description |
| Yes | API key (format: |
| No | Override API URL (default: |
Tools (12)
Verification
Tool | Description | Credits |
| Verify a single email for deliverability | 1 |
| Submit batch of emails for async verification | 1/email |
| Check batch job status and progress | Free |
| Download completed batch results as CSV | Free |
| List verification jobs with pagination | Free |
Intelligence
Tool | Description | Credits |
| Find business email by name + domain | 2 |
| Check domain against 50 DNSBL zones | 1 |
| Analyze SPF/DKIM/DMARC/MTA-STS/BIMI | 1 |
| Evaluate spam trap risk (13 signals) | 1 |
| Comprehensive domain trust report | 1 |
| Query organization email patterns | Free |
Account
Tool | Description | Credits |
| Check credit balance and usage stats | Free |
Why MCP?
Email deliverability is one of those problems where the right answer needs 6–8 API calls (verify → reputation → DMARC → blocklist → infrastructure → ...). Letting Claude orchestrate these as tools is ~10× more useful than shipping another dashboard — the model can plan, branch on results, and explain the verdict in plain English.
Development
# Clone the monorepo
git clone https://github.com/Davison-Francis/min8t-sdks.git
cd min8t-sdks/deliveriq-mcp
# Install + build
npm install
npm run build
# Watch mode
npm run dev
# Run directly against the published API
DELIVERIQ_API_KEY=lc_your_key node dist/index.js
# Or against a local DeliverIQ service
DELIVERIQ_API_KEY=lc_test \
DELIVERIQ_BASE_URL=http://localhost:3019/api/v1 \
node dist/index.jsRequirements
Node.js 18+
DeliverIQ API key
Roadmap
See ../ROADMAP.md for upcoming work, or open an issue to
propose a tool.
License
MIT — see LICENSE.
Available Tools
12 toolsdeliveriq_batch_downloadDownload Batch ResultsARead-onlyIdempotent
Download the results of a completed batch verification job as CSV.
Args:
job_id (string): The completed job ID
category (string, optional): Filter to "safe", "risky", "invalid", or "unknown" only
Returns: CSV text with verification results. Large results may be truncated.
Examples:
"Download results for job abc123" -> { job_id: "abc123" }
"Get only safe emails from job abc123" -> { job_id: "abc123", category: "safe" }
Credit cost: Free
Inputs: job_id (required), category.
deliveriq_batch_statusCheck Batch Job StatusARead-onlyIdempotent
Check the status and progress of a batch verification job.
Args:
job_id (string): The job ID from deliveriq_batch_verify
Returns: Job status, progress percentage, and summary when complete.
Examples:
"Check job abc123" -> { job_id: "abc123" }
Credit cost: Free
Inputs: job_id (required).
deliveriq_batch_verifySubmit Batch VerificationA
Submit a batch of email addresses for asynchronous verification. Returns a job ID for tracking.
Use deliveriq_batch_status to poll progress, and deliveriq_batch_download to get results when complete.
Args:
emails (string[]): Array of 1-10,000 email addresses
skip_smtp (boolean): Skip SMTP verification (default: false)
callback_url (string, optional): Webhook URL for batch.completed/batch.failed events
Returns: Job ID, status, estimated completion time, and status polling URL.
Examples:
"Verify these 3 emails" -> { emails: ["a@ex.com", "b@ex.com", "c@ex.com"] }
"Batch verify with webhook" -> { emails: [...], callback_url: "https://my-app.com/webhook" }
Credit cost: 1 credit per email
Inputs: emails (required), skip_smtp, callback_url.
deliveriq_blacklist_checkDNSBL Blacklist CheckAIdempotent
Check a domain's IP against 50 DNSBL (DNS-based Blackhole List) zones across 6 categories: spam, proxy, dynamic, domain reputation, backscatter, and general.
Args:
domain (string): Domain to check (e.g. "example.com")
Returns: Listed/clean status, number of hits, and details per zone.
Examples:
"Is example.com blacklisted?" -> { domain: "example.com" }
Credit cost: 1 credit
Inputs: domain (required).
deliveriq_check_creditsCheck Credit BalanceARead-onlyIdempotent
Check current credit balance, usage breakdown, and plan information. Use this before performing credit-consuming operations to verify sufficient balance.
Returns: Remaining credits, plan tier, billing period, and usage breakdown by category (single, batch, ESP sync).
Examples:
"How many credits do I have left?" -> {}
"What's my usage this month?" -> {}
Credit cost: Free
Inputs: no named parameters.
deliveriq_domain_intelComprehensive Domain IntelligenceAIdempotent
Get a comprehensive intelligence report for a domain including MX records, DNSBL status, email infrastructure (SPF/DKIM/DMARC), domain age, ISP profile, and trust score.
This is a combined report — if you only need one aspect, use the more specific tools (deliveriq_blacklist_check, deliveriq_infrastructure_check) instead.
Args:
domain (string): Domain to analyze (e.g. "example.com")
Returns: Complete domain intelligence report with trust score.
Examples:
"Full report on example.com" -> { domain: "example.com" }
Credit cost: 1 credit (heavy rate limit: 10 req/min)
Inputs: domain (required).
deliveriq_find_emailFind Business EmailAIdempotent
Find a person's business email address by name and company domain. Uses pattern generation, SMTP probing, corroboration from public sources, and org intelligence.
Args:
first_name (string): Person's first name
last_name (string): Person's last name
domain (string, optional): Company domain (e.g. "acme.com"). Required if company_name is not set
middle_name (string, optional): Middle name for disambiguation
company_name (string, optional): Company name, used to resolve domain if domain is not provided
Returns: Found email address, confidence score and label, verification method, and domain context.
Examples:
"Find John Doe at acme.com" -> { first_name: "John", last_name: "Doe", domain: "acme.com" }
"Find Jane Smith at Globex Corp" -> { first_name: "Jane", last_name: "Smith", company_name: "Globex Corp" }
Credit cost: 2 credits per lookup
Inputs: first_name (required), last_name (required), domain, middle_name, +1 more.
deliveriq_infrastructure_checkEmail Infrastructure CheckAIdempotent
Analyze a domain's email infrastructure: SPF, DKIM, DMARC, MTA-STS, BIMI, TLS-RPT records and MX configuration.
Args:
domain (string): Domain to analyze (e.g. "example.com")
Returns: Infrastructure score (0-100) and detailed analysis of each protocol.
Examples:
"Check example.com email setup" -> { domain: "example.com" }
Credit cost: 1 credit
Inputs: domain (required).
deliveriq_list_jobsList Verification JobsARead-onlyIdempotent
List batch verification jobs with pagination and optional status filter.
Args:
page (number): Page number (default: 1)
limit (number): Results per page (default: 20, max: 100)
status (string, optional): Filter by "pending", "processing", "completed", "failed", or "cancelled"
Returns: Table of jobs with ID, status, email count, and dates.
Credit cost: Free
Inputs: page, limit, status.
deliveriq_org_intelOrganization IntelligenceARead-onlyIdempotent
Query the organization intelligence database for a domain. Returns email patterns, verified contact count, and company name. Free — no credits charged.
This data is populated by the enrichment system. If no data exists, use deliveriq_find_email to trigger enrichment for the domain.
Args:
domain (string): Company domain (e.g. "acme.com")
Returns: Primary email pattern, confidence, verified contact count, and all observed patterns.
Examples:
"What email patterns does acme.com use?" -> { domain: "acme.com" }
Credit cost: Free
Inputs: domain (required).
deliveriq_spam_trap_analysisSpam Trap AnalysisAIdempotent
Analyze an email address for spam trap risk using 13 signals including domain age, DNSBL listing, disposability, role-based detection, entropy, and email pattern trust.
Args:
email (string): Email address to analyze
Returns: Risk level (low/medium/high), trap type (pristine/recycled/typo/none), confidence score, and all 13 signals.
Examples:
"Is user@example.com a spam trap?" -> { email: "user@example.com" }
Credit cost: 1 credit
Inputs: email (required).
deliveriq_verify_emailVerify Email AddressAIdempotent
Verify a single email address for deliverability. Returns reachability status (safe/risky/invalid/unknown), a 0-100 score, and detailed checks (syntax, MX, SMTP, disposable, role-based, etc.).
Args:
email (string): Email address to verify
skip_smtp (boolean): Skip SMTP check (faster, default: false)
check_gravatar (boolean): Check for Gravatar profile (default: false)
check_hibp (boolean): Check Have I Been Pwned breaches (default: false)
include_intelligence (boolean): Include DNSBL, spam trap, domain age, infrastructure analysis (default: false)
Returns: Markdown report with reachability, score, and check details.
Examples:
"Is john@acme.com a valid email?" -> { email: "john@acme.com" }
"Deep check on user@example.com" -> { email: "user@example.com", include_intelligence: true, check_hibp: true }
Credit cost: 1 credit (0 if syntax is invalid)
Error Handling:
Returns "Authentication failed..." if API key is invalid
Returns "Insufficient credits..." if balance is 0
Inputs: email (required), skip_smtp, check_gravatar, check_hibp, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool targets a distinct operation (batch download, status, verify, blacklist check, credits, domain intel, find email, infrastructure, list jobs, org intel, spam trap, verify email). No overlaps, even domain_intel suggests using specific tools for granular needs.
All tools follow a consistent deliveriq_verb_noun pattern (e.g., batch_verify, blacklist_check, find_email, org_intel). The prefix is uniform, and verbs clearly indicate actions.
12 tools are well-scoped for an email verification service, covering batch operations, single verification, intelligence, infrastructure, and account management. Neither too many nor too few.
The tool set covers the full verification lifecycle: single and batch verify, status polling, result download, intelligence, blacklist, infrastructure, spam trap, and account credits. Minor gap: no explicit cancel/delete for batch jobs, though batch_status provides monitoring.
Maintenance
Related MCP Connectors
Free SPF, DKIM, DMARC, blacklist, MX and bounce checks for any domain, as MCP tools for AI agents.
Email verification and domain intelligence for AI agents. MX, RDAP, SSL checks. 25 free credits.
Email verification and domain intelligence for AI agents, including single and bulk email checks.
Email for AI agents: send from your verified domain, track delivery, list mail, validate addresses.
Related MCP Servers
- FlicenseAqualityDmaintenanceA lightweight Model Context Protocol (MCP) server that enables your LLM to validate email addresses. This tool checks email format, domain validity, and deliverability using the AbstractAPI Email Validation API. Perfect for integrating email validation into AI applications like Claude Desktop.14-
- AlicenseAqualityCmaintenanceMailchimp MCP Server - Access Mailchimp data from Claude via MCP.100353 PyPI25MIT
- AlicenseBqualityDmaintenanceConnects DMARC monitoring data to AI assistants to facilitate the analysis of email security reports, domain details, and statistics. It allows users to manage security alerts, export report data, and monitor email authentication health through natural language commands.2145 npmMIT
- AlicenseAqualityCmaintenanceEmail validation MCP server using MailboxValidator API to determine validity of an email address.335 npm1MIT