Email Spam Tester vs Leadmagic — MCP Server Comparison | AllMCPs
Email Spam Tester vs Leadmagic
A side-by-side look at the Email Spam Tester and Leadmagic 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 Leadmagic 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.
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.
Leadmagic tools
No tool names declared yet. Check the project README from 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 is categorized under Communication and uses a remote HTTP/SSE transport. Leadmagic belongs to Communication and uses a local stdio subprocess. Pick Email Spam Tester for communication work and Leadmagic 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. Leadmagic is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 leadmagic 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. Leadmagic has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.