# Emailens MCP (remote · emailens.dev)

Email compatibility analysis across 15 clients — preview, audit, fix, diff, deliverability.

- Trust score: 77/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `emailens.dev`: 77/100 (this document), [markdown](https://verifymcp.io/servers/emailens-mcp/api-mcp.md), [page](https://verifymcp.io/servers/emailens-mcp/api-mcp)
- npm · `@emailens/mcp`: 35/100, [markdown](https://verifymcp.io/servers/emailens-mcp/emailens-mcp.md), [page](https://verifymcp.io/servers/emailens-mcp/emailens-mcp)

## Channel facts

- Endpoint: `https://emailens.dev/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.1`

## 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-08-03.

- **Endpoint Security**: 80/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 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**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 647 tokens (~71/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http emailens-mcp https://emailens.dev/api/mcp
```

### Codex

```toml
[mcp_servers.emailens-mcp]
url = "https://emailens.dev/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "emailens-mcp": {
      "type": "remote",
      "url": "https://emailens.dev/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add emailens-mcp --url https://emailens.dev/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  emailens-mcp:
    url: "https://emailens.dev/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "emailens-mcp": {
      "type": "http",
      "url": "https://emailens.dev/api/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-08-02 (score 77, +1)

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

### 2026-07-31 (score 76, +4)

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

### 2026-07-30 (score 72, 0)

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

### 2026-07-29 (score 72, +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-07-28 (score 71, +1)

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

### 2026-07-27 (score 70, 0)

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

### 2026-07-26 (score 70)

First indexed and scored.

## MCP tools (9)

### `preview_email` (~89 tokens)

Preview Email

Full email compatibility preview , transforms HTML for 21 email clients, analyzes CSS, generates scores, simulates dark mode, checks inbox preview and email size.

Input parameters:

- `clients` (array): Optional client ID filter
- `format` (string): Input format: 'html' (default), 'jsx', 'mjml', or 'maizzle'
- `html` (string, required): The email HTML source code

### `analyze_email` (~46 tokens)

Analyze Email

Quick CSS compatibility analysis , returns warnings and per-client scores.

Input parameters:

- `format` (string): Input format for framework-specific fix snippets
- `html` (string, required): The email HTML source code

### `audit_email` (~67 tokens)

Audit Email

Comprehensive quality audit , CSS compatibility, spam, links, accessibility, images, inbox preview, size, templates, content overflow, visual bugs.

Input parameters:

- `format` (string): Input format
- `html` (string, required): The email HTML source code
- `skip` (array): Checks to skip

### `fix_email` (~68 tokens)

Fix Email

Generate a structured fix prompt for email compatibility issues.

Input parameters:

- `format` (string): Input format , controls fix syntax
- `html` (string, required): The email HTML source code to fix
- `scope` (string): Fix scope
- `selectedClientId` (string): Client ID for scoped fixes

### `list_clients` (~49 tokens)

List Email Clients

List all 21 supported email clients with IDs, names, rendering engines, dark mode support, and deprecation status. Use the returned IDs to filter other tools like preview_email or capture_screenshots.

### `diff_emails` (~57 tokens)

Diff Emails

Compare two email HTML versions , shows score changes, fixed issues, and regressions per client.

Input parameters:

- `after` (string, required): Modified email HTML
- `before` (string, required): Original email HTML
- `format` (string): Input format

### `check_deliverability` (~48 tokens)

Check Deliverability

Check email deliverability for a domain , SPF, DKIM, DMARC, MX, BIMI.

Input parameters:

- `domain` (string, required): Domain to check (e.g. 'company.com')

### `build_email` (~173 tokens)

Build Email

Generate a cross-client-compatible email from a brief using Emailens's self-healing loop (generate → score across 21 clients → repair). Output stays in the framework you choose. Returns a runId immediately , poll get_build_status for progress and the final code. Requires a Pro/Team API key.

Input parameters:

- `format` (string): Output framework: 'html' (default), 'jsx', 'mjml', or 'maizzle'
- `intent` (string, required): What the email should be and contain , the brief to build from
- `maxIterations` (number): Max repair rounds, 1-8 (default 5)
- `seedHtml` (string): Optional existing code to improve from instead of starting blank
- `threshold` (number): Target compatibility score, 50-100 (default 90)

### `get_build_status` (~50 tokens)

Get Build Status

Check a build_email run by runId , returns status, iteration, best compatibility score, and the current best source once available.

Input parameters:

- `runId` (string, required): The runId returned by build_email

## Diagnostics

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

## Score history

- 2026-08-03: 77
- 2026-08-02: 77
- 2026-08-01: 76
- 2026-07-31: 76
- 2026-07-30: 72
- 2026-07-29: 72
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 70

## Links

- Remote endpoint: https://emailens.dev/api/mcp
- Repository: https://github.com/emailens/mcp
- Website: https://emailens.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/emailens-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/emailens-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/emailens-mcp/api-mcp