leafwright MCP server
co.leafwright/leafwrightleafwright.costreamable-httpv0.2.4Scanned
Render HTML, URLs, and templates to PDF. AI drafts templates and fixes them from logs.
3 tools: 1 can delete or cancel things and 2 change things.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the leafwright MCP server can do
The leafwright MCP server is published by leafwright.co, a domain the MCP Registry verified. It has 3 tools. It can delete or cancel things (1 tool: leafwright_logout) and create or change data (2 tools: leafwright_login and leafwright_auth_status). None of its tools only reads.
3 tools bring in text other people can write (leafwright_login, leafwright_auth_status and leafwright_logout).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.2.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Deletes or cancels 1Claude Code: deny
leafwright_logoutRevoke the stored Leafwright MCP token and clear local auth state.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "revoke": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Revoke the stored Leafwright MCP token and clear local auth state.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 2Claude Code: ask
leafwright_auth_statusCheck whether Leafwright MCP is authenticated.Reads text others write1 finding
Why it is in this group
- The name "leafwright_auth_status" says "status": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "leafwright_auth_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The name "leafwright_auth_status" says "status": a word for reading.
Description, as the server wrote it Check whether Leafwright MCP is authenticated. Completes a pending browser login if approved. Pass the device_code returned by leafwright_login when the client has no local storage, which is the case over HTTP.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
leafwright_loginStart a browser login flow for Leafwright MCP.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Start a browser login flow for Leafwright MCP. Open the returned URL, choose an organization and project, then call leafwright_auth_status.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://leafwright.co/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://leafwright.co
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://leafwright.co/mcp: tools/list returned 3 tools to an anonymous client, including leafwright_logout (destructive), leafwright_login (write), leafwright_auth_status (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "leafwright_auth_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The name "leafwright_auth_status" says "status": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http leafwright https://leafwright.co/mcpclaude mcp add --transport http leafwright https://leafwright.co/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__leafwright__leafwright_login",
"mcp__leafwright__leafwright_auth_status"
],
"deny": [
"mcp__leafwright__leafwright_logout"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as leafwright. Review it before you use it.
Capability tags behind 3 rules
- mcp__leafwright__leafwright_login untrusted-input
- mcp__leafwright__leafwright_auth_status untrusted-input
- mcp__leafwright__leafwright_logout untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/co.leafwright/leafwright/verify?hash=d58975f23ecb6b17f2ccbda4b6a017bffc9a713be31f24131c3dc3082073418a" | jq -e '.changed == false'Pinned hash d58975f23ecb, from Nov 10, 2026, 09:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/co.leafwright/leafwright/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/co.leafwright/leafwright)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:47 UTC.
leafwright MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the leafwright MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the leafwright MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: leafwright_logout.
Can the leafwright MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the leafwright MCP server have?
- 3 tools: 1 destructive, 2 write. leafwright_logout, leafwright_login and leafwright_auth_status.
Does the leafwright MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the leafwright MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the leafwright MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.