Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VerifyPulse: email deliverability checks

REMOTE · VERIFYPULSE-SEVEN.VERCEL.APP

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

+4 this week 76 Trust /100

Last scanned (23 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1281 tokens (~106/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management49
  • Stability check failed: schema churn in the 23 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 9 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 45 to 49.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 39 to 42.

  • 31 Oct 26 +1
    • Tool “watch_sending_domains” rewrote its description, which is the text the model reads security
  • 29 Oct 26 +1
    • Tool “watch_sending_domains” rewrote its description, which is the text the model reads security
    • Schema quality: 1131 → 1281 ▼ functional
    • New tool “get_fix_kit” functional
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 15 to 19.

  • 25 Oct 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “audit_sending_domains” rewrote its description, which is the text the model reads security
    • Tool “monitor_sending_domains” rewrote its description, which is the text the model reads security
    • Tool “verify_email” rewrote its description, which is the text the model reads security
    • Schema quality: 85 → 102 ▼ functional
    • The server now declares the “prompts” capability functional
    • First check of Schema quality: 100 functional
    • New prompt “check_sending_domain” functional
    • New prompt “watch_my_domains” functional
    • New prompt “why_did_this_email_fail” functional
    • New tool “analyze_email_authentication” functional
    • New tool “check_blocklists” functional
    • New tool “check_tls_certificate” functional
    • New tool “domain_intel” functional
    • New tool “watch_sending_domains” functional
  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 5 to 9.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 2.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://verifypulse-seven.vercel.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of verifypulse-seven.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
vercel.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://verifypulse-seven.vercel.app/mcp Verified 200
http (plaintext) http://verifypulse-seven.vercel.app/mcp HTTPS enforced 308 https://verifypulse-seven.vercel.app/mcp
MCP tools · 12 exposed · ~1,208 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_email_authentication ~97

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.

NameTypeReqDescription
rawstringyesThe full message source, or its headers

No output schema declared.

No examples provided.

audit_sending_domains ~90

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.

NameTypeReqDescription
domainsarrayyesUp to 3 domains

No output schema declared.

No examples provided.

check_blocklists ~74

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.

NameTypeReqDescription
targetstringyesIPv4 address or domain

No output schema declared.

No examples provided.

check_tls_certificate ~54

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

NameTypeReqDescription
hoststringyesHost name, for example mta-sts.example.com

No output schema declared.

No examples provided.

domain_intel ~82

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.

NameTypeReqDescription
domainstringyesDomain, for example stripe.com

No output schema declared.

No examples provided.

flatten_spf ~66

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.

NameTypeReqDescription
domainstringyesDomain whose SPF record to flatten

No output schema declared.

No examples provided.

get_fix_kit ~150

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.

NameTypeReqDescription
api_keystring–Optional VerifyPulse API key (vp_...): pays 250 credits instead of x402
domainstringyesThe sending domain, for example yourcompany.com

No output schema declared.

No examples provided.

get_x402_payment_endpoints ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inspect_domain_dns ~77

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.

NameTypeReqDescription
domainstringyesDomain to audit, for example stripe.com

No output schema declared.

No examples provided.

monitor_sending_domains ~117

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.

NameTypeReqDescription
domainsarrayyesUp to 3 domains
previousobject–The `snapshots` object from the previous call, or omit on the first run

No output schema declared.

No examples provided.

verify_email ~124

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.

NameTypeReqDescription
api_keystring–Optional VerifyPulse API key (vp_...) or Base USDC transaction hash (0x...)
emailstringyesEmail address to check, for example founder@stripe.com

No output schema declared.

No examples provided.

watch_sending_domains ~246

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.

NameTypeReqDescription
api_keystring–Optional VerifyPulse API key: pays for a pass with credits when more than 3 domains are watched
domainsarrayyesDomains to watch: up to 3 free, more with a pass
guard_passstring–Optional Sender Guard pass (vpg_...) for more than 3 domains
webhook_urlstringyesPublic https URL that receives the change alerts, for example a Slack incoming webhook

No output schema declared.

No examples provided.

Install

How do I install the VerifyPulse: email deliverability checks MCP server?

VerifyPulse: email deliverability checks is a hosted endpoint at https://verifypulse-seven.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · verifypulse-seven.vercel.app

# add to Claude Code
claude mcp add --transport http mohdev212-verifypulse 'https://verifypulse-seven.vercel.app/mcp'
Common questions

What is the VerifyPulse: email deliverability checks MCP server?

VerifyPulse: email deliverability checks is an MCP server listed in the public MCP registry as io.github.MohDev212/verifypulse. Daily SPF, DKIM, DMARC and MX monitoring with webhook alerts, plus free sending-domain audits. This page covers its hosted endpoint (https://verifypulse-seven.vercel.app/mcp).

Is the VerifyPulse: email deliverability checks MCP server safe to use?

VerifyPulse: email deliverability checks scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VerifyPulse: email deliverability checks MCP server expose?

VerifyPulse: email deliverability checks exposes 12 tools: inspect_domain_dns, audit_sending_domains, monitor_sending_domains, watch_sending_domains, flatten_spf, and 7 more. Their descriptions and schemas cost roughly 1,208 tokens of context every time the server is loaded.

Does the VerifyPulse: email deliverability checks MCP server require authentication?

No. We connected to VerifyPulse: email deliverability checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VerifyPulse: email deliverability checks MCP server still maintained?

VerifyPulse: email deliverability checks is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.