Email Spam Tester vs EmptyInbox
A side-by-side look at the Email Spam Tester and EmptyInbox MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Email Spam Tester for communication work over a hosted endpoint; choose EmptyInbox for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Email Spam Tester when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
get_test_address, wait_for_report, get_report.
Choose EmptyInbox when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You want tools like
register_account, get_quota, create_inbox.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 82/100 · Excellent | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 2 | 4 |
| Directory activity | 6 views 0 installs 2 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | 12 |
| Full listing | View Email Spam Tester | View EmptyInbox |
Tools & capabilities
Email Spam Tester tools 4
get_test_addressReserve 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_for_reportWait 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.get_reportRead 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_sourceThe 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.
EmptyInbox tools 12
register_accountRegister a new EmptyInbox account and get an API key. Use this only if there is no account configured yet, or if authentication is failing. Prefer reusing an existing key: repeatedly registering from one network reduces the free credits each new account receives. Saves the key locally for future sessions.get_quotaCheck how many inbox credits remain on this account. When credits are low, the result says how to buy more with Bitcoin.create_inboxCreate a new disposable email inbox. Returns the email address and when it expires (30 days). Use this before triggering any signup or email verification flow.keep_inboxMake an inbox permanent so it never expires, for 30 credits. Use when the address was used to sign up for an account the user will keep (password resets go there). Ask the user first. Also brings back an expired inbox: addresses are never given to anyone else. Free if the inbox is already permanent.list_inboxesList all email inboxes on this account, with when each expires (null = permanent) and whether it already has.list_messagesList received email messages, newest first, already parsed: each entry carries the extracted one-time code, the link to open, and a text preview — no HTML parsing needed. Filter by inbox and use limit to keep responses small.get_messageGet one email message by ID. Returns the parsed message: extracted code, action_url, every link with its anchor text, and the body as plain text. Set format='text' for a flat rendering to read directly, or include_html=true only if the raw HTML is genuinely needed.wait_for_messagePoll an inbox until a new message arrives. Use after triggering an email verification, OTP, or signup confirmation. Returns the parsed message — including the extracted code and the link to open — as soon as it lands, or a timeout result.buy_quotaBuy inbox credits with Bitcoin. Only call this after the user has chosen a bundle or amount. Returns a pay_url to give the user: a page with a QR code, the exact amount and a live payment status, which works with any Bitcoin wallet. Also returns the raw address, amount and BIP21 URI for paying directly. Credits are added as soon as the payment is seen on the network. Call check_payment once the user has paid.list_bundlesList the inbox credit bundles for sale and their USD prices, paid in Bitcoin. Show these to the user before calling buy_quota.check_paymentCheck whether a Bitcoin payment from buy_quota has landed. Pass wait_seconds (around 120) once the user says they have paid, to wait for the credits in one call. Credit usually arrives within seconds of broadcast, well before confirmation.report_issueSend feedback to the EmptyInbox team: a bug, a failed or abandoned payment, confusing docs, or a missing feature. A human reads every report. Use it when a tool fails in a way retrying will not fix, or when the user decides not to buy and says why. Never include passwords, verification codes, API keys or email contents.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Email Spam Tester
{
"mcpServers": {
"email-spam-tester": {
"url": "https://email-spam-tester.com/mcp"
}
}
}
EmptyInbox
{
"mcpServers": {
"emptyinbox": {
"command": "npx",
"args": [
"-y",
"emptyinbox-mcp"
]
}
}
}
Frequently asked questions
Email Spam Tester is categorized under Communication and uses a remote HTTP/SSE transport. EmptyInbox belongs to Communication and uses a local stdio subprocess. Pick Email Spam Tester for communication work and EmptyInbox for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Email Spam Tester is listed as free. Auth: no auth required. EmptyInbox has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add email-spam-tester and emptyinbox as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Email Spam Tester has a quality signal of 82/100 (Excellent) with 6 views, 0 installs and 2 GitHub stars. EmptyInbox has 63/100 (Good) with 1 views, 0 installs and 4 GitHub stars.