Home / MCP registry index / io.github.MohDev212/verifypulse

VerifyPulse Email Verification & DNS Security

io.github.MohDev212/verifypulse in the official MCP registry. Endpoint https://verifypulse-seven.vercel.app/mcp. Source: github.com/MohDev212/verifypulse.

The registry describes it as: Real-time RFC 5322 email verification, SPF/DMARC DNS audits & B2B leads (x402 Base USDC).

We read its 12 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http verifypulse https://verifypulse-seven.vercel.app/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "verifypulse": {
      "url": "https://verifypulse-seven.vercel.app/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"verifypulse","type":"http","url":"https://verifypulse-seven.vercel.app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

inspect_domain_dns audit_sending_domains monitor_sending_domains watch_sending_domains flatten_spf get_fix_kit verify_email domain_intel check_tls_certificate check_blocklists analyze_email_authentication get_x402_payment_endpoints

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mohdev212-verifypulse/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mohdev212-verifypulse)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Email MCP servers · Crypto and Web3 MCP servers · Security MCP servers

AgentMart
ai.ciphyr.agentmart/agentmart
112 tools, nothing matched
2026-10-21
OSIR Domain Registrar
com.osir/domain-registrar
106 tools, nothing matched
2026-10-28
Fine Structure
ai.finestructure/fine-structure
99 tools, nothing matched
2026-10-21
Spur
com.usespur/spur
87 tools, nothing matched
2026-10-27
io.github.spruikco/send16-mcp
io.github.spruikco/send16-mcp
87 tools, nothing matched
2026-10-27
BlackVeil DNS & Email Security Scanner
com.blackveilsecurity/dns
81 tools, nothing matched
2026-10-22