io.github.serg-tanichev/email-spam-tester
REMOTE · EMAIL-SPAM-TESTER.COM · SCANNED SEP 20
Test an email before it goes out: a disposable address, 41 checks with RFC citations, a fix plan.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 544 tokens (~136/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.serg-tanichev/email-spam-tester MCP server?
io.github.serg-tanichev/email-spam-tester is a hosted endpoint at https://email-spam-tester.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · email-spam-tester.com
claude mcp add --transport http serg-tanichev-email-spam-tester 'https://email-spam-tester.com/mcp'
{
"mcpServers": {
"serg-tanichev-email-spam-tester": {
"url": "https://email-spam-tester.com/mcp"
}
}
} {
"servers": {
"serg-tanichev-email-spam-tester": {
"type": "http",
"url": "https://email-spam-tester.com/mcp"
}
}
} [mcp_servers.serg-tanichev-email-spam-tester] url = "https://email-spam-tester.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"serg-tanichev-email-spam-tester": {
"type": "remote",
"url": "https://email-spam-tester.com/mcp",
"enabled": true
}
}
} openclaw mcp add serg-tanichev-email-spam-tester --url 'https://email-spam-tester.com/mcp' --transport streamable-http
mcp_servers:
serg-tanichev-email-spam-tester:
url: "https://email-spam-tester.com/mcp" {
"McpServers": {
"serg-tanichev-email-spam-tester": {
"Transport": "http",
"Url": "https://email-spam-tester.com/mcp"
}
}
} assistant mcp add serg-tanichev-email-spam-tester -t streamable-http -u 'https://email-spam-tester.com/mcp'
{
"mcpServers": {
"serg-tanichev-email-spam-tester": {
"type": "http",
"url": "https://email-spam-tester.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +11
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- “get_message_source” reworded the description of “slug” cosmetic
- “get_report” reworded the description of “slug” cosmetic
- “get_test_address” reworded the description of “lang” cosmetic
- “wait_for_report” reworded the description of “slug” cosmetic
- “wait_for_report” reworded the description of “timeout_seconds” cosmetic
- Tool “get_message_source” changed its title: Read the received message cosmetic
- Tool “get_report” changed its title: Read a report cosmetic
- Tool “get_test_address” changed its title: Reserve a test address cosmetic
- Tool “wait_for_report” changed its title: Wait for the report cosmetic
- 17 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://email-spam-tester.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_CHACHA20_POLY1305_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=email-spam-tester.com | CN=YR2,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | RSA 4096 | SHA256-RSA | 6b933405158c2c1598ed29fff1c4a8e6022 |
| SANs: email-spam-tester.com, www.email-spam-tester.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of email-spam-tester.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| email-spam-tester.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://email-spam-tester.com/mcp | Verified | 200 | |
| http (plaintext) | http://email-spam-tester.com/mcp | HTTPS enforced | 302 | https://email-spam-tester.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_message_source Read the received message ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug of a test whose message has already arrived. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_report Read a report ~39
Read an existing report by its slug, without waiting.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug of a test, the last part of the report URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_test_address Reserve a test address ~261
Reserve a single-use address to send a draft message to. Returns the address and the URL its report will appear at. The address accepts exactly one message and expires after an hour. lang is the language the fix plan will be written in, as an ISO code ("de", "pt-BR"). Set it to the language the person you are working for reads: it decides the plan and the per-check findings on the page they open, and it has to be decided now because the message arrives minutes later over SMTP, which carries no hint of who is waiting for it. Unknown codes fall back to English rather than failing. What you get back from wait_for_report stays English whatever you set: the check lines it quotes come from the report's `summary` field, which is English by design so a script reading it reads the same words every time. The person following report_url sees their own language.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | 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". Unknown codes fall back to English. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
wait_for_report Wait for the report ~125
Wait until the message arrives and has been analysed, then summarise it. Blocks rather than returning "not ready yet": an agent told to poll writes a sleep loop and usually gives up before the analysis finishes.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug get_test_address returned, the last part of the report URL. |
| timeout_seconds | integer | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.serg-tanichev/email-spam-tester MCP server?
io.github.serg-tanichev/email-spam-tester is an MCP server listed in the public MCP registry as 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. This page covers its hosted endpoint (https://email-spam-tester.com/mcp).
Is the io.github.serg-tanichev/email-spam-tester MCP server safe to use?
io.github.serg-tanichev/email-spam-tester scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.serg-tanichev/email-spam-tester MCP server expose?
io.github.serg-tanichev/email-spam-tester exposes 4 tools: get_test_address, wait_for_report, get_report, get_message_source. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.
Does the io.github.serg-tanichev/email-spam-tester MCP server require authentication?
No. We connected to io.github.serg-tanichev/email-spam-tester without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.serg-tanichev/email-spam-tester MCP server still maintained?
io.github.serg-tanichev/email-spam-tester is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.