Remote MCP server that creates temporary email addresses and returns deliverability reports on a test message: SPF, DKIM, DMARC, TLS, IPv6 and sender rules.
What you can do
Create a temporary echo.email test address and get back a token and key
Wait for the email sent to that address to be analysed, polling until a digest is ready
Fetch the finished report as JSON with the digest plus every check: SPF trace, DKIM, DMARC, BIMI, TLS, IPv6, images, links, unsubscribe, headers and DNS log
When to use it
Use it when you need to verify that outgoing email from a system under test authenticates and passes common sender requirements, for example after changing DNS records or mail configuration. It suits quick, one-message checks rather than ongoing monitoring.
Requirements
A remote MCP endpoint; no package, API key, environment variable or header is declared. The workflow needs the ability to send one real email from the system under test to the generated address, and the test address expires after 10 minutes without a wait_for_report call.
Before you install
The test address accepts one message and dies after 10 minutes without a wait_for_report call, so timing matters. The email content is sent to a third-party service for analysis, so avoid including sensitive data in the test message. No authentication is declared.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/email.echo%2Fdeliverability/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Takes no parameters.
wait_for_report
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.
Parameterskeyrequiredtokenrequiredtimeout_s
get_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).
Parametersreport_idrequired
Version history
1
v1.1.0LatestOct 30, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.