MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

emailmd

Earlier Revision Publisher unverified Confidence: Good (0.85)

emailmd is an MCP server published by emailmd.dev, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-14.

Does emailmd support the current MCP specification (2026-07-28)?

Not yet confirmed. emailmd is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-14.

Is emailmd a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for emailmd (as of 2026-08-14).

How do I connect to emailmd?

emailmd is available via a hosted remote endpoint at https://www.emailmd.dev/api/mcp, the package npm:emailmd, the official MCP Registry under dev.emailmd/emailmd, the source repository at https://github.com/anypost/emailmd. Authentication: none. Transports: sse-legacy.

What tools does emailmd expose?

emailmd exposes 3 tools, including render, lint, read_docs (last verified 2026-08-14).

Does emailmd support MCP revision 2025-11-25?

Yes. emailmd supports MCP revision 2025-11-25 (checked 2026-08-07).

When were emailmd's facts last verified?

2026-08-14. Each fact on this page links to the sources used to verify it.

Which tools does emailmd expose?

3 tools verified.

  • render
  • lint
  • read_docs

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

Which MCP spec revisions does emailmd support?

emailmd has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source

How widely adopted is emailmd?

Ranked #75 in The MCP 500 with Adoption Index 70.13 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
npm downloads (weekly) 3,512 API ·
GitHub stars 1,300 API ·
GitHub forks 38 API ·
Last push 2026-07-26T05:03:39Z API ·
Repository archived no API ·

How was this verified, and what are the sources?

Verified · method: endpoint-probe · confidence 0.85 (Good).

  1. Official MCP Registry record for dev.emailmd/emailmd at version 0.9.1 - lists remote endpoint https://www.emailmd.dev/api/mcp and repository https://github.com/anypost/emailmd - accessed
  2. Endpoint probe of https://www.emailmd.dev/api/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 3 tools - accessed
  3. Staleness re-verification via the GitHub API - repository anypost/emailmd active (pushed 2026-07-26, not archived), latest release v0.10.0 (2026-07-26); entity facts unchanged - accessed
  4. Endpoint re-probe - server/discover at 2026-07-28 again rejected with error -32000 "Unsupported protocol version: 2026-07-28 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"; legacy status unchanged - accessed