mcp-registry/dev.emailmd/emailmd · v0.13.2
Also listed as awesome/anypost/emailmd, glama/anypost/emailmd
As of 2026-10-26 18:07 UTC, the Emailmd MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Point your MCP client at this streamable-http endpoint: https://www.emailmd.dev/api/mcp
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.emailmd%2Femailmd/fixes
{
"name": "lint",
"description": "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).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"markdown"
],
"properties": {
"markdown": {
"type": "string",
"maxLength": 262144,
"description": "The emailmd markdown document, optionally starting with YAML frontmatter."
},
"partials": {
"type": "object",
"description": "Named markdown partials spliced in wherever the document says \"::: include <name>\".",
"propertyNames": {
"type": "string",
"maxLength": 200
},
"additionalProperties": {
"type": "string",
"maxLength": 262144
}
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Lint an email"
}{
"name": "read_docs",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"page": {
"type": "string",
"pattern": "^[a-z0-9][a-z0-9/-]*$",
"maxLength": 200,
"description": "Docs page path, e.g. 'buttons' or 'directives/hero'. Omit for the index."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Read emailmd docs"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.emailmd/emailmd"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.emailmd/emailmd"}) over MCP.
render ~270 tokenslint ~243 tokensread_docs ~152 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.emailmd%2Femailmd?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.emailmd%2Femailmd?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.emailmd%2Femailmd.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.emailmd%2Femailmd.svg :target: https://glimind.com/server/mcp-registry%2Fdev.emailmd%2Femailmd?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d2d6ee202111b87f…, first seen 2026-10-17, included at leaf 11510 of 74,602. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:07 UTC, the Emailmd MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Emailmd MCP server advertises 3 tools, including lint, read_docs, render.
Point your MCP client at this streamable-http endpoint: https://www.emailmd.dev/api/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.