# Email Check (remote · email-check.david-cyr.workers.dev)

Fast email validation at the edge: syntax, MX records, disposable-domain detection.

- Trust score: 70/100 (medium)
- Change this week: +52
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `email-check.david-cyr.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dawaxwx-email-check/email-check.md), [page](https://verifymcp.io/servers/dawaxwx-email-check/email-check)

## Channel facts

- Endpoint: `https://email-check.david-cyr.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - 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**: 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 Check MCP server?

Email Check is a hosted endpoint at https://email-check.david-cyr.workers.dev/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 dawaxwx-email-check 'https://email-check.david-cyr.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dawaxwx-email-check": {
      "url": "https://email-check.david-cyr.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dawaxwx-email-check": {
      "type": "http",
      "url": "https://email-check.david-cyr.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dawaxwx-email-check]
url = "https://email-check.david-cyr.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dawaxwx-email-check": {
      "type": "remote",
      "url": "https://email-check.david-cyr.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dawaxwx-email-check --url 'https://email-check.david-cyr.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dawaxwx-email-check:
    url: "https://email-check.david-cyr.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dawaxwx-email-check": {
      "Transport": "http",
      "Url": "https://email-check.david-cyr.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dawaxwx-email-check -t streamable-http -u 'https://email-check.david-cyr.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dawaxwx-email-check": {
      "type": "http",
      "url": "https://email-check.david-cyr.workers.dev/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-09-28 (score 70, 0)

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

### 2026-09-27 (score 70, +1)

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

### 2026-09-25 (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-23 (score 68, +1)

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

### 2026-09-22 (score 67, +49)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.80
- [functional improvement] MCP protocol: unverified → pass

### 2026-09-21 (score 18, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.73 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-18 (score 66, +1)

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

### 2026-09-16 (score 65, +1)

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

## MCP tools (1)

### `run` (~30 tokens)

Fast email validation at the edge: syntax, MX records, disposable-domain detection.

Input parameters:

- `input` (object, required)

## Diagnostics

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

## Score history

- 2026-09-28: 70
- 2026-09-27: 70
- 2026-09-26: 69
- 2026-09-25: 69
- 2026-09-24: 68
- 2026-09-23: 68
- 2026-09-22: 67
- 2026-09-21: 18
- 2026-09-20: 66
- 2026-09-19: 66
- 2026-09-18: 66
- 2026-09-17: 65
- 2026-09-16: 65
- 2026-09-15: 64
- 2026-09-14: 64
- 2026-09-13: 63
- 2026-09-12: 63
- 2026-09-11: 62
- 2026-09-10: 62
- 2026-09-09: 61
- 2026-09-08: 61
- 2026-09-07: 60
- 2026-09-06: 60
- 2026-09-05: 59
- 2026-09-04: 59
- 2026-09-03: 59
- 2026-09-02: 58
- 2026-09-01: 58
- 2026-08-31: 57
- 2026-08-30: 57

## Common questions

### What is the Email Check MCP server?

Email Check is an MCP server listed in the public MCP registry as io.github.Dawaxwx/email-check. Fast email validation at the edge: syntax, MX records, disposable-domain detection. This page covers its hosted endpoint (https://email-check.david-cyr.workers.dev/mcp).

### Is the Email Check MCP server safe to use?

Email Check scores 70 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 Check MCP server expose?

Email Check exposes 1 tool: run. Their descriptions and schemas cost roughly 30 tokens of context every time the server is loaded.

### Does the Email Check MCP server require authentication?

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

### Is the Email Check MCP server still maintained?

Email Check is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 27 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://email-check.david-cyr.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dawaxwx-email-check/email-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/dawaxwx-email-check/email-check.json
- HTML version of this page: https://verifymcp.io/servers/dawaxwx-email-check/email-check