English Français العربية

io.github.serg-tanichev/email-spam-tester

Official registry Productivity

Test an email before it goes out: a disposable address, 41 checks with RFC citations, a fix plan.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http email-spam-tester 'https://email-spam-tester.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "email-spam-tester": {
            "type": "http",
            "url": "https://email-spam-tester.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Email Spam Tester MCP server
  2. Claude plugin
  3. Claude Desktop
  4. ChatGPT
  5. Claude Code
  6. Reading what comes back
  7. Where it is listed
  8. Files
  9. License

Email Spam Tester MCP server

Email Spam Tester is a free, independent email deliverability testing tool built by Serhii Tanichev. This repository is the client side of its MCP server: how to connect an agent to it, what the tools do, and how to read what they return. There is nothing to install on a server; the MCP endpoint is hosted with the tool.

The service exposes an MCP server at https://email-spam-tester.com/mcp over streamable HTTP. No key, no account. The one-hour test works in every client:

ToolWhat it does
get_test_address(lang, include_placement=false)Reserves a disposable address and returns it with the slug and the report URL. lang decides the language of the fix plan a person sees on the report page. With include_placement the same send also shows which folder the message lands in at different mailbox providers: you get one list of recipients and a marker for the subject. Some of those inboxes are public test inboxes, so use it for mail that is not confidential.
wait_for_report(slug, timeout_seconds=150)Blocks until the analysis is done and returns a summary: scores, the failing and warning checks with their evidence, the fix plan. Nothing to poll and no sleep loop to get wrong.
get_report(slug)Reads an existing report without waiting.
get_message_source(slug)The message as delivered: headers in wire order, both bodies, the raw source. It is kept for an hour after it arrives, and in that hour anyone with the slug can read it; after that only the report remains.

get_report also returns provider placement so far, when the test asked for it.

In ChatGPT there is more, because ChatGPT tells the server which of its users is asking. Permanent mailboxes collect a series of letters (a welcome sequence, a newsletter) and check every one: open_series_mailbox(domain), list_series_mailboxes(), get_series_letters(mailbox_id), write_fix_plan(slug) and close_series_mailbox(mailbox_id). Other clients, Claude among them, are not offered these tools: a permanent mailbox belongs to someone, and they don't say who is asking. Every tool also returns structured content for an MCP Apps card (ui://widget/email-spam-tester-v3.html): the address with copy buttons that turns into the report when the mail lands. Clients that draw no card read the same result as text.

The agent's job in between is to send a real message to the address, from the platform that will send the campaign. Half the checks read headers the sending platform adds, so a copy sent from a laptop says little about it.

Claude plugin

This repository is also a Claude plugin and its own marketplace. In Claude Code:

/plugin marketplace add serg-tanichev/email-spam-tester-mcp
/plugin install email-spam-tester@email-spam-tester

The plugin is two things and nothing else. .mcp.json connects Claude to the remote server at https://email-spam-tester.com/mcp, and skills/email-spam-tester/SKILL.md tells Claude how to run a test: reserve an address, have the real message sent to it, wait for the report, fix, test again. There is no local code, no hook and no script. What leaves your machine is what the tools send to that server (a report slug, a language code, whether you asked for provider placement), and the email you choose to send to the test address. What the service keeps, and for how long, is in the privacy policy.

Claude Desktop

Add the server to claude_desktop_config.json (see claude-desktop.json for the whole file):

{
  "mcpServers": {
    "email-spam-tester": {
      "url": "https://email-spam-tester.com/mcp"
    }
  }
}

Clients that do not speak streamable HTTP directly can bridge it with mcp-remote:

{
  "mcpServers": {
    "email-spam-tester": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://email-spam-tester.com/mcp"]
    }
  }
}

ChatGPT

The ChatGPT plugin package (manifest, icons, review test cases) is in serg-tanichev/email-spam-tester-chatgpt-plugin. Until it is in the plugin directory you can add the server yourself: Plugins → Add → Create MCP App, server URL https://email-spam-tester.com/mcp, no authentication.

Claude Code

claude mcp add --transport http email-spam-tester https://email-spam-tester.com/mcp

Reading what comes back

  • The per-check lines the tools return are in English whatever lang was set to; lang decides what the person opening the report URL sees.
  • A check status of skip is not a pass: the check did not apply. error means it could not run and is left out of the score.
  • complete: false means something could not be checked. Treat the score as optimistic until it is true.
  • The slug is the capability: whoever holds it can read the report, including the subject, the sender, the bounce address and the full source. Do not test somebody else's mail without asking.

The same instructions, written for an agent to read before it starts, are in SKILL.md, and in the project repository serg-tanichev/email-spam-tester.

Where it is listed

Files

  • claude-desktop.json: a complete Claude Desktop configuration with the server added.
  • server.json: the manifest in the MCP registry format, for registries and directories that read one.

License

MIT, see LICENSE. The license covers this repository, not the service.

Frequently asked questions

What is io.github.serg-tanichev/email-spam-tester?

Test an email before it goes out: a disposable address, 41 checks with RFC citations, a fix plan.

How do I install io.github.serg-tanichev/email-spam-tester?

It runs as a remote server. In Claude Code: claude mcp add --transport http email-spam-tester 'https://email-spam-tester.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.serg-tanichev/email-spam-tester need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.serg-tanichev/email-spam-tester open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.serg-tanichev/email-spam-tester?

It is published by serg-tanichev. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.