Winnr vs Email Spam Tester — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Winnr vs Email Spam Tester
In-depth architectural comparison of the Winnr and Email Spam Tester MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Winnr
Communication · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Email Spam Tester
Communication · Remote HTTP/SSE
Quality: 82/100 (Excellent) | Auth: No auth required
Verdict Summary: Choose Winnr if you need specialized Communication tools running via a local process. Choose Email Spam Tester if your workspace requires Communication integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
W
Choose Winnr when:
You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: WINNR_API_TOKEN.
Cold email infrastructure: buy domains, create SMTP mailboxes, set DNS, run warming, read mail.
Email deliverability testing for agents. Four tools: get a disposable test address, wait for the report once the message arrives, read it, and fetch the raw source. The report has 42 checks (SPF, DKIM, DMARC, 21 blocklists, two spam engines, Gmail and Yahoo bulk sender rules), each linked to its RFC, plus a fix plan. Remote endpoint, no API key.
Category & Scope
Tools & Capabilities Breakdown
Winnr Tools (54)
winnr_get_account
Account, plan, limits, and the calling token's scope
winnr_get_usage
Domains / email users / pre-warmed addresses vs limits
winnr_list_jobs
Recent async jobs (status / type filters)
winnr_get_job
One job's status, progress, result, error
winnr_wait_for_job
Block until a job finishes, streaming progress notifications
winnr_list_export_formats
Supported CSV formats
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Winnr is categorized under Communication and uses a local stdio subprocess. In contrast, Email Spam Tester belongs to Communication using remote streaming HTTP/SSE transport. Select Winnr when you need capabilities focused on communication and Email Spam Tester when you require tools for communication.
CSV of credentials (15-minute link), 22 sequencer formats
winnr_list_domains
List domains (paginated, optional status filter: complete, pending, …)
winnr_get_domain
One domain with DNS status and live health
winnr_search_domains
Availability + price for one name
winnr_search_domains_bulk
Availability + price for up to 100 names
winnr_get_dns_status
Provisioning/propagation state (MX, SPF, DKIM, DMARC)
+42 more tools listed on main page
Email Spam Tester Tools (4)
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_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.
get_report
Read a report by its slug without waiting, with provider placement so far.
Works for one-hour tests and for letters in the person's series mailboxes.
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, or to find the
confirmation link in a welcome letter.