Name: Domain Deliverability Checker
Author: mambalabsdev

LABSCO SUMMARY

The three records only mean something together, and returning them as one report is the difference between data and an answer.

SPF, DKIM and DMARC each pass or fail individually, and the useful question — will this domain's mail be accepted — depends on how they combine. A DMARC policy of reject with a misaligned SPF is worse than no DMARC at all, and three separate lookups leave that inference to the caller. One tool, one report, one interpretation is the right shape for this question. Narrow by design: it audits and does not fix, and the recommendation of what to change is still yours to derive from what it reports.

What it is

A single-tool email deliverability auditor: it checks a domain's SPF, DKIM and DMARC configuration along with its DNS health and returns the result as one report.

What you get

check_domain_deliverability returns the three authentication records and the DNS health around them, rather than requiring three separate lookups and their interpretation.

Requirements

APIFY_TOKEN — it runs through Apify, so usage draws on that account.

Setup effort

One command plus a key — npx -y @mambalabsdev/mcp-domain-deliverability-checker, then supply credentials

See installation options

USE CASES

01

Finding out why mail from a domain is being rejected

Audit SPF, DKIM and DMARC together with the DNS health behind them, rather than checking three records and inferring how they interact.

check_domain_deliverability

02

Checking a domain before you send from it

Run the audit as a pre-flight on a newly configured sending domain, so a failure is found before a campaign is.

check_domain_deliverability

1 tool

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`check_domain_deliverability`

Audit a domain's email deliverability and DNS health. Returns SPF, DKIM, and DMARC authentication with policy, MX records and mail provider, DNS blacklist status, catch-all detection, domain age, and a 0 to 100 health score as a flat, Clay-ready JSON row. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.

BEFORE YOU INSTALL

What to know first

Tools you get

1 tool when we connected. Pass domains instead of domain to audit up to ten at once. skipCache bypasses the 24 hour cache; attempt_catch_all is off by default because Apify blocks port 25.

Requires

npx on PATH
Node.js 18 or later
APIFY_TOKEN in your environment

Where it runs

The documented client runs the server on your machine.

CONTEXT COST

Light Standing cost

Rated by the size of the one tool definition that rides along on every turn

INSTALLATION

Connect your client

Server setup

TERMINAL

npx -y @mambalabsdev/mcp-domain-deliverability-checker

MCP Clients

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "mamba-domain-deliverability-checker": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-deliverability-checker"
      ],
      "env": {
        "APIFY_TOKEN": "<YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Domain Deliverability Checker