echo.email Deliverability Test
REMOTE · MCP.ECHO.EMAIL
Send a test email, get SPF, DKIM, DMARC, TLS and IPv6 results plus sender rules. No key.
Available components
Last scanned (1 hour ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 239 tokens (~79/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.echo.email/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=echo.email | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | dc45b5cc1c81164f0e6b4d819fab4701 |
| SANs: echo.email, mcp.echo.email, *.mcp.echo.email | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.echo.email. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| email. | present | 53311 | 8 | Verified |
| echo.email. | present | 2371 | 13 | Verified |
| mcp.echo.email. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.echo.email/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.echo.email/mcp | HTTPS enforced | 301 | https://mcp.echo.email/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_test_address Create test address ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_report Get report ~58
Fetch a finished report as JSON: the digest plus every check (SPF trace, DKIM, DMARC, BIMI, TLS, IPv6, images, links, unsubscribe, headers, DNS log).
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
wait_for_report Wait for report ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Key from create_test_address |
| timeout_s | number | – | – |
| token | string | yes | Token from create_test_address (the address local part) |
No output schema declared.
No examples provided.
How do I install the echo.email Deliverability Test MCP server?
echo.email Deliverability Test is a hosted endpoint at https://mcp.echo.email/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.
remote · mcp.echo.email
claude mcp add --transport http email-echo-deliverability 'https://mcp.echo.email/mcp'
What is the echo.email Deliverability Test MCP server?
echo.email Deliverability Test is an MCP server listed in the public MCP registry as email.echo/deliverability. Send a test email, get SPF, DKIM, DMARC, TLS and IPv6 results plus sender rules. No key. This page covers its hosted endpoint (https://mcp.echo.email/mcp).
Is the echo.email Deliverability Test MCP server safe to use?
echo.email Deliverability Test scores 65 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 echo.email Deliverability Test MCP server expose?
echo.email Deliverability Test exposes 3 tools: create_test_address, wait_for_report, get_report. Their descriptions and schemas cost roughly 219 tokens of context every time the server is loaded.
Does the echo.email Deliverability Test MCP server require authentication?
No. We connected to echo.email Deliverability Test without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the echo.email Deliverability Test MCP server still maintained?
echo.email Deliverability Test 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.