# Email List Validation Email Verification (remote · app.emaillistvalidation.com)

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

- Trust score: 0/100 (low)
- Change this week: −68
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-11-01

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

## Components

- remote · `app.emaillistvalidation.com`: 0/100 (this document), [markdown](https://verifymcp.io/servers/com-emaillistvalidation-email-verification/app.md), [page](https://verifymcp.io/servers/com-emaillistvalidation-email-verification/app)

## Channel facts

- Endpoint: `https://app.emaillistvalidation.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-11-01.

- **Endpoint Security**: 0/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Email List Validation Email Verification MCP server?

Email List Validation Email Verification is a hosted endpoint at https://app.emaillistvalidation.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 com-emaillistvalidation-email-verification 'https://app.emaillistvalidation.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-emaillistvalidation-email-verification": {
      "url": "https://app.emaillistvalidation.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-emaillistvalidation-email-verification": {
      "type": "http",
      "url": "https://app.emaillistvalidation.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-emaillistvalidation-email-verification]
url = "https://app.emaillistvalidation.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-emaillistvalidation-email-verification --url 'https://app.emaillistvalidation.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-emaillistvalidation-email-verification:
    url: "https://app.emaillistvalidation.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-emaillistvalidation-email-verification": {
      "Transport": "http",
      "Url": "https://app.emaillistvalidation.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-emaillistvalidation-email-verification -t streamable-http -u 'https://app.emaillistvalidation.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-emaillistvalidation-email-verification": {
      "type": "http",
      "url": "https://app.emaillistvalidation.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-11-01 (score 0, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-31 (score 14, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-30 (score 27, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-29 (score 41, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-28 (score 54, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-26 (score 68, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Stability: 0.50 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-25 (score 68, +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 67, +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.

## 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/com-emaillistvalidation-email-verification/app#diagnostics

## Score history

- 2026-11-01: 0
- 2026-10-31: 14
- 2026-10-30: 27
- 2026-10-29: 41
- 2026-10-28: 54
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 68
- 2026-10-24: 67
- 2026-10-23: 67
- 2026-10-22: 66
- 2026-10-21: 66
- 2026-10-20: 65
- 2026-10-19: 65
- 2026-10-18: 64
- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 62
- 2026-10-13: 62
- 2026-10-12: 62
- 2026-10-11: 61
- 2026-10-10: 61

## Common questions

### What is the Email List Validation Email Verification MCP server?

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

### Is the Email List Validation Email Verification MCP server safe to use?

Email List Validation Email Verification scores 0 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 Email List Validation Email Verification MCP server expose?

Email List Validation 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 Email List Validation Email Verification MCP server require authentication?

Its publisher declares no required credentials for Email List Validation Email Verification. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Email List Validation Email Verification MCP server still maintained?

Email List Validation Email Verification has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 25 October 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://app.emaillistvalidation.com/mcp
- Website: https://app.emaillistvalidation.com/agent-gateway
- Changelog RSS feed: https://verifymcp.io/servers/com-emaillistvalidation-email-verification/app.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-emaillistvalidation-email-verification/app.json
- HTML version of this page: https://verifymcp.io/servers/com-emaillistvalidation-email-verification/app