# io.github.serg-tanichev/email-spam-tester (remote · email-spam-tester.com)

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

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `email-spam-tester.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/serg-tanichev-email-spam-tester/email-spam-tester.md), [page](https://verifymcp.io/servers/serg-tanichev-email-spam-tester/email-spam-tester)

## Channel facts

- Endpoint: `https://email-spam-tester.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http serg-tanichev-email-spam-tester 'https://email-spam-tester.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "serg-tanichev-email-spam-tester": {
      "url": "https://email-spam-tester.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "serg-tanichev-email-spam-tester": {
      "type": "http",
      "url": "https://email-spam-tester.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.serg-tanichev-email-spam-tester]
url = "https://email-spam-tester.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "serg-tanichev-email-spam-tester": {
      "type": "remote",
      "url": "https://email-spam-tester.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add serg-tanichev-email-spam-tester --url 'https://email-spam-tester.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  serg-tanichev-email-spam-tester:
    url: "https://email-spam-tester.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "serg-tanichev-email-spam-tester": {
      "Transport": "http",
      "Url": "https://email-spam-tester.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add serg-tanichev-email-spam-tester -t streamable-http -u 'https://email-spam-tester.com/mcp'
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 73, +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.

### 2026-09-18 (score 72, +11)

- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “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

### 2026-09-17 (score 61)

First indexed and scored.

## MCP tools (4)

### `get_test_address` (~261 tokens)

Reserve a test address

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.

Input parameters:

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

Output parameters:

- `result` (string)

### `wait_for_report` (~125 tokens)

Wait for the report

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.

Input parameters:

- `slug` (string, required): 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.

Output parameters:

- `result` (string)

### `get_report` (~39 tokens)

Read a report

Read an existing report by its slug, without waiting.

Input parameters:

- `slug` (string, required): The slug of a test, the last part of the report URL.

Output parameters:

- `result` (string)

### `get_message_source` (~71 tokens)

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.

Input parameters:

- `slug` (string, required): The slug of a test whose message has already arrived.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/serg-tanichev-email-spam-tester/email-spam-tester#diagnostics

## Score history

- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 61

## Common questions

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

## Links

- Remote endpoint: https://email-spam-tester.com/mcp
- Repository: https://github.com/serg-tanichev/email-spam-tester-mcp
- Changelog RSS feed: https://verifymcp.io/servers/serg-tanichev-email-spam-tester/email-spam-tester.xml
- Changelog JSON feed: https://verifymcp.io/servers/serg-tanichev-email-spam-tester/email-spam-tester.json
- HTML version of this page: https://verifymcp.io/servers/serg-tanichev-email-spam-tester/email-spam-tester