Deliveriq Mcp

io.github.Davison-FrancisPublished by GitHub account Davison-Francisv1.1.1Updated Oct 25, 2026

Email deliverability for AI agents. 12 tools: verify, DNSBL, DMARC, spam-trap, finder.

VerifiedSTDIODesktop onlyCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that gives an assistant 12 DeliverIQ tools to verify emails, check DNSBL, DMARC and spam-trap risk, and find business emails.

What you can do
Verify single emails and submit, track, download and list batch verification jobs as CSV results, with credit costs per email or job shown in the README table of tools and credits, where batch status, download and job listing are free and single verification costs one credit per email and batch verification one credit per email submitted, so the assistant can plan and branch on results across several calls as the README's rationale for MCP describes, and it can also find business emails by name and domain, check a domain against 50 DNSBL zones, analyze SPF, DKIM, DMARC, MTA-STS and BIMI infrastructure, evaluate spam-trap risk across 13 signals, pull domain trust and organization email-patter
When to use it
Use it when an assistant needs to check whether email addresses are deliverable, audit a sending domain's authentication and blocklist reputation, or look up business contacts, instead of switching to a separate dashboard.
Requirements
Node.js 18+ and a DeliverIQ API key in the DELIVERIQ_API_KEY environment variable (format lc_*), obtained by signing up at the provider's site; the free tier covers demo and low-volume use. An optional DELIVERIQ_BASE_URL overrides the default API endpoint. Runs locally over stdio via npx.
Before you install
The API key is a secret passed in plain text in client config files. Tools consume paid credits: single verification costs 1 credit, batch verification 1 credit per email, email finder 2 credits, and the intelligence checks 1 credit each, so usage can spend money. Batch submission sends lists of email addresses to the third-party DeliverIQ API.

Installation

In SourceWeft

  1. Open Deliveriq Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@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.

[npm] [License: MIT] [Davison-Francis/min8t-sdks MCP server]

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):

json
{  "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

bash
claude mcp add deliveriq npx -y @deliveriq/mcp \  -e DELIVERIQ_API_KEY=lc_your_api_key

Cursor

Add to .cursor/mcp.json:

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.

Environment Variables

VariableRequiredDescription
DELIVERIQ_API_KEYYesAPI key (format: lc_prefix_secret)
DELIVERIQ_BASE_URLNoOverride API URL (default: https://api.min8t.com/deliverability/v1)

Tools (12)

Verification

ToolDescriptionCredits
deliveriq_verify_emailVerify a single email for deliverability1
deliveriq_batch_verifySubmit batch of emails for async verification1/email
deliveriq_batch_statusCheck batch job status and progressFree
deliveriq_batch_downloadDownload completed batch results as CSVFree
deliveriq_list_jobsList verification jobs with paginationFree

Intelligence

ToolDescriptionCredits
deliveriq_find_emailFind business email by name + domain2
deliveriq_blacklist_checkCheck domain against 50 DNSBL zones1
deliveriq_infrastructure_checkAnalyze SPF/DKIM/DMARC/MTA-STS/BIMI1
deliveriq_spam_trap_analysisEvaluate spam trap risk (13 signals)1
deliveriq_domain_intelComprehensive domain trust report1
deliveriq_org_intelQuery organization email patternsFree

Account

ToolDescriptionCredits
deliveriq_check_creditsCheck credit balance and usage statsFree

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

bash
# Clone the monorepogit clone https://github.com/Davison-Francis/min8t-sdks.gitcd min8t-sdks/deliveriq-mcp
# Install + buildnpm installnpm run build
# Watch modenpm run dev
# Run directly against the published APIDELIVERIQ_API_KEY=lc_your_key node dist/index.js
# Or against a local DeliverIQ serviceDELIVERIQ_API_KEY=lc_test \  DELIVERIQ_BASE_URL=http://localhost:3019/api/v1 \  node dist/index.js

Requirements

  • 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.

Source: deliveriq-mcp/README.md at commit 6ba8636

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts