# Emaillistchecker.io Email Verification (remote · platform.emaillistchecker.io)

Verify emails (valid/invalid/risky/unknown): MX, SMTP, catch-all, disposable. Free agent key.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `platform.emaillistchecker.io`: 75/100 (this document), [markdown](https://verifymcp.io/servers/io-emaillistchecker-email-verification/platform.md), [page](https://verifymcp.io/servers/io-emaillistchecker-email-verification/platform)

## Channel facts

- Endpoint: `https://platform.emaillistchecker.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **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 9 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**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 681 tokens (~75/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the Emaillistchecker.io Email Verification MCP server?

Emaillistchecker.io Email Verification is a hosted endpoint at https://platform.emaillistchecker.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-emaillistchecker-email-verification 'https://platform.emaillistchecker.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-emaillistchecker-email-verification": {
      "url": "https://platform.emaillistchecker.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-emaillistchecker-email-verification": {
      "type": "http",
      "url": "https://platform.emaillistchecker.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-emaillistchecker-email-verification]
url = "https://platform.emaillistchecker.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-emaillistchecker-email-verification --url 'https://platform.emaillistchecker.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-emaillistchecker-email-verification:
    url: "https://platform.emaillistchecker.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-emaillistchecker-email-verification": {
      "Transport": "http",
      "Url": "https://platform.emaillistchecker.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-emaillistchecker-email-verification -t streamable-http -u 'https://platform.emaillistchecker.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-emaillistchecker-email-verification": {
      "type": "http",
      "url": "https://platform.emaillistchecker.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-05 (score 75, +1)

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

### 2026-11-02 (score 74, +1)

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

### 2026-10-31 (score 73, +1)

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

### 2026-10-29 (score 72, +1)

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

### 2026-10-27 (score 71, +1)

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

### 2026-10-25 (score 70, +1)

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

### 2026-10-23 (score 69, +1)

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

### 2026-10-21 (score 68, +1)

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

## MCP tools (9)

### `get_api_key` (~106 tokens)

Get your own free API key for this server (no account needed; 25 email verifications per day). Optional: the verification tools already work without a key on a shared trial. Returns the key once — reconnect with 'Authorization: Bearer <api_key>' for your own quota and the list tools.

Input parameters:

- `contact` (string): Optional operator email or URL.
- `name` (string): Your agent's name.
- `purpose` (string): What you verify emails for.

### `get_credit_balance` (~23 tokens)

Get the current credit balance and a short usage summary for the account.

### `list_lists` (~33 tokens)

List the user's bulk verification lists/jobs, most recent first.

Input parameters:

- `limit` (integer): Maximum number of lists to return.

### `get_list` (~36 tokens)

Get the details of a single bulk verification list by its id.

Input parameters:

- `list_id` (integer, required): The id of the bulk verification list.

### `explain_result` (~112 tokens)

Explain what a verification status or reason means in plain English, with a send recommendation. Covers valid, invalid, catch-all/accept-all, unknown, greylisted, disposable, role, free, spam-trap, abuse, do-not-mail, no-mx, disabled, and network. Use when a user asks what a result means.

Input parameters:

- `term` (string, required): The status/reason to explain, e.g. 'catch-all', 'GREYLISTED', 'unknown', 'role'. Case-insensitive.

### `verify_email` (~47 tokens)

Verify the deliverability of a single email address. Returns a verdict (valid, invalid, risky, unknown). Costs 1 credit.

Input parameters:

- `email` (string, required): The email address to verify.

### `verify_batch` (~67 tokens)

Verify a batch of email addresses (up to 25 per call with an agent key). Returns per-email verdicts and saves a list. Costs 1 credit per email.

Input parameters:

- `emails` (array, required): Email addresses to verify.
- `name` (string): Optional label for the saved list.

### `estimate_cost` (~116 tokens)

Estimate the credit cost of a verification before running it, and whether the user can afford it. Provide either a count of emails, a list_id to re-verify, or an operation ('single'/'finder'). Always quote this before proposing anything billable.

Input parameters:

- `emails` (integer): Number of emails to verify (1 credit each).
- `list_id` (integer): Estimate re-verifying an existing list by its id.
- `operation` (string): Operation type: bulk/single (1 credit) or finder (3 credits).

### `get_batch_status` (~31 tokens)

Get the progress and status of a bulk verification list/job by id.

Input parameters:

- `list_id` (integer, required)

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 70
- 2026-10-25: 70
- 2026-10-24: 69
- 2026-10-23: 69
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 67
- 2026-10-19: 67
- 2026-10-18: 67
- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 65
- 2026-10-14: 65
- 2026-10-13: 64
- 2026-10-12: 64
- 2026-10-11: 63
- 2026-10-10: 63

## Common questions

### What is the Emaillistchecker.io Email Verification MCP server?

Emaillistchecker.io Email Verification is an MCP server listed in the public MCP registry as io.emaillistchecker/email-verification. Verify emails (valid/invalid/risky/unknown): MX, SMTP, catch-all, disposable. Free agent key. This page covers its hosted endpoint (https://platform.emaillistchecker.io/mcp).

### Is the Emaillistchecker.io Email Verification MCP server safe to use?

Emaillistchecker.io Email Verification scores 75 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 Emaillistchecker.io Email Verification MCP server expose?

Emaillistchecker.io Email Verification exposes 9 tools: get_api_key, get_credit_balance, list_lists, get_list, explain_result, and 4 more. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.

### Does the Emaillistchecker.io Email Verification MCP server require authentication?

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

### Is the Emaillistchecker.io Email Verification MCP server still maintained?

Emaillistchecker.io Email Verification is still listed as active in the MCP registry. We last reached this channel on 5 November 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://platform.emaillistchecker.io/mcp
- Repository: https://github.com/Emaillistchecker-io/emaillistchecker-mcp
- Website: https://platform.emaillistchecker.io/agent-gateway
- Changelog RSS feed: https://verifymcp.io/servers/io-emaillistchecker-email-verification/platform.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-emaillistchecker-email-verification/platform.json
- HTML version of this page: https://verifymcp.io/servers/io-emaillistchecker-email-verification/platform