Emailens MCP

REMOTE · EMAILENS.DEV · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · emailens.dev 77 npm · @emailens/mcp 35

+7 this week 77 77 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security80

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability82

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 647 tokens (~71/item across 9 items; 9 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · emailens.dev

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 +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.
31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +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.
28 Jul 26 +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.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 70

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://emailens.dev/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=emailens.dev	CN=YE1,O=Let's Encrypt,C=US	23 Jun 2026	21 Sept 2026	ECDSA 256	ECDSA-SHA384	58e806f41388742ffa5bb74d28eec2b7fbd
SANs: *.emailens.dev, emailens.dev
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of emailens.dev. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
dev.	present	60074	8	Verified
emailens.dev.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=63072000
content-security-policy	default-src 'self'; script-src 'self' 'unsafe-inline' https://openpanel.dev; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https:; media-src 'self' https://cdn.emailens.dev; font-src 'self' data: https://fonts.gstatic.com; frame-src 'self'; connect-src 'self' https://api-openpanel.philippekam.dev https://ebwqcitgedxwwrswebew.supabase.co wss://ebwqcitgedxwwrswebew.supabase.co; object-src 'none'; base-uri 'self'
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	strict-origin-when-cross-origin

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://emailens.dev/api/mcp	Verified	200
http (plaintext)	http://emailens.dev/api/mcp	HTTPS enforced	308	https://emailens.dev/api/mcp

MCP tools — 9 exposed · ~647 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

analyze_email Analyze Email ~46

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

Input Output Examples

Name	Type	Req	Description
format	string	—	Input format for framework-specific fix snippets
html	string	yes	The email HTML source code

No output schema declared.

No examples provided.

audit_email Audit Email ~67

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

Input Output Examples

Name	Type	Req	Description
format	string	—	Input format
html	string	yes	The email HTML source code
skip	array	—	Checks to skip

No output schema declared.

No examples provided.

build_email Build Email ~173

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 Output Examples

Name	Type	Req	Description
format	string	—	Output framework: 'html' (default), 'jsx', 'mjml', or 'maizzle'
intent	string	yes	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)

No output schema declared.

No examples provided.

check_deliverability Check Deliverability ~48

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

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain to check (e.g. 'company.com')

No output schema declared.

No examples provided.

diff_emails Diff Emails ~57

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

Input Output Examples

Name	Type	Req	Description
after	string	yes	Modified email HTML
before	string	yes	Original email HTML
format	string	—	Input format

No output schema declared.

No examples provided.

fix_email Fix Email ~68

Generate a structured fix prompt for email compatibility issues.

Input Output Examples

Name	Type	Req	Description
format	string	—	Input format , controls fix syntax
html	string	yes	The email HTML source code to fix
scope	string	—	Fix scope
selectedClientId	string	—	Client ID for scoped fixes

No output schema declared.

No examples provided.

get_build_status Get Build Status ~50

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

Input Output Examples

Name	Type	Req	Description
runId	string	yes	The runId returned by build_email

No output schema declared.

No examples provided.

list_clients List Email Clients ~49

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.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preview_email Preview Email ~89

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

Input Output Examples

Name	Type	Req	Description
clients	array	—	Optional client ID filter
format	string	—	Input format: 'html' (default), 'jsx', 'mjml', or 'maizzle'
html	string	yes	The email HTML source code

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	70
27 Jul	70
28 Jul	71
29 Jul	72
30 Jul	72
31 Jul	76
1 Aug	76
2 Aug	77
3 Aug	77