# ihateemail.io (remote · ihateemail.io)

Check a domain's SPF, DKIM, DMARC, MX, TLS and blacklists, and get the DNS records to fix it.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `ihateemail.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-ihateemail-ihateemail/ihateemail.md), [page](https://verifymcp.io/servers/io-ihateemail-ihateemail/ihateemail)

## Channel facts

- Endpoint: `https://ihateemail.io/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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 214 tokens (~107/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ihateemail.io MCP server?

ihateemail.io is a hosted endpoint at https://ihateemail.io/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 io-ihateemail-ihateemail 'https://ihateemail.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-ihateemail-ihateemail": {
      "url": "https://ihateemail.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-ihateemail-ihateemail": {
      "type": "http",
      "url": "https://ihateemail.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-ihateemail-ihateemail]
url = "https://ihateemail.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-ihateemail-ihateemail": {
      "type": "remote",
      "url": "https://ihateemail.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-ihateemail-ihateemail --url 'https://ihateemail.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-ihateemail-ihateemail:
    url: "https://ihateemail.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-ihateemail-ihateemail": {
      "Transport": "http",
      "Url": "https://ihateemail.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-ihateemail-ihateemail -t streamable-http -u 'https://ihateemail.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-ihateemail-ihateemail": {
      "type": "http",
      "url": "https://ihateemail.io/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-11-21 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 62)

First indexed and scored.

## MCP tools (2)

### `check_domain` (~123 tokens)

Check a domain's email setup

Checks a domain's SPF, DKIM, DMARC, MX and TLS, blacklists, website and age, the way Gmail, Yahoo and Microsoft judge a sender. Returns a setup score out of 100, a readiness verdict, and each problem with how to fix it. Also accepts a public IPv4 address (blacklists and reverse DNS).

Input parameters:

- `domain` (string, required): Domain (example.com) or public IPv4 address
- `selector` (string): DKIM selector to check, if known (the s= value in a DKIM-Signature header)

### `generate_records` (~61 tokens)

Write the DNS records to publish

Returns the SPF, DKIM, DMARC and MX records the domain should publish, based on the providers it already uses, each marked add, replace, keep or configure, with the reason.

Input parameters:

- `domain` (string, required)
- `selector` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 63
- 2026-11-17: 63
- 2026-11-16: 62

## Common questions

### What is the ihateemail.io MCP server?

ihateemail.io is an MCP server listed in the public MCP registry as io.ihateemail/ihateemail. Check a domain's SPF, DKIM, DMARC, MX, TLS and blacklists, and get the DNS records to fix it. This page covers its hosted endpoint (https://ihateemail.io/mcp).

### Is the ihateemail.io MCP server safe to use?

ihateemail.io scores 65 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 ihateemail.io MCP server expose?

ihateemail.io exposes 2 tools: check_domain, generate_records. Their descriptions and schemas cost roughly 184 tokens of context every time the server is loaded.

### Does the ihateemail.io MCP server require authentication?

No. We connected to ihateemail.io without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ihateemail.io MCP server still maintained?

ihateemail.io is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the ihateemail.io MCP server?

VerifyMCP ran 12 checks on ihateemail.io, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ihateemail.io: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ihateemail.io/mcp
- Website: https://ihateemail.io/docs/api#mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-ihateemail-ihateemail/ihateemail.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-ihateemail-ihateemail/ihateemail/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-ihateemail-ihateemail/ihateemail.json
- HTML version of this page: https://verifymcp.io/servers/io-ihateemail-ihateemail/ihateemail
