# Mailvett: Email Validation API for AI Agents (remote · mailvett.cybermax-tools.workers.dev)

Mailvett: validate emails. MX, provider, disposable/role/free flags, typo fix, verdict.

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

## Components

- remote · `mailvett.cybermax-tools.workers.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/cybermax-tools-email-validate/mailvett.md), [page](https://verifymcp.io/servers/cybermax-tools-email-validate/mailvett)

## Channel facts

- Endpoint: `https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry`
- 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-28.

- **Endpoint Security**: 63/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 check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 179 tokens (~179/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 Mailvett: Email Validation API for AI Agents MCP server?

Mailvett: Email Validation API for AI Agents is a hosted endpoint at https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry, 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 cybermax-tools-email-validate 'https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "cybermax-tools-email-validate": {
      "url": "https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cybermax-tools-email-validate": {
      "type": "http",
      "url": "https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cybermax-tools-email-validate]
url = "https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cybermax-tools-email-validate": {
      "type": "remote",
      "url": "https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cybermax-tools-email-validate --url 'https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cybermax-tools-email-validate:
    url: "https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "cybermax-tools-email-validate": {
      "Transport": "http",
      "Url": "https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cybermax-tools-email-validate -t streamable-http -u 'https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "cybermax-tools-email-validate": {
      "type": "http",
      "url": "https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry"
    }
  }
}
```

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-28 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-26 (score 68)

First indexed and scored.

## MCP tools (1)

### `validate_emails` (~126 tokens)

Validate email addresses (no SMTP probing)

Check up to 10 email addresses: syntax, whether the domain exists and has mail servers (MX), mail provider, disposable, role account (info@, sales@), free provider, likely typo with a suggested fix, domain age, SPF and DMARC. Returns verdict (deliverable_likely/risky/undeliverable/invalid), score 0-100 and reason codes per address. Does not verify that the mailbox itself exists.

Input parameters:

- `emails` (array, required): Email addresses, also "Name <email>" or mailto: links. Up to 10.

## Diagnostics

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

## Score history

- 2026-09-28: 69
- 2026-09-27: 68
- 2026-09-26: 68

## Common questions

### What is the Mailvett: Email Validation API for AI Agents MCP server?

Mailvett: Email Validation API for AI Agents is an MCP server listed in the public MCP registry as io.github.CyberMax-tools/email-validate. Mailvett: validate emails. MX, provider, disposable/role/free flags, typo fix, verdict. This page covers its hosted endpoint (https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry).

### Is the Mailvett: Email Validation API for AI Agents MCP server safe to use?

Mailvett: Email Validation API for AI Agents scores 69 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 Mailvett: Email Validation API for AI Agents MCP server expose?

Mailvett: Email Validation API for AI Agents exposes 1 tool: validate_emails. Their descriptions and schemas cost roughly 126 tokens of context every time the server is loaded.

### Does the Mailvett: Email Validation API for AI Agents MCP server require authentication?

No. We connected to Mailvett: Email Validation API for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Mailvett: Email Validation API for AI Agents MCP server still maintained?

Mailvett: Email Validation API for AI Agents is still listed as active in the MCP registry. We last reached this channel on 28 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://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry
- Repository: https://github.com/CyberMax-tools/product-factory
- Website: https://mailvett.cybermax-tools.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/cybermax-tools-email-validate/mailvett.xml
- Changelog JSON feed: https://verifymcp.io/servers/cybermax-tools-email-validate/mailvett.json
- HTML version of this page: https://verifymcp.io/servers/cybermax-tools-email-validate/mailvett