# Email List Validation Email Verification

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

- name: com.emaillistvalidation/email-verification
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.emaillistvalidation%2Femail-verification
- tools: https://api.protogrid.dev/v1/servers/com.emaillistvalidation%2Femail-verification/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "email-verification": {
      "type": "http",
      "url": "https://app.emaillistvalidation.com/mcp",
      "headers": {
        "Authorization": "Bearer ${EMAIL_VERIFICATION_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${EMAIL_VERIFICATION_TOKEN}`.

## Trust

- hygiene: 80
- liveness: 99
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-98% +updated-12d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2024-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_lists (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_list (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify_batch (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 771 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 1 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 9, about 771 tokens to load them all
- tool set hash: 74da004c6a032d7b429a6cbc5cb45109
- tools last changed: 2026-10-12T16:15:01.151Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.emaillistvalidation/email-verification.svg)](https://protogrid.dev/servers/com.emaillistvalidation/email-verification)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-12 `get_api_key` changed (description)
  - before: Get a free API key for this server (no account needed; 25 email verifications per day). Returns the key once — reconnect with 'Authorization: Bearer <api_key>' to use the other tools.
  - after: 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.

Full history: https://api.protogrid.dev/v1/servers/com.emaillistvalidation%2Femail-verification/changes

## Remotes

- https://app.emaillistvalidation.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.9782609)

## Packages

_none_

## Tools (9)

- `estimate_cost`: 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.
- `explain_result`: 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.
- `get_api_key`: 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.
- `get_batch_status`: Get the progress and status of a bulk verification list/job by id.
- `get_credit_balance`: Get the current credit balance and a short usage summary for the account.
- `get_list`: Get the details of a single bulk verification list by its id.
- `list_lists`: List the user's bulk verification lists/jobs, most recent first.
- `verify_batch`: 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.
- `verify_email`: Verify the deliverability of a single email address. Returns a verdict (valid, invalid, risky, unknown). Costs 1 credit.
