HTML Email Playbook
REMOTE · DOCS.OSAMAHASSOUNA.COM · 2 COMPONENTS
Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 21 rules, 6 comps.
Available components
Last scanned (21 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 686 tokens (~137/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Server version: 0.7.0 → 0.8.0 functional
- 17 Oct 26 +6
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_categories” rewrote its description, which is the text the model reads security
- Tool “get_playbook_rules” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 0.6.3 → 0.7.0 functional
- New tool “get_rule” functional
- “get_playbook_rules” added an optional parameter “format” cosmetic
- “get_playbook_rules” reworded the description of “category” cosmetic
- “get_playbook_rules” made “category” optional cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://docs.osamahassouna.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.osamahassouna.com | CN=YR2,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | RSA 2048 | SHA256-RSA | 5df7a0637e8959d0354e92b200aafc70f06 |
| SANs: *.osamahassouna.com, osamahassouna.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of docs.osamahassouna.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| osamahassouna.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docs.osamahassouna.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://docs.osamahassouna.com/api/mcp | HTTPS enforced | 308 | https://docs.osamahassouna.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_component ~84
Return the full record for a single component: title, description, narrative body, the primary HTML pattern, list of slots (placeholders the model should fill), VML/responsive flags, and all code examples. Use after list_components to fetch the actual HTML pattern to paste into an email.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Component name. Get the list from list_components first. |
No output schema declared.
No examples provided.
get_playbook_rules ~164
Return rule pages. format "checklist": each page as its slug, title, description and a short list of the rules to follow, without the body or code; leave out category to get every page in one call (about 16 KB). format "full" (default, needs a category): each page with title, description, checklist, markdown body and all HTML/CSS code examples. Start with the checklists, then fetch the pages you need with get_rule. Components are not included: use list_components / get_component.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Which rule category to fetch. Required for format "full"; optional for "checklist". |
| format | string | – | full (default): whole pages with code. checklist: titles and rules only. |
No output schema declared.
No examples provided.
get_rule ~149
Return one rule page: slug, category, title, description, checklist, and the markdown body, which includes the page's HTML/CSS code. Accepts the full slug (e.g. "compatibility/responsive"), just the page name ("responsive"), or a page link from a body ("/email-playbook/compatibility/responsive/"). Get the slugs from list_categories. Much smaller than fetching the whole category with get_playbook_rules.
| Name | Type | Req | Description |
|---|---|---|---|
| include_examples | boolean | – | Also return the code examples as a separate array (they are already in the body). Default false. |
| slug | string | yes | Page slug, e.g. "compatibility/responsive" or "responsive". |
No output schema declared.
No examples provided.
list_categories ~123
List all rule categories in the Email Playbook with a one-line description, page count, and the slug and title of each page in it. Categories are: structure (head/body container/header/body/footer), compatibility (Outlook MSO, RTL, responsive), production (Gmail clipping, dark mode, preheader, bulletproof buttons), ai-generation (constraints for AI emitters). Pass a page slug to get_rule to fetch just that page. For reusable components, use list_components instead — they live in a separate dimension and are not returned by get_playbook_rules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_components ~60
List all reusable email components in the playbook with their metadata: name, subcategory (layout/media/interactive/text), description, whether they require Outlook VML, and whether they are responsive. Use this first to discover what components exist before calling get_component.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the HTML Email Playbook MCP server?
HTML Email Playbook is a hosted endpoint at https://docs.osamahassouna.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · docs.osamahassouna.com
claude mcp add --transport http osamahassouna-email-playbook-mcp 'https://docs.osamahassouna.com/api/mcp'
What is the HTML Email Playbook MCP server?
HTML Email Playbook is an MCP server listed in the public MCP registry as io.github.OsamaHassouna/email-playbook-mcp. Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 21 rules, 6 comps. This page covers its hosted endpoint (https://docs.osamahassouna.com/api/mcp).
Is the HTML Email Playbook MCP server safe to use?
HTML Email Playbook scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HTML Email Playbook MCP server expose?
HTML Email Playbook exposes 5 tools: list_categories, get_playbook_rules, get_rule, list_components, get_component. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.
Does the HTML Email Playbook MCP server require authentication?
No. We connected to HTML Email Playbook without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HTML Email Playbook MCP server still maintained?
HTML Email Playbook is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.