co.leafwright/leafwright
NPM · @LEAFWRIGHT/MCP · 2 COMPONENTS · SCANNED SEP 21
Render HTML, URLs, and templates to PDF. AI drafts templates and fixes them from logs.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 102 tokens (~34/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · @leafwright/mcp
claude mcp add co-leafwright-leafwright -- npx -y @leafwright/mcp
{
"mcpServers": {
"co-leafwright-leafwright": {
"command": "npx",
"args": [
"-y",
"@leafwright/mcp"
]
}
}
} {
"servers": {
"co-leafwright-leafwright": {
"command": "npx",
"args": [
"-y",
"@leafwright/mcp"
]
}
}
} codex mcp add co-leafwright-leafwright -- npx -y @leafwright/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-leafwright-leafwright": {
"type": "local",
"command": [
"npx",
"-y",
"@leafwright/mcp"
],
"enabled": true
}
}
} openclaw mcp add co-leafwright-leafwright --command npx --arg -y --arg @leafwright/mcp
mcp_servers:
co-leafwright-leafwright:
command: "npx"
args: ["-y", "@leafwright/mcp"] {
"McpServers": {
"co-leafwright-leafwright": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@leafwright/mcp"
]
}
}
} assistant mcp add co-leafwright-leafwright -t stdio -c npx -a -y @leafwright/mcp
{
"mcpServers": {
"co-leafwright-leafwright": {
"command": "npx",
"args": [
"-y",
"@leafwright/mcp"
]
}
}
} 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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 8 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 29 → 34 ▼ functional
- First check of Tool coverage: 100 functional
- Package version: 0.2.2 → 0.2.4 functional
- 7 Sept 26 +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.
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 21 Sept 2026 · Analysed npm/@leafwright/mcp@0.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
leafwright_auth_status Leafwright auth status ~27
Check whether Leafwright MCP is authenticated. Completes a pending browser login if approved.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| active_project_id | string|null | – | – |
| expires_at | string | – | – |
| next_step | string | – | – |
| status | string | yes | – |
| token | object | – | – |
| token_source | string|null | – | – |
| user_code | string | – | – |
No examples provided.
leafwright_login Log in to Leafwright ~52
Start a browser login flow for Leafwright MCP. Open the returned URL, choose an organization and project, then call leafwright_auth_status.
| Name | Type | Req | Description |
|---|---|---|---|
| client_name | string | – | Optional client name shown in Leafwright. |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at | string | yes | – |
| next_step | string | yes | – |
| status | string | yes | – |
| user_code | string | yes | – |
| verification_url | string | yes | – |
No examples provided.
leafwright_logout Log out of Leafwright ~23
Revoke the stored Leafwright MCP token and clear local auth state.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
No examples provided.
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.