echo.email Deliverability Test MCP Server

by echo Your server? Claim it

answering

echo.email Deliverability Test is answering right now. Last checked moments ago. It exposes 3 tools.

Send a test email, get SPF, DKIM, DMARC, TLS and IPv6 results plus sender rules. No key.

Uptime history 70 hours of history

70 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

131 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check echo.email Deliverability Test every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add deliverability --transport http https://mcp.echo.email/mcp

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

https://mcp.echo.email/mcp

~/.codex/config.toml

[mcp_servers.deliverability]
url = "https://mcp.echo.email/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "deliverability": {
      "url": "https://mcp.echo.email/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "deliverability": {
      "type": "http",
      "url": "https://mcp.echo.email/mcp"
    }
  }
}

Available tools 3

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

report

get_report

Fetch a finished report as JSON: the digest plus every check (SPF trace, DKIM, DMARC, BIMI, TLS, IPv6, images, links, unsubscribe, headers, DNS log).

test

create_test_address

Create a temporary echo.email address. Send one email to it from the system under test, then call wait_for_report with the returned token and key. The address dies after 10 minutes without a wait_for_report call and accepts one message.

wait

wait_for_report

Wait up to timeout_s seconds (max 50) for the email sent to a test address to be analysed. Returns status waiting or received (call again), or done with a digest: score, SPF, DKIM, DMARC, TLS, IPv6 and the failing sender requirements.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.echo.email/mcp	streamable-http	answering	48 ms	0 min ago

Alternatives to echo.email Deliverability Test

same job, measured the same way

Inbox Check — Email Deliverability Test

by live-direct-marketing

Email inbox placement tests across Gmail, Outlook, Yahoo, Mail.ru, Yandex (SPF/DKIM/DMARC).

76 installs/wk local only

Lettrove

by lettrove

Design emails from a brief, send tests, send to your lists now or scheduled, and read delivery.

answering

Resend Email MCP

by helbertparanhos

Complete Resend email MCP: full API coverage + debug layer (deliverability, DNS, bounces).

39 installs/wk local only

RevenueBase

by revenuebase

Find B2B contacts, inspect audience coverage, enrich emails, and verify deliverability.

answering

marginal

by marginal

Email A/B tests for AI agents: subject lines, managed sends, open/click tracking, and results.

answering

Pushizo

by pushizo

Push, email, SMS, in-app and journeys. 54 tools: reads and drafts; only test sends.

153 installs/wk answering

Randomuser MCP

by mrfentmen

Fake people for demos and tests: names, emails, addresses and photos from randomuser.me - keyless.

611 installs/wk local only

Agent Identity MCP

by flovoice53-tech

Gives an AI agent a disposable email and a real UK phone number to test signup flows.

114 installs/wk local only

echo.email Deliverability Test — questions

Answers built from our own checks of this server.

What can echo.email Deliverability Test do?

It exposes 3 tools, read directly from the server on our last check. Among them: create_test_address, get_report, wait_for_report. 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 echo.email Deliverability Test working right now?

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

How do I connect echo.email Deliverability Test?

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 echo.email Deliverability Test need an API key?

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

How fast is echo.email Deliverability Test?

It answers our handshake in 131 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.