VerifyPulse: email deliverability checks MCP Server

by mohdev212 Your server? Claim it

not responding

VerifyPulse: email deliverability checks is listed as active in the registry but did not answer our last check. It exposes 12 tools. Last commit 31 Oct 2026.

Daily SPF, DKIM, DMARC and MX monitoring with webhook alerts, plus free sending-domain audits.

Uptime history 29 days of history · worst day 8%

29 days agonow

8.8%

Uptime 24h

8 of 91 checks

Tools

read from the server

463 ms

Response time

average over 24h

Stars

last commit 31 Oct 2026

What changed 19

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 October 2026. No other catalogue keeps this.

29 Oct a tool appeared get_fix_kit

25 Oct 5 tools appeared analyze_email_authentication, check_blocklists, check_tls_certificate and 2 more

25 Oct 3 tool descriptions were rewritten audit_sending_domains, monitor_sending_domains, verify_email

13 Oct 3 tool descriptions were rewritten get_x402_payment_endpoints, inspect_domain_dns, verify_email

13 Oct 3 tools appeared audit_sending_domains, flatten_spf, monitor_sending_domains

13 Oct 2 tools changed the parameters they ask for inspect_domain_dns, verify_email

13 Oct a tool disappeared preview_b2b_leads

11 Oct a tool description was rewritten verify_email

VerifyPulse: email deliverability checks does not always answer

Over the last week it answered 23.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add verifypulse --transport http https://verifypulse-seven.vercel.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://verifypulse-seven.vercel.app/mcp

~/.codex/config.toml

[mcp_servers.verifypulse]
url = "https://verifypulse-seven.vercel.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "verifypulse": {
      "url": "https://verifypulse-seven.vercel.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "verifypulse": {
      "type": "http",
      "url": "https://verifypulse-seven.vercel.app/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

analyze

analyze_email_authentication

Free. Explain why an email passed or failed authentication or went to spam. Pass the raw message, or just its headers: checks DKIM signatures (verified when the body is included), whether the sending IP is authorized by SPF, DMARC alignment and policy, what the receiving server recorded, and delays at each relay hop. Returns the reasons in plain words.

audit

audit_sending_domains

Free for up to 3 domains per call. Audit several sending domains at once and get a grade, SPF lookup count, DMARC policy, DKIM status, MTA-STS (policy checked against the MX hosts), TLS-RPT, BIMI and fixes for each, plus a snapshot to pass to monitor_sending_domains later.

blocklists

check_blocklists

Free. Whether an IPv4 address, or a domain's MX and A addresses, are listed on the SpamCop and PSBL blocklists. Spamhaus and Barracuda are not queried (their terms require a subscription); the result says which lists were checked.

domain

domain_intel

Free. Registration data for one domain from the registry (RDAP): when it was registered and its age in days, expiry, registrar, status codes, nameservers and DNSSEC. Flags domains registered in the last 30 days, a strong spam and fraud signal, and domains about to expire.

fix

get_fix_kit

Fix a domain whose email goes to spam or fails SPF, DKIM or DMARC. Returns the exact DNS records to publish (host, type, value) for its mail provider, built from live DNS, in order, with the reason for each. Called without payment it returns a free preview of the fixes plus an x402 payment request for $0.25 USDC on Base (or 250 credits with api_key); a domain that needs no new records gets its advice free.

flatten

flatten_spf

Free. Replace the includes in a domain's SPF record with the IP ranges they resolve to, and return the TXT records to publish. Use it when an SPF record is at or over the 10-lookup limit.

inspect

inspect_domain_dns

Free. Audit one sending domain: MX hosts, SPF with every include expanded and the true DNS lookup count against the limit of 10, DMARC policy including inheritance from the parent domain, and published DKIM keys. Returns a grade and the fixes to make.

monitor

monitor_sending_domains

Free for up to 3 domains per call. Report what changed in SPF, DKIM, DMARC, MX, MTA-STS, TLS-RPT and BIMI since a previous run. Pass the `snapshots` object returned by the previous call as `previous`; the server stores nothing. The first call returns a baseline with no changes.

tls

check_tls_certificate

Free. The TLS certificate a host serves on port 443: whether it validates, issuer, names covered, expiry and days left.

verify

verify_email

Check an email address: syntax, whether its domain accepts mail, typo suggestion, disposable and shared-mailbox flags. Checks the domain, not the individual inbox. Costs one credit with an API key (POST /v1/agent/provision returns a key with 100 free credits), or $0.01 USDC on Base per call over x402.

watch

watch_sending_domains

Hosted monitoring. Register domains for a daily server-side check of SPF, DKIM, DMARC, MX, MTA-STS, TLS-RPT and BIMI; when something changes, the changes are POSTed as JSON to your https webhook_url. Free for up to 3 domains (renew every 30 days). For 4 to 20 domains in one watch, call without a pass: the result is an x402 payment request for the pass that covers them ($5 for up to 50 domains), payable in params._meta["x402/payment"] or with api_key credits; the paid call returns the pass and starts the watch. Returns a token to list or delete the watch.

x402

get_x402_payment_endpoints

List the paid HTTP endpoints, their prices in USDC on Base, and the free endpoints.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

preview_b2b_leads

removed 14 Oct 2026

Endpoints

URL	Transport	State	Latency	Checked
https://verifypulse-seven.vercel.app/mcp	streamable-http	answering	44 ms	11 min ago

Alternatives to VerifyPulse: email deliverability checks

same job, measured the same way

Mail Security Tools

by mailsecuritytools-api

DMARC/SPF/DKIM/MX checks, email score, 100-domain bulk score, webhook watch alerts (x402 USDC).

8 tools answering

ParseBounce

by parsebounce

Email deliverability monitoring and sending: bounces, complaints, suppression, campaigns.

answering

Agent Health

by autonet

Free owned-agent uptime monitoring, DNS domain proof, signed alerts and opt-in endpoint checks.

53 tools answering

Domain Sentinel

by domain-sentinel

Domain availability over RDAP, watchlists with daily or hourly checks, change history and alerts.

answering

Suped DMARC

by suped-com

DMARC monitoring, SPF/DKIM diagnostics, reports, domains and MSP client management with Suped.

answering

Uptimeify

by uptimeify

Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access.

20 tools answering

Palisade

by palisade

Monitor and manage email authentication (SPF, DKIM, DMARC, MTA-STS, BIMI) for your domains.

192 installs/wk answering

Agent Domains

by clize

Domains your AI agent can buy, point and monitor, with four-layer health checks and alerts.

72 installs/wk local only

VerifyPulse: email deliverability checks — questions

Answers built from our own checks of this server.

What can VerifyPulse: email deliverability checks do?

It exposes 12 tools, read directly from the server on our last check. Among them: analyze_email_authentication, audit_sending_domains, check_blocklists, check_tls_certificate, domain_intel, flatten_spf and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is VerifyPulse: email deliverability checks working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 8 of 91 checks got a reply (8.8%), average response time 463 ms. The bar chart above shows every period we have measured.

Did VerifyPulse: email deliverability checks ever remove tools?

Yes. preview_b2b_leads is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

The registry lists VerifyPulse: email deliverability checks as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect VerifyPulse: email deliverability checks?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does VerifyPulse: email deliverability checks need an API key?

No. VerifyPulse: email deliverability checks completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is VerifyPulse: email deliverability checks?

It answers our handshake in 463 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is VerifyPulse: email deliverability checks open source?

We cannot say either way: written in Python and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.