Test a template
Test emails/receipt.html and tell me what a receiving server would object to.
Two warnings, both in the HTML. I can fix them here.
Zed
A remote server in settings.json is all it takes. The agent panel gets four tools for testing the mail your project sends.
42 checks · No key · No account
Use the settings screen or edit the file. The result is the same entry.
https://email-spam-tester.com/mcp{ "context_servers": { "email-spam-tester": { "url": "https://email-spam-tester.com/mcp" } }}Test a template
Test emails/receipt.html and tell me what a receiving server would object to.
Two warnings, both in the HTML. I can fix them here.
Clean the HTML
The report flags the image to text ratio. Rework this template and test again.
More text, one image removed. Testing again.
Check a domain's mail
Read this report and list what I change in DNS and what I change in code: [report link]
DNS: one record. Code: two headers.
Zed calls these context servers. Nothing runs on your machine, because the entry points at a hosted address.
/mcpget_test_addressReserves a one-hour address. With placement switched on, you also get a list of mailboxes at different providers.
wait_for_reportHolds until the checks finish, then returns the scores, the failed and warned checks with their evidence, and the fix plan.
get_reportReads an existing report by its slug, including how far the folder check has got.
get_message_sourceReturns the email as it arrived, headers in wire order, for an hour after delivery.
Nothing to install.
Nothing to slow the editor down.
About half of the checks read what the sending platform adds: the DKIM signature, the path through its servers, the unsubscribe headers. Pasted text has none of those, so the model would be guessing.
What you send to the test address. The raw message stays for an hour after it arrives and then only the report remains, at a link anyone with the slug can open. Test mail you would be fine showing a colleague, and read the privacy policy for the rest.
Yes. It is the same analysis and the same report page, so a run from a chat can be compared with one from the home page.
Zed can offer OAuth for a remote server with no Authorization header. This server needs no key and no account.
In your Zed settings.json, under context_servers.
Any model in the agent panel that can call tools.