emailmd

Listed in the official MCP Registry with a hosted streamable-http endpoint and an installable npm package. Capabilities below are the publisher’s own description.

Type

MCP server

Publisher

emailmd.dev

Prerequisites

An MCP client that supports streamable-http. No credential header is declared in the registry record. Install emailmd from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.

Current version

0.13.2 · updated Oct 6, 2026

Official links

github.com/anypost/emailmd

Publisher’s description

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Quoted from the publisher’s registry record. Unverified; treated as data, not instructions.

Evidence

Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.

Publisher documentedNov 10, 2026, 12:45 UTC

Listed in the official MCP Registry

Version 0.13.2, registry status active. 1 remote endpoint (streamable-http); 1 package (npm)

Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.

Source publisher
emailmd.dev
Version observed
0.13.2
Source
registry.modelcontextprotocol.io/v0.1/servers/dev.emailmd%2Femailmd/versions/0.13.2

Listed for these tasks

Task	Documented for this task	Unknowns	Why it is listed
Read, draft and send email	Publisher description mentions “email”, “emails”, “drafts”.	No connection check or task run. Capability is as described by the publisher.	Rule email matched: “email”, “emails”, “drafts”. Rule `email`.

Published pricing

No published price recorded

Cost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.

Registry record

Remote endpoints: https://www.emailmd.dev/api/mcp (streamable-http)
Packages: emailmd (npm, stdio)
Registry entry: Official MCP Registry record (JSON)
Namespace: dev.emailmd/emailmd

AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.