ES

Email Spam Tester

io.github.serg-tanichev/email-spam-tester

Test an email before it goes out: a disposable address, 41 checks with RFC citations, a fix plan.

Yes, your AI can use this right now.Answered a live MCP handshake in 783 ms with no sign-in needed and exposes 4 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://email-spam-tester.com/mcp

4 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
get_test_address

Reserve a single-use address to send a draft email to, for a full check. Returns the address and the URL its report will appear at. The address accepts exactly one message and expires after an hour. The email has to be sent by the person, from the platform or mailbox they really send from: half the checks read what that platform adds. The report covers 42 checks (SPF, DKIM, DM

wait_for_reportread-only

Wait until the message arrives and has been analysed, then summarise it. Call it after the email has been sent to the address from get_test_address. Blocks rather than returning "not ready yet": an agent told to poll writes a sleep loop and usually gives up before the analysis finishes. Provider placement keeps filling in for up to 30 minutes after the report; get_report reads

get_reportread-only

Read a report by its slug without waiting, with provider placement so far. The report stays at its link for good and anyone with the link can read it: the checks, the score, the fix plan, and the subject and sender of the email.

get_message_sourceread-only

The message exactly as it was received: headers, both bodies, source. Useful when a finding points at a header and the agent needs to see what it actually sent rather than what it believes it sent. The message is kept for an hour after it arrives and then deleted; within that hour anyone with the slug can read it. After that only the report remains.

Alternatives in Developer Tools

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”