email-spam-tester
Server Details
Test an email before it goes out: a disposable address, 41 checks with RFC citations, a fix plan.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- serg-tanichev/email-spam-tester-mcp
- GitHub Stars
- 0
- ChatGPT
- Email Spam Tester
- Claude
- Email Spam Tester
TDQS
Scored across 4 tools
Each tool has a fairly distinct role in the send-and-check workflow: get_test_address reserves an address, wait_for_report blocks for analysis, get_report reads the current report, and get_message_source retrieves the raw message. The only mild overlap is between wait_for_report and get_report, but their descriptions clearly differentiate blocking-summary versus immediate-read behavior.
Three of four tools follow a clean get_<noun> pattern (get_message_source, get_report, get_test_address), with wait_for_report the single deviation using a different verb. This is a minor, readable break rather than a chaotic mix.
Four tools cleanly map to one coherent lifecycle (reserve address, wait for analysis, read report, inspect raw source), so each earns its place. It is on the lean side but not thin enough to feel incomplete for the workflow.
The surface covers the full loop of reserving a test address, sending, awaiting analysis, reading the report, and inspecting the raw message source. Minor gaps exist (e.g. no listing/history of past reports or a way to re-trigger a check), but core workflows are covered.
Available Tools
4 toolsget_message_sourceRead the received messageARead-onlyIdempotentInspect
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.
Inputs: slug (required). Returns: result
get_reportRead a reportARead-onlyIdempotentInspect
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.
Inputs: slug (required). Returns: What every tool returns for the card; `view` says which card.
get_test_addressGet a test addressAInspect
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.
Inputs: lang, include_placement. Returns: What every tool returns for the card; `view` says which card.
wait_for_reportWait for the reportARead-onlyIdempotentInspect
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.
Inputs: slug (required), timeout_seconds. Returns: What every tool returns for the card; `view` says which card.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Verify emails (syntax, MX, SMTP mailbox, catch-all), test email DNS and check Spamhaus blocklists.
Verify email deliverability with RFC format, MX, SMTP and disposable-domain checks.
Check if an email address is real before you send, with a plain-English reason for every result.
Check whether an email address is real and will accept mail before you send to it.
Related MCP Servers
- AlicenseAqualityCmaintenanceChecks email deliverability: audits a domain's SPF (including the 10-lookup limit), DKIM, DMARC and MX records with ranked fixes, checks a sending IP's reverse DNS and blocklist listings, and tests email headers against Gmail and Yahoo bulk sender requirements.3MIT
- AlicenseAqualityDmaintenanceProgrammatic email deliverability testing for AI agents. Create inbox placement tests across Gmail, Outlook, Yahoo, Mail.ru, Yandex — get per-provider placement (Inbox/Spam/Promotions), SPF/DKIM/DMARC auth, Rspamd & SpamAssassin verdicts, DNS health (MX, PTR, DNSBL), and live SSE results.550 npm2MIT
- AlicenseAqualityBmaintenanceVerify email addresses in real time, without sending anything: a valid, risky, invalid or unknown status with a score, disposable, role-based and catch-all detection, and typo suggestions. Official local server of the MailProbe API, hosted in France.2123 npmMIT
- AlicenseNot gradedqualityBmaintenanceKeyless email validation: disposable/burner, role-account, and free-provider detection, MX checks, and typo suggestions. Tools: check_email, check_domain.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.