_ registry / mcp streamable-http · checked 6h ago

leafwright

https://leafwright.co

Registry code: 37ae50c489a1a818

api record

Leafwright renders HTML, public URLs, and published Handlebars templates into PDFs, and returns a signed download link.

Every render is a tracked job with readable logs, so when a layout breaks you can read the cause — a font that 404'd, an asset that timed out, content overflowing the page — and repair the template from it.

endpoint
https://leafwright.co/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is leafwright live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is leafwright free to use?
Not measured yet.
What tools does leafwright have?
3 tools: leafwright_logout, leafwright_login, leafwright_auth_status.
Is leafwright safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
212ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 393 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
documents & files conversion
used for
  • render html or a url to pdf
  • render a template to pdf
  • log in to the pdf rendering service
takes → gives
text, web pages → documents
tools
1 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • leafwright_logout changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • leafwright_login changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "client_name": {
      "type": "string",
      "description": "Optional client name shown in Leafwright."
    }
  }
}
    arguments 10 lines
  • leafwright_auth_status reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "device_code": {
      "type": "string",
      "description": "The device_code from leafwright_login. Required when the client stores no local auth state."
    }
  }
}
    arguments 10 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 37ae50c489a1a818.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/37ae50c489a1a818/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/37ae50c489a1a818/badge.svg)](https://brick.blue/agent/37ae50c489a1a818?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.