# HTML Email Playbook (remote · docs.osamahassouna.com)

Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 19 rules, 6 comps.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `docs.osamahassouna.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/osamahassouna-email-playbook-mcp/api-mcp.md), [page](https://verifymcp.io/servers/osamahassouna-email-playbook-mcp/api-mcp)
- npm · `email-playbook-mcp`: 68/100, [markdown](https://verifymcp.io/servers/osamahassouna-email-playbook-mcp/email-playbook-mcp.md), [page](https://verifymcp.io/servers/osamahassouna-email-playbook-mcp/email-playbook-mcp)

## Channel facts

- Endpoint: `https://docs.osamahassouna.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 321 tokens (~80/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http osamahassouna-email-playbook-mcp https://docs.osamahassouna.com/api/mcp
```

### Codex

```toml
[mcp_servers.osamahassouna-email-playbook-mcp]
url = "https://docs.osamahassouna.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "osamahassouna-email-playbook-mcp": {
      "type": "remote",
      "url": "https://docs.osamahassouna.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add osamahassouna-email-playbook-mcp --url https://docs.osamahassouna.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  osamahassouna-email-playbook-mcp:
    url: "https://docs.osamahassouna.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "osamahassouna-email-playbook-mcp": {
      "type": "http",
      "url": "https://docs.osamahassouna.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (4)

### `list_categories` (~99 tokens)

List all rule categories in the Email Playbook with a one-line description and page count. 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). For reusable components, use list_components instead — they live in a separate dimension and are not returned by get_playbook_rules.

### `get_playbook_rules` (~78 tokens)

Return the full rule pages for a given category. Each rule includes the title, description, markdown body explaining the rule, and any HTML/CSS code examples from the playbook. Use this to teach a model the exact patterns for a specific concern (e.g., responsive layout).

Input parameters:

- `category` (string, required): Which rule category to fetch.

### `list_components` (~60 tokens)

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.

### `get_component` (~84 tokens)

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.

Input parameters:

- `name` (string, required): Component name. Get the list from list_components first.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/osamahassouna-email-playbook-mcp/api-mcp#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://docs.osamahassouna.com/api/mcp
- Repository: https://github.com/OsamaHassouna/docs-hub
- Website: https://docs.osamahassouna.com/email-playbook/
- Changelog RSS feed: https://verifymcp.io/servers/osamahassouna-email-playbook-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/osamahassouna-email-playbook-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/osamahassouna-email-playbook-mcp/api-mcp