emailmd
REMOTE · WWW.EMAILMD.DEV · 2 COMPONENTS
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Available components
Last scanned (10 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 770 tokens (~256/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 7 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.11.1 → 0.13.2 functional
- 2 Oct 26 79
- Server version: 0.11.0 → 0.11.1 functional
- 28 Sept 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
- 25 Sept 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 Aug 26 0
- First check of Injection markers: pass security
- First check of Judged manipulation: pass security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 204 → 241 ▼ functional
- First check of Destructive annotations: pass functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 0.10.0 → 0.11.0 functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
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 5 Nov 2026 · Probed https://www.emailmd.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=www.emailmd.dev | CN=YR2,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | RSA 2048 | SHA256-RSA | 61f2c709785b9dc9f92d98e31802bebdba8 |
| SANs: www.emailmd.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.emailmd.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| emailmd.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.emailmd.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.emailmd.dev/api/mcp | HTTPS enforced | 308 | https://www.emailmd.dev/api/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lint Lint an email ~115
Check emailmd markdown for deliverability, accessibility, and readability problems without rendering it: missing alt text, http:// links, Gmail's 102KB clip limit, generic link text, spam-trigger phrases, and more. Fix warnings before sending; suggestions are sometimes intentional (e.g. transactional emails without an unsubscribe link).
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The emailmd markdown document, optionally starting with YAML frontmatter. |
| partials | object | – | Named markdown partials spliced in wherever the document says "::: include <name>". |
No output schema declared.
No examples provided.
read_docs Read emailmd docs ~95
Fetch emailmd documentation from emailmd.dev. Call with no arguments for the index of all pages; pass page to read one (e.g. 'buttons', 'frontmatter', 'theme', 'directives/hero'). Read the relevant page before using syntax you are not sure about.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | – | Docs page path, e.g. 'buttons' or 'directives/hero'. Omit for the index. |
No output schema declared.
No examples provided.
render Render an email ~143
Render emailmd markdown into email-safe HTML. Returns html (the complete email document), text (the plain-text MIME part), meta (frontmatter), warnings (non-fatal repairs made while rendering; aim for none), htmlBytes, and previewUrl (a live browser preview of this exact document to share with the user).
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The emailmd markdown document, optionally starting with YAML frontmatter. |
| minify | boolean | – | Minify the HTML. Recommended for sending; helps stay under Gmail's 102KB clip limit. |
| partials | object | – | Named markdown partials spliced in wherever the document says "::: include <name>". |
No output schema declared.
No examples provided.
How do I install the emailmd MCP server?
emailmd is a hosted endpoint at https://www.emailmd.dev/api/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.
remote · www.emailmd.dev
claude mcp add --transport http dev-emailmd-emailmd 'https://www.emailmd.dev/api/mcp'
What is the emailmd MCP server?
emailmd is an MCP server listed in the public MCP registry as dev.emailmd/emailmd. Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails. This page covers its hosted endpoint (https://www.emailmd.dev/api/mcp).
Is the emailmd MCP server safe to use?
emailmd scores 79 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 emailmd MCP server expose?
emailmd exposes 3 tools: render, lint, read_docs. Their descriptions and schemas cost roughly 353 tokens of context every time the server is loaded.
Does the emailmd MCP server require authentication?
No. We connected to emailmd without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the emailmd MCP server still maintained?
emailmd is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.