VerifyPulse: email deliverability checks MCP server
io.github.MohDev212/verifypulseMohDev212streamable-httpv2.1.1Scanned
Daily SPF, DKIM, DMARC and MX monitoring with webhook alerts, plus free sending-domain audits.
12 tools: 8 change things and 4 only read.
- Reads private data · 2
- Reads text others write · 3
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
8 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the VerifyPulse: email deliverability checks MCP server can do
The VerifyPulse: email deliverability checks MCP server is published by the GitHub account MohDev212. It has 12 tools. It can create or change data (8 tools: audit_sending_domains, monitor_sending_domains, watch_sending_domains, flatten_spf and 4 more), but cannot delete data. 4 tools only read.
2 tools read private data (get_fix_kit and analyze_email_authentication); 3 tools bring in text other people can write (get_fix_kit, analyze_email_authentication and get_x402_payment_endpoints); 1 tool can send data out of your system (watch_sending_domains). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 2.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Changes things 8Claude Code: ask
audit_sending_domainsFree for up to 3 domains per call.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
check_blocklistsFree.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
check_tls_certificateFree.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Free. The TLS certificate a host serves on port 443: whether it validates, issuer, names covered, expiry and days left.
domain_intelFree.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
flatten_spfFree.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
monitor_sending_domainsFree for up to 3 domains per call.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
verify_emailCheck an email address: syntax, whether its domain accepts mail, typo suggestion, disposable and shared-mailbox flags.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_sending_domainsHosted monitoring.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Only reads 4Show 4 read-only tools
analyze_email_authenticationFree.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "analyze_email_authentication" says "analyze": a word for reading.
What it can reach
- private-dataThe name "analyze_email_authentication" says "analyze" and "email": it reads mail.
- untrusted-inputThe name "analyze_email_authentication" says "analyze" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
get_fix_kitFix a domain whose email goes to spam or fails SPF, DKIM or DMARC.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_fix_kit" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
get_x402_payment_endpointsList the paid HTTP endpoints, their prices in USDC on Base, and the free endpoints.Reads text others writeNo findings
Why it is in this group
- The name "get_x402_payment_endpoints" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it List the paid HTTP endpoints, their prices in USDC on Base, and the free endpoints.
inspect_domain_dnsFree.No findings
Why it is in this group
- The name "inspect_domain_dns" says "inspect": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__verifypulse__watch_sending_domains"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:59 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://verifypulse-seven.vercel.app/mcp: tools/list returned 12 tools to an anonymous client, including audit_sending_domains (write), monitor_sending_domains (write), watch_sending_domains (write), flatten_spf (write), verify_email (write) and 3 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 4 to 8
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:watch_sending_domainsChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 8.View diff
- Tools that change things, listed without credentials: 4 to 8
Tools6 added, 3 changed.+6 added~3 changedView diff
- Added:analyze_email_authenticationOnly reads
- Added:check_blocklistsChanges things
- Added:check_tls_certificateChanges things
- Added:domain_intelChanges things
- Added:get_fix_kitOnly reads
- Added:watch_sending_domainsChanges things
- Changed:audit_sending_domainsChanges thingsdescription
- Changed:monitor_sending_domainsChanges thingsdescription
- Changed:verify_emailChanges thingsdescription
Install
Pinned to version 2.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http verifypulse https://verifypulse-seven.vercel.app/mcpclaude mcp add --transport http verifypulse https://verifypulse-seven.vercel.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__verifypulse__inspect_domain_dns",
"mcp__verifypulse__get_fix_kit",
"mcp__verifypulse__analyze_email_authentication",
"mcp__verifypulse__get_x402_payment_endpoints"
],
"ask": [
"mcp__verifypulse__audit_sending_domains",
"mcp__verifypulse__monitor_sending_domains",
"mcp__verifypulse__watch_sending_domains",
"mcp__verifypulse__flatten_spf",
"mcp__verifypulse__verify_email",
"mcp__verifypulse__domain_intel",
"mcp__verifypulse__check_tls_certificate",
"mcp__verifypulse__check_blocklists"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as verifypulse. Review it before you use it.
Capability tags behind 4 rules
- mcp__verifypulse__watch_sending_domains outbound
- mcp__verifypulse__get_fix_kit private-data, untrusted-input
- mcp__verifypulse__analyze_email_authentication private-data, untrusted-input
- mcp__verifypulse__get_x402_payment_endpoints untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.MohDev212/verifypulse/verify?hash=bf0859c5c2e47a92c249b0086ec3da95c5de056cdeed5a81766c85b65ea53c82" | jq -e '.changed == false'Pinned hash bf0859c5c2e4, from Nov 13, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.MohDev212/verifypulse/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.MohDev212/verifypulse)Source: MCP Registry · repository. Synced Oct 31, 2026, 17:17 UTC.
VerifyPulse: email deliverability checks MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the VerifyPulse: email deliverability checks MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the VerifyPulse: email deliverability checks MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the VerifyPulse: email deliverability checks MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the VerifyPulse: email deliverability checks MCP server have?
- 12 tools: 8 write, 4 read. audit_sending_domains, monitor_sending_domains, watch_sending_domains, flatten_spf, verify_email, domain_intel, check_tls_certificate, check_blocklists and 4 more.
Does the VerifyPulse: email deliverability checks MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the VerifyPulse: email deliverability checks MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): watch_sending_domains.
Has the VerifyPulse: email deliverability checks MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.