Email Spam Tester

io.github.serg-tanichev由 GitHub 账号 serg-tanichev 发布v1.0.0更新于 Nov 2, 2026

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

已验证Streamable HTTP可网页运行沟通与协作商业与电商

概览

AI 生成的概览

远程 MCP 服务器，用于在发送前测试邮件的送达率：分配一次性测试地址，并返回带修复方案的评分报告。

可以做什么
  • 预留一次性测试地址，可选同时检测各邮箱服务商的投递位置，并取得报告链接
  • 阻塞等待分析完成，返回评分、未通过和警告的检查项以及修复方案
  • 按 slug 直接读取已有报告，无需等待
  • 获取邮件实际送达时的原始内容，包括头部、两个正文部分和原始源码
适用场景
适合在发送营销或事务性邮件前检查其反垃圾与送达表现，并让助手负责预留地址、等待结果并解释修复建议。对从个人笔记本发出的邮件意义有限，因为许多检查读取的是发送平台添加的头部。
运行要求
使用远程 streamable HTTP 端点，无需本地安装；不需要密钥或账号。不支持 streamable HTTP 的客户端可用 mcp-remote 桥接。需要本人从实际发送邮件的平台向预留地址发送真实邮件。
安装前请注意
报告 slug 就是唯一凭证：持有者即可读取报告，包括主题、发件人、退信地址和完整源码，未经同意不要测试他人的邮件。邮件源码在到达后保留一小时即删除。投递位置检测使用部分公开测试收件箱，请勿用于机密邮件。skip 状态不等于通过，complete 为 false 时评分偏乐观。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Email Spam Tester，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.serg-tanichev%2Femail-spam-tester/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

README

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:

bash
/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):

json
{  "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:

json
{  "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

bash
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.

来源：README.md，提交 4f2d7c2

工具

4

get_test_address

Get a 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.

输入参数langinclude_placement

wait_for_report

Wait for the 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.

输入参数slug必填timeout_seconds

get_report

Read a report

Read 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.

输入参数slug必填

get_message_source

Read the received message

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. 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.

输入参数slug必填

版本历史

1
  1. v1.0.0最新Sep 17, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。