email-spam-tester
Test an email before it goes out: a disposable address, 41 checks with RFC citations, a fix plan.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"email-spam-tester": {
"url": "https://email-spam-tester.com/mcp"
}
}
}Remote endpoints
https://email-spam-tester.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (4)
🟡get_test_address(lang, include_placement)
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.
Input Schema
{
"type": "object",
"properties": {
"lang": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "ISO code of the language the report and the fix plan are written in for the person who opens the report page, for example \"en\", \"de\" or \"pt-BR\". Defaults to the language of the conversation. Unknown codes fall back to English.",
"title": "Lang"
},
"include_placement": {
"default": false,
"description": "Also check which folder (inbox, spam, promotions) the email lands in at different mailbox providers, from the same send. The email then goes to a list of recipients instead of one address and needs a marker in the subject; both come back. Some provider inboxes are public test inboxes: the subject, the sender name and the folder are shown on a public web page, so it suits messages that are not confidential.",
"title": "Include Placement",
"type": "boolean"
}
},
"title": "get_test_addressArguments"
}Output Schema
{
"type": "object",
"properties": {
"view": {
"description": "test, report, mailbox, mailboxes, series or error",
"title": "View",
"type": "string"
}
},
"required": [
"view"
],
"additionalProperties": true,
"description": "What every tool returns for the card; `view` says which card.",
"title": "Output"
}🟢wait_for_report(slug, timeout_seconds)
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.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"description": "The slug get_test_address returned, the last part of the report URL.",
"title": "Slug",
"type": "string"
},
"timeout_seconds": {
"default": 150,
"description": "How long to block waiting for the message and its analysis, in seconds. The checks are ready in well under a minute; the fix plan takes about another one. Past this the tool returns what it has.",
"maximum": 600,
"minimum": 5,
"title": "Timeout Seconds",
"type": "integer"
}
},
"required": [
"slug"
],
"title": "wait_for_reportArguments"
}Output Schema
{
"type": "object",
"properties": {
"view": {
"description": "test, report, mailbox, mailboxes, series or error",
"title": "View",
"type": "string"
}
},
"required": [
"view"
],
"additionalProperties": true,
"description": "What every tool returns for the card; `view` says which card.",
"title": "Output"
}🟢get_report(slug)
Read a report by its slug without waiting, with provider placement so far. Works for one-hour tests and for letters in the person's series mailboxes.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"description": "The slug of a test or of a letter in a series mailbox, the last part of the report URL.",
"title": "Slug",
"type": "string"
}
},
"required": [
"slug"
],
"title": "get_reportArguments"
}Output Schema
{
"type": "object",
"properties": {
"view": {
"description": "test, report, mailbox, mailboxes, series or error",
"title": "View",
"type": "string"
}
},
"required": [
"view"
],
"additionalProperties": true,
"description": "What every tool returns for the card; `view` says which card.",
"title": "Output"
}🟢get_message_source(slug)
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, or to find the confirmation link in a welcome letter.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"description": "The slug of a test or a series letter whose message has already arrived.",
"title": "Slug",
"type": "string"
}
},
"required": [
"slug"
],
"title": "get_message_sourceArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "get_message_sourceOutput"
}Community
Evidence