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.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http email-spam-tester 'https://email-spam-tester.com/mcp'
{
"mcpServers": {
"email-spam-tester": {
"type": "http",
"url": "https://email-spam-tester.com/mcp"
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
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.
- Site: https://email-spam-tester.com/
- Agent guide: https://email-spam-tester.com/skill/
- API and examples: https://github.com/serg-tanichev/email-spam-tester
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:
| Tool | What 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
langwas set to;langdecides what the person opening the report URL sees. - A check status of
skipis not a pass: the check did not apply.errormeans it could not run and is left out of the score. complete: falsemeans 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
- MCP Registry, the official one, as
io.github.serg-tanichev/email-spam-tester - Smithery
- Glama
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.
Questions fréquentes
Qu'est-ce que 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.
Comment installer io.github.serg-tanichev/email-spam-tester ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http email-spam-tester 'https://email-spam-tester.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.serg-tanichev/email-spam-tester ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
io.github.serg-tanichev/email-spam-tester est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient io.github.serg-tanichev/email-spam-tester ?
Il est publié par serg-tanichev. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.