emailmd
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-25.
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-25.
Is emailmd a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for emailmd (as of 2026-08-25).
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-25).
Does emailmd support MCP revision 2025-11-25?
Yes. emailmd supports MCP revision 2025-11-25 (checked 2026-08-25).
When were emailmd's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
Which tools does emailmd expose?
3 tools verified.
renderlintread_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 #65 in The MCP 500 with Adoption Index 58.59 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 4,148 | API · |
| GitHub stars | 1,373 | API · |
| GitHub forks | 41 | API · |
| Last push | 2026-08-26T19:42:32Z | API · |
| Repository archived | no | API · |
Repository and package signals for emailmd
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 1
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- None
Package (npm) as of
- Latest version
0.10.0- Last published
- First published
- Releases
- 26
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 15
- Unpacked size
- 482 KB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- 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
- 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
- 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
- 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
- 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