echo.email Deliverability Test MCP server
email.echo/deliverabilityecho.emailstreamable-httpv1.1.0Scanned
Send a test email, get SPF, DKIM, DMARC, TLS and IPv6 results plus sender rules. No key.
3 tools: 1 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- 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 echo.email Deliverability Test MCP server can do
The echo.email Deliverability Test MCP server is published by echo.email, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: create_test_address), but cannot delete data. 2 tools only read.
1 tool reads private data (wait_for_report); 1 tool brings in text other people can write (wait_for_report).
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.
Last scanned Nov 12, 2026, version 1.1.0.
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.
3 tools
Changes things 1Claude Code: ask
create_test_addressCreate a temporary echo.email address.No findings
Why it is in this group
- The name "create_test_address" says "create": a word for a change.
Description, as the server wrote it 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.
Only reads 2Show 2 read-only tools
get_reportFetch a finished report as JSON: the digest plus every check (SPF trace, DKIM, DMARC, BIMI, TLS, IPv6, images, links, unsubscribe, headers, DNS log).No findings
Why it is in this group
- The name "get_report" says "get": a word for reading.
Description, as the server wrote it Fetch a finished report as JSON: the digest plus every check (SPF trace, DKIM, DMARC, BIMI, TLS, IPv6, images, links, unsubscribe, headers, DNS log).
wait_for_reportWait up to timeout_s seconds (max 50) for the email sent to a test address to be analysed.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "wait_for_report" says "wait": a word for reading.
What it can reach
- private-dataThe description's first sentence says "wait" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "wait" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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 21, 2026, 19:23 UTC, unchanged since Oct 30, 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
- 1
- 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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.echo.email/mcp: tools/list returned 3 tools to an anonymous client, including create_test_address (write)
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http deliverability https://mcp.echo.email/mcpclaude mcp add --transport http deliverability https://mcp.echo.email/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__deliverability__wait_for_report",
"mcp__deliverability__get_report"
],
"ask": [
"mcp__deliverability__create_test_address"
],
"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 deliverability. Review it before you use it.
Capability tags behind 1 rule
- mcp__deliverability__wait_for_report private-data, 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/email.echo/deliverability/verify?hash=3725a6cc103bb2f31c71b28de77c5c32c950b5a73cc782835cf5be9c5d833201" | jq -e '.changed == false'Pinned hash 3725a6cc103b, from Nov 12, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/email.echo/deliverability/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/email.echo/deliverability)Source: MCP Registry. Synced Oct 30, 2026, 13:17 UTC.
echo.email Deliverability Test MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the echo.email Deliverability Test MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 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 echo.email Deliverability Test MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the echo.email Deliverability Test 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 echo.email Deliverability Test MCP server have?
- 3 tools: 1 write, 2 read. create_test_address, wait_for_report and get_report.
Does the echo.email Deliverability Test MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the echo.email Deliverability Test MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the echo.email Deliverability Test MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.