# MailValid Email Verification (remote · mailvalid.io)

Verify emails: syntax, MX, SMTP mailbox, disposable, role and catch-all checks. Single and bulk.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mailvalid.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-mailvalid-email-verifier/mailvalid.md), [page](https://verifymcp.io/servers/io-mailvalid-email-verifier/mailvalid)

## Channel facts

- Endpoint: `https://mailvalid.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-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_bulk_job).
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 400 tokens (~66/item across 6 items; 6 tools + 0 resources), lean.
  - 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**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MailValid Email Verification MCP server?

MailValid Email Verification is a hosted endpoint at https://mailvalid.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-mailvalid-email-verifier 'https://mailvalid.io/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "io-mailvalid-email-verifier": {
      "url": "https://mailvalid.io/mcp/"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.io-mailvalid-email-verifier]
url = "https://mailvalid.io/mcp/"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  io-mailvalid-email-verifier:
    url: "https://mailvalid.io/mcp/"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-mailvalid-email-verifier": {
      "type": "http",
      "url": "https://mailvalid.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-10-18 (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-10-16 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 62)

First indexed and scored.

## MCP tools (6)

### `verify_email` (~97 tokens)

Verify a single email's deliverability (syntax, DNS/MX, SMTP mailbox,
    disposable / role / catch-all detection, confidence score).

    Costs 1 credit for a billable result (valid/invalid/catch_all/do_not_mail),
    whether fresh or served from cache. `unknown` results are free. Requires an
    API key. Returns {success, credits_used, result}.

Input parameters:

- `email` (string, required)

### `submit_bulk_verification` (~89 tokens)

Queue a list of emails for asynchronous verification. Reserves up to N
    credits (final charge settles on completion). Poll get_bulk_job for status
    and results. Optionally provide webhook_url for a completion callback.
    Requires an API key. Returns {job_id, status, total_emails, credits_reserved}.

Input parameters:

- `emails` (array, required)
- `webhook_url`

### `get_bulk_job` (~45 tokens)

Get the status, progress, and (when complete) results of a bulk job by
    its job_id. Requires an API key.

Input parameters:

- `job_id` (string, required)

### `list_bulk_jobs` (~54 tokens)

List your recent bulk verification jobs (paginated, newest first).
    Optionally filter by status. Requires an API key.

Input parameters:

- `page` (integer)
- `page_size` (integer)
- `status`

### `cancel_bulk_job` (~36 tokens)

Cancel a pending or processing bulk job and release any reserved credits.
    Requires an API key.

Input parameters:

- `job_id` (string, required)

### `get_credit_balance` (~23 tokens)

Return your current credit balance and lifetime usage. Requires an API key.

## Diagnostics

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

## Score history

- 2026-10-18: 64
- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 62

## Common questions

### What is the MailValid Email Verification MCP server?

MailValid Email Verification is an MCP server listed in the public MCP registry as io.mailvalid/email-verifier. Verify emails: syntax, MX, SMTP mailbox, disposable, role and catch-all checks. Single and bulk. This page covers its hosted endpoint (https://mailvalid.io/mcp/).

### Is the MailValid Email Verification MCP server safe to use?

MailValid Email Verification scores 64 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 MailValid Email Verification MCP server expose?

MailValid Email Verification exposes 6 tools: verify_email, submit_bulk_verification, get_bulk_job, list_bulk_jobs, cancel_bulk_job, get_credit_balance. Their descriptions and schemas cost roughly 344 tokens of context every time the server is loaded.

### Does the MailValid Email Verification MCP server require authentication?

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

### Is the MailValid Email Verification MCP server still maintained?

MailValid Email Verification is still listed as active in the MCP registry. We last reached this channel on 18 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://mailvalid.io/mcp/
- Authorisation metadata: https://mailvalid.io/.well-known/oauth-protected-resource/mcp
- Website: https://mailvalid.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-mailvalid-email-verifier/mailvalid.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-mailvalid-email-verifier/mailvalid.json
- HTML version of this page: https://verifymcp.io/servers/io-mailvalid-email-verifier/mailvalid