mcpbeat Sign in

Email Spam Tester MCP Server

by serg-tanichev Your server? Claim it
answering

Email Spam Tester is answering right now. Last checked 6 min ago. It exposes 4 tools. Last commit 12 Oct 2026.

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

Uptime history 46 days of history · worst day 97%
46 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
167 ms
Response time
average over 24h
2
Stars
last commit 12 Oct 2026

What changed 26

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 September 2026. No other catalogue keeps this.

12 Oct 2 tools changed the parameters they ask for get_message_source, get_report
12 Oct 2 tool descriptions were rewritten get_message_source, get_report
30 Sep 5 tools disappeared close_series_mailbox, get_series_letters, list_series_mailboxes and 2 more
30 Sep 5 tools appeared close_series_mailbox, get_series_letters, list_series_mailboxes and 2 more
30 Sep 4 tool descriptions were rewritten get_message_source, get_report, get_test_address and 1 more
30 Sep 3 tools changed the parameters they ask for4 times that day get_message_source, get_report, get_test_address
18 Sep 4 tools changed the parameters they ask for get_message_source, get_report, get_test_address and 1 more
and 1 more, back to 18 September 2026

Email Spam Tester missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add email-spam-tester --transport http https://email-spam-tester.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://email-spam-tester.com/mcp
~/.codex/config.toml
[mcp_servers.email-spam-tester]
url = "https://email-spam-tester.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "email-spam-tester": {
      "url": "https://email-spam-tester.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "email-spam-tester": {
      "type": "http",
      "url": "https://email-spam-tester.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

message
get_message_source
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.
report
get_report
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.
test
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, DMARC, reverse DNS, TLS, blocklists, content, links, the Gmail and Yahoo bulk-sender rules) and a plan of what to fix. lang is decided now because the message arrives minutes later over SMTP, which carries no hint of who is waiting for it. What wait_for_report returns quotes check lines in English whatever it is set to; the person following report_url sees their own language.
wait
wait_for_report
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 the latest.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

close_series_mailbox
removed 30 Sep 2026
get_series_letters
removed 30 Sep 2026
list_series_mailboxes
removed 30 Sep 2026
open_series_mailbox
removed 30 Sep 2026
write_fix_plan
removed 30 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://email-spam-tester.com/mcp streamable-http answering 167 ms 6 min ago

Alternatives to Email Spam Tester

same job, measured the same way
Disban
by disban

Check if a signup email is disposable, free, an alias, testing, parked or unknown, with evidence.

3 tools answering
fabricatedemail
by fabricatedemail

Disposable email addresses for tests and agents: register, wait for mail, extract codes and links.

answering
F
fixture.email — Email Testing for Agents
by fixture

Disposable test mailboxes on a real domain: send, receive and assert on real email.

answering
Agent Identity MCP
by flovoice53-tech

Gives an AI agent a disposable email and a real UK phone number to test signup flows.

114 installs/wk local only
Readfirst
by jeonghun917

What to read and check before changing a file: project rules, risks, checks and tests per file.

local only
ipvolt Proxy Toolkit
by ipvolt

Proxy guides, tested configurations and error diagnostics, with an optional local route check.

43 installs/wk 4 tools answering
Tewip
by hmamut39

Proves software work: triages failing tests, checks whether a test can fail, and reads migrations.

889 installs/wk local only
Tapp
by aarwitz

Test iOS, Android, and web apps with agent exploration, replayable flows, and CI gates.

3 902 installs/wk local only

Email Spam Tester — questions

Answers built from our own checks of this server.

What can Email Spam Tester do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_message_source, get_report, get_test_address, wait_for_report. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Email Spam Tester working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 167 ms. The bar chart above shows every period we have measured.
Did Email Spam Tester ever remove tools?
Yes. close_series_mailbox, get_series_letters, list_series_mailboxes, open_series_mailbox and 1 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Email Spam Tester?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Email Spam Tester need an API key?
No. Email Spam Tester completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Email Spam Tester?
It answers our handshake in 167 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Email Spam Tester open source?
We cannot say either way: 2 stars on GitHub and 1 open issue, but we could not determine the licence, and without one the code is not open source by default.