# emailmd (remote · www.emailmd.dev)

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

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

## Components

- remote · `www.emailmd.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/dev-emailmd-emailmd/api-mcp.md), [page](https://verifymcp.io/servers/dev-emailmd-emailmd/api-mcp)
- npm · `emailmd`: 45/100, [markdown](https://verifymcp.io/servers/dev-emailmd-emailmd/emailmd.md), [page](https://verifymcp.io/servers/dev-emailmd-emailmd/emailmd)

## Channel facts

- Endpoint: `https://www.emailmd.dev/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.9.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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 613 tokens (~204/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - 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 dev-emailmd-emailmd https://www.emailmd.dev/api/mcp
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "dev-emailmd-emailmd": {
      "type": "http",
      "url": "https://www.emailmd.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-03 (score 68, +1)

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

### 2026-08-01 (score 67, +1)

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

### 2026-07-31 (score 66, +1)

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

### 2026-07-30 (score 65, 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 65, +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 64, +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 63, 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 63)

First indexed and scored.

## MCP tools (3)

### `render` (~143 tokens)

Render an email

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).

Input parameters:

- `markdown` (string, required): 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>".

### `lint` (~115 tokens)

Lint an email

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).

Input parameters:

- `markdown` (string, required): The emailmd markdown document, optionally starting with YAML frontmatter.
- `partials` (object): Named markdown partials spliced in wherever the document says "::: include <name>".

### `read_docs` (~95 tokens)

Read emailmd docs

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.

Input parameters:

- `page` (string): Docs page path, e.g. 'buttons' or 'directives/hero'. Omit for the index.

## Diagnostics

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

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 65
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 63

## Links

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