# co.leafwright/leafwright (npm · @leafwright/mcp)

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

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@leafwright/mcp`
- Version: `0.2.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **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**: 90/100
  - Stability observed for 27 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 runs locally as an npm package, launched with npx -y @leafwright/mcp. 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 co-leafwright-leafwright -- npx -y @leafwright/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "co-leafwright-leafwright": {
      "command": "npx",
      "args": [
        "-y",
        "@leafwright/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-leafwright-leafwright": {
      "command": "npx",
      "args": [
        "-y",
        "@leafwright/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add co-leafwright-leafwright -- npx -y @leafwright/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-leafwright-leafwright": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@leafwright/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-leafwright-leafwright --command npx --arg -y --arg @leafwright/mcp
```

### Hermes

```yaml
mcp_servers:
  co-leafwright-leafwright:
    command: "npx"
    args: ["-y", "@leafwright/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "co-leafwright-leafwright": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@leafwright/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-leafwright-leafwright -t stdio -c npx -a -y @leafwright/mcp
```

### Other

```json
{
  "mcpServers": {
    "co-leafwright-leafwright": {
      "command": "npx",
      "args": [
        "-y",
        "@leafwright/mcp"
      ]
    }
  }
}
```

## 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-20 (score 79, +1)

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

### 2026-09-18 (score 78, +1)

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

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

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

### 2026-09-13 (score 76, +1)

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

### 2026-09-11 (score 75, +1)

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

### 2026-09-09 (score 74, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-08 (score 58, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 29 → 34
- [functional] First check of Tool coverage: 100
- [functional] Package version: 0.2.2 → 0.2.4

### 2026-09-07 (score 73, +1)

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

## 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` (string|null)
- `expires_at` (string)
- `next_step` (string)
- `status` (string)
- `token` (object)
- `token_source` (string|null)
- `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: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/co-leafwright-leafwright/leafwright-mcp#diagnostics

## Score history

- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 76
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 58
- 2026-09-07: 73
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 71
- 2026-09-03: 71
- 2026-09-02: 67
- 2026-09-01: 67
- 2026-08-31: 67
- 2026-08-30: 67
- 2026-08-29: 67
- 2026-08-28: 67
- 2026-08-27: 67
- 2026-08-26: 67
- 2026-08-25: 65

## 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 npm package (@leafwright/mcp).

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

co.leafwright/leafwright scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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.

### 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

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

co.leafwright/leafwright declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@leafwright/mcp
- Socket report: https://socket.dev/npm/package/@leafwright/mcp
- Website: https://leafwright.co/
- Changelog RSS feed: https://verifymcp.io/servers/co-leafwright-leafwright/leafwright-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-leafwright-leafwright/leafwright-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-leafwright-leafwright/leafwright-mcp