# VerifyPulse: email deliverability checks (remote · verifypulse-seven.vercel.app)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `verifypulse-seven.vercel.app`: 76/100 (this document), [markdown](https://verifymcp.io/servers/mohdev212-verifypulse/verifypulse-seven.md), [page](https://verifymcp.io/servers/mohdev212-verifypulse/verifypulse-seven)

## Channel facts

- Endpoint: `https://verifypulse-seven.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1281 tokens (~106/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 52/100
  - Stability check failed: schema churn in the 24 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 9 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http mohdev212-verifypulse 'https://verifypulse-seven.vercel.app/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mohdev212-verifypulse": {
      "type": "remote",
      "url": "https://verifypulse-seven.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mohdev212-verifypulse --url 'https://verifypulse-seven.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mohdev212-verifypulse:
    url: "https://verifypulse-seven.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mohdev212-verifypulse": {
      "Transport": "http",
      "Url": "https://verifypulse-seven.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mohdev212-verifypulse -t streamable-http -u 'https://verifypulse-seven.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mohdev212-verifypulse": {
      "type": "http",
      "url": "https://verifypulse-seven.vercel.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +1)

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

### 2026-11-02 (score 75, +1)

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

### 2026-10-31 (score 74, +1)

- [security] Tool “watch_sending_domains” rewrote its description, which is the text the model reads

### 2026-10-29 (score 73, +1)

- [security] Tool “watch_sending_domains” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1131 → 1281
- [functional] New tool “get_fix_kit”

### 2026-10-26 (score 72, +1)

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

### 2026-10-25 (score 71, +2)

- [security] 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
- [functional regression] 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”

### 2026-10-23 (score 69, +1)

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

### 2026-10-21 (score 68, +1)

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

## MCP tools (12)

### `inspect_domain_dns` (~77 tokens)

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.

Input parameters:

- `domain` (string, required): Domain to audit, for example stripe.com

### `audit_sending_domains` (~90 tokens)

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.

Input parameters:

- `domains` (array, required): Up to 3 domains

### `monitor_sending_domains` (~117 tokens)

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.

Input parameters:

- `domains` (array, required): Up to 3 domains
- `previous` (object): The `snapshots` object from the previous call, or omit on the first run

### `watch_sending_domains` (~246 tokens)

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.

Input parameters:

- `api_key` (string): Optional VerifyPulse API key: pays for a pass with credits when more than 3 domains are watched
- `domains` (array, required): Domains to watch: up to 3 free, more with a pass
- `guard_pass` (string): Optional Sender Guard pass (vpg_...) for more than 3 domains
- `webhook_url` (string, required): Public https URL that receives the change alerts, for example a Slack incoming webhook

### `flatten_spf` (~66 tokens)

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.

Input parameters:

- `domain` (string, required): Domain whose SPF record to flatten

### `get_fix_kit` (~150 tokens)

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.

Input parameters:

- `api_key` (string): Optional VerifyPulse API key (vp_...): pays 250 credits instead of x402
- `domain` (string, required): The sending domain, for example yourcompany.com

### `verify_email` (~124 tokens)

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.

Input parameters:

- `api_key` (string): Optional VerifyPulse API key (vp_...) or Base USDC transaction hash (0x...)
- `email` (string, required): Email address to check, for example founder@stripe.com

### `domain_intel` (~82 tokens)

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.

Input parameters:

- `domain` (string, required): Domain, for example stripe.com

### `check_tls_certificate` (~54 tokens)

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

Input parameters:

- `host` (string, required): Host name, for example mta-sts.example.com

### `check_blocklists` (~74 tokens)

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.

Input parameters:

- `target` (string, required): IPv4 address or domain

### `analyze_email_authentication` (~97 tokens)

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.

Input parameters:

- `raw` (string, required): The full message source, or its headers

### `get_x402_payment_endpoints` (~31 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mohdev212-verifypulse/verifypulse-seven#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 71
- 2026-10-24: 69
- 2026-10-23: 69
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 67
- 2026-10-19: 67
- 2026-10-18: 67
- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 67
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 66

## 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://verifypulse-seven.vercel.app/mcp
- Repository: https://github.com/MohDev212/verifypulse-mcp
- Website: https://verifypulse-seven.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/mohdev212-verifypulse/verifypulse-seven.xml
- Changelog JSON feed: https://verifymcp.io/servers/mohdev212-verifypulse/verifypulse-seven.json
- HTML version of this page: https://verifymcp.io/servers/mohdev212-verifypulse/verifypulse-seven