# co.leafwright/leafwright (remote · leafwright.co)

Render HTML, URLs, and templates to PDF. AI drafts templates and fixes them from logs.

- Trust score: 89/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `leafwright.co`: 89/100 (this document), [markdown](https://verifymcp.io/servers/co-leafwright-leafwright/leafwright.md), [page](https://verifymcp.io/servers/co-leafwright-leafwright/leafwright)
- npm · `@leafwright/mcp`: 79/100, [markdown](https://verifymcp.io/servers/co-leafwright-leafwright/leafwright-mcp.md), [page](https://verifymcp.io/servers/co-leafwright-leafwright/leafwright-mcp)

## Channel facts

- Endpoint: `https://leafwright.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.4`

## 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-09-20.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 102 tokens (~34/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the co.leafwright/leafwright MCP server?

co.leafwright/leafwright is a hosted endpoint at https://leafwright.co/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.

### Claude

```bash
claude mcp add --transport http co-leafwright-leafwright 'https://leafwright.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-leafwright-leafwright": {
      "url": "https://leafwright.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-leafwright-leafwright": {
      "type": "http",
      "url": "https://leafwright.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-leafwright-leafwright]
url = "https://leafwright.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-leafwright-leafwright": {
      "type": "remote",
      "url": "https://leafwright.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-leafwright-leafwright --url 'https://leafwright.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-leafwright-leafwright:
    url: "https://leafwright.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-leafwright-leafwright": {
      "Transport": "http",
      "Url": "https://leafwright.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-leafwright-leafwright -t streamable-http -u 'https://leafwright.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-leafwright-leafwright": {
      "type": "http",
      "url": "https://leafwright.co/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-09-18 (score 89, +1)

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

### 2026-09-16 (score 88, +1)

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

### 2026-09-14 (score 87, +1)

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

### 2026-09-12 (score 86, +1)

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

### 2026-09-10 (score 85, +1)

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

### 2026-09-08 (score 84, +1)

- [security] Tool “leafwright_logout” is now declared destructive
- [functional] Server version: 0.2.3 → 0.2.4

### 2026-09-06 (score 83, +1)

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

### 2026-09-03 (score 82, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `leafwright_login` (~52 tokens)

Log in to Leafwright

Start a browser login flow for Leafwright MCP. Open the returned URL, choose an organization and project, then call leafwright_auth_status.

Input parameters:

- `client_name` (string): Optional client name shown in Leafwright.

Output parameters:

- `expires_at` (string)
- `next_step` (string)
- `status` (string)
- `user_code` (string)
- `verification_url` (string)

### `leafwright_auth_status` (~27 tokens)

Leafwright auth status

Check whether Leafwright MCP is authenticated. Completes a pending browser login if approved.

Output parameters:

- `active_project_id`
- `expires_at` (string)
- `next_step` (string)
- `status` (string)
- `token` (object)
- `token_source`
- `user_code` (string)

### `leafwright_logout` (~23 tokens)

Log out of Leafwright

Revoke the stored Leafwright MCP token and clear local auth state.

Output parameters:

- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-leafwright-leafwright/leafwright#diagnostics

## Score history

- 2026-09-20: 89
- 2026-09-19: 89
- 2026-09-18: 89
- 2026-09-17: 88
- 2026-09-16: 88
- 2026-09-15: 87
- 2026-09-14: 87
- 2026-09-13: 86
- 2026-09-12: 86
- 2026-09-11: 85
- 2026-09-10: 85
- 2026-09-09: 84
- 2026-09-08: 84
- 2026-09-07: 83
- 2026-09-06: 83
- 2026-09-05: 82
- 2026-09-04: 82
- 2026-09-03: 82
- 2026-09-02: 81
- 2026-09-01: 38
- 2026-08-31: 38
- 2026-08-30: 38
- 2026-08-29: 38
- 2026-08-28: 38
- 2026-08-27: 38
- 2026-08-26: 38
- 2026-08-25: 38

## Common questions

### What is the co.leafwright/leafwright MCP server?

co.leafwright/leafwright is an MCP server listed in the public MCP registry as co.leafwright/leafwright. Render HTML, URLs, and templates to PDF. AI drafts templates and fixes them from logs. This page covers its hosted endpoint (https://leafwright.co/mcp).

### Is the co.leafwright/leafwright MCP server safe to use?

co.leafwright/leafwright scores 89 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 co.leafwright/leafwright MCP server expose?

co.leafwright/leafwright exposes 3 tools: leafwright_login, leafwright_auth_status, leafwright_logout. Their descriptions and schemas cost roughly 102 tokens of context every time the server is loaded.

### Does the co.leafwright/leafwright MCP server require authentication?

Yes. co.leafwright/leafwright asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the co.leafwright/leafwright MCP server still maintained?

co.leafwright/leafwright is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://leafwright.co/mcp
- Website: https://leafwright.co/
- Changelog RSS feed: https://verifymcp.io/servers/co-leafwright-leafwright/leafwright.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-leafwright-leafwright/leafwright.json
- HTML version of this page: https://verifymcp.io/servers/co-leafwright-leafwright/leafwright