BounceProtect MCP Server vs Email Spam Tester

A side-by-side look at the BounceProtect MCP Server and Email Spam Tester MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

BounceProtect MCP Server logoBounceProtect MCP ServerCommunicationEmail validation and SMTP verification for Claude Desktop, Cursor, and Claude Code.29EmergingAuth: not declaredEmail Spam Tester logoEmail Spam TesterCommunication · Remote HTTP/SSEEmail 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.82ExcellentAuth: no auth required

Verdict: choose BounceProtect MCP Server for communication work; choose Email Spam Tester for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

BounceProtect MCP Server logoChoose BounceProtect MCP Server when

  • You need dedicated capabilities in the Communication domain.
  • You have the keys it needs: BOUNCEPROTECT_API_KEY.
Explore BounceProtect MCP Server

Email Spam Tester logoChoose 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.
Explore Email Spam Tester

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBounceProtect MCP Server logoBounceProtect MCP ServerEmail Spam Tester logoEmail Spam Tester
CategoryCommunicationCommunication
Quality signal29/100 · Emerging82/100 · Excellent
Install commandNot confirmed yetConfirmed
Transport—Remote HTTP/SSE
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsBOUNCEPROTECT_API_KEYNone listed
Verified ownerCommunity listing Verified
GitHub stars02
Directory activity 0 views 0 installs 0 upvotes 6 views 0 installs 2 upvotes
ToolsNot listed4

Tools & capabilities

BounceProtect MCP Server tools

No tool names declared yet. Check the project README from the listing page.

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.

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.

BounceProtect MCP Server

No confirmed install command for BounceProtect MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.

Email Spam Tester

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "email-spam-tester": {
      "url": "https://email-spam-tester.com/mcp"
    }
  }
}

Frequently asked questions

BounceProtect MCP Server is categorized under Communication and uses an install path we have not confirmed yet. Email Spam Tester belongs to Communication and uses a remote HTTP/SSE transport. Pick BounceProtect MCP Server for communication work and Email Spam Tester 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. BounceProtect MCP Server has no confirmed install command yet — follow its own setup instructions.

BounceProtect MCP Server has no declared pricing — check the project's own site. Email Spam Tester is listed as free. Auth: no auth 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 mcp-65 and email-spam-tester as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, BounceProtect MCP Server has a quality signal of 29/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Email Spam Tester has 82/100 (Excellent) with 6 views, 0 installs and 2 GitHub stars.