Email Spam Tester vs Mailtrap
A side-by-side look at the Email Spam Tester and Mailtrap 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 Mailtrap 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 Mailtrap when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MAILTRAP_API_TOKEN, MAILTRAP_ACCOUNT_ID, DEFAULT_FROM_EMAIL, MAILTRAP_SANDBOX_ID, MAILTRAP_TEST_INBOX_ID, MAILTRAP_ORGANIZATION_ID, MAILTRAP_ORGANIZATION_API_TOKEN. - You want tools like
send-email, batch-send-transactional-email, batch-send-bulk-email.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 82/100 · Excellent | 64/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 | MAILTRAP_API_TOKENMAILTRAP_ACCOUNT_IDDEFAULT_FROM_EMAILMAILTRAP_SANDBOX_IDMAILTRAP_TEST_INBOX_IDMAILTRAP_ORGANIZATION_IDMAILTRAP_ORGANIZATION_API_TOKEN |
| Verified owner | Verified | Community listing |
| GitHub stars | 2 | 66 |
| Directory activity | 6 views 0 installs 2 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 125 |
| Full listing | View Email Spam Tester | View Mailtrap |
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.
Mailtrap tools 125
send-emailSend an email to your recipient email address using Mailtrap Email API. You can send emails to multiple recipients at once.batch-send-transactional-emailSend a batch of transactional emails in one Mailtrap API call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Each request must include `to`.batch-send-bulk-emailSend a batch of bulk emails (Mailtrap bulk-stream API) in one call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Each request must include at least one of `to`/`cc`/`bcc`.create-templateCreate a new email templatelist-templatesList the account's email templates with page-token pagination (`token`, `per_page`). Pages are offsets over the newest-first list, so after deleting templates list again from token 1 instead of continuing with the next token.get-templateGet a single email template by ID, including subject, category, and HTML/text body.update-templateUpdate an existing email templatedelete-templateDelete an existing email templatesend-sandbox-emailSend an email in sandbox mode to a test inbox without delivering to your recipientsbatch-send-sandbox-emailSend a batch of emails in sandbox mode to a test inbox in one Mailtrap API call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Requires `sandbox_id` or the MAILTRAP_SANDBOX_ID env var.get-sandbox-messagesGet list of messages from the sandbox test inboxshow-sandbox-email-messageShow sandbox email message details and content from the sandbox test inbox. Optionally include spam report (SpamAssassin score) and HTML analysis (client compatibility) for email testing workflows.- +113 more on the listing page
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"
}
}
}
Mailtrap
{
"mcpServers": {
"mailtrap": {
"command": "npx",
"args": [
"-y",
"mcp-mailtrap"
],
"env": {
"MAILTRAP_API_TOKEN": "YOUR_MAILTRAP_API_TOKEN_HERE",
"MAILTRAP_ACCOUNT_ID": "YOUR_MAILTRAP_ACCOUNT_ID_HERE",
"DEFAULT_FROM_EMAIL": "YOUR_DEFAULT_FROM_EMAIL_HERE",
"MAILTRAP_SANDBOX_ID": "YOUR_MAILTRAP_SANDBOX_ID_HERE",
"MAILTRAP_TEST_INBOX_ID": "YOUR_MAILTRAP_TEST_INBOX_ID_HERE",
"MAILTRAP_ORGANIZATION_ID": "YOUR_MAILTRAP_ORGANIZATION_ID_HERE",
"MAILTRAP_ORGANIZATION_API_TOKEN": "YOUR_MAILTRAP_ORGANIZATION_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Email Spam Tester is categorized under Communication and uses a remote HTTP/SSE transport. Mailtrap belongs to Communication and uses a local stdio subprocess. Pick Email Spam Tester for communication work and Mailtrap 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. Mailtrap 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 mailtrap 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. Mailtrap has 64/100 (Good) with 0 views, 0 installs and 66 GitHub stars.