# pdfzen (remote · api.pdfzen.site) Render PDFs from 45 starter templates or raw HTML. Pay-per-render with USDC via x402. - Trust score: 56/100 (low) - Change this week: +2 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-03 ## Components - remote · `api.pdfzen.site`: 56/100 (this document), [markdown](https://verifymcp.io/servers/site-pdfzen-render/api.md), [page](https://verifymcp.io/servers/site-pdfzen-render/api) ## Channel facts - Endpoint: `https://api.pdfzen.site/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.0` ## 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-08-03. - **Endpoint Security**: 46/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 62/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 1076 tokens (~269/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 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. - **Capabilities**: 20/100 - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http site-pdfzen-render https://api.pdfzen.site/mcp ``` ### Codex ```toml [mcp_servers.site-pdfzen-render] url = "https://api.pdfzen.site/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "site-pdfzen-render": { "type": "remote", "url": "https://api.pdfzen.site/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add site-pdfzen-render --url https://api.pdfzen.site/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: site-pdfzen-render: url: "https://api.pdfzen.site/mcp" ``` ### Other ```json { "mcpServers": { "site-pdfzen-render": { "type": "http", "url": "https://api.pdfzen.site/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-08-03 (score 56, +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-08-01 (score 55, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-31 (score 54, −2) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 56, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-28 (score 55, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-27 (score 54, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 53) First indexed and scored. ## MCP tools (4) ### `list_starters` (~121 tokens) List pdfzen's 45 public starter templates — invoices, receipts, contracts, certificates, NDAs, letters, reports, resumes, boarding passes, menus, bank statements, lab reports, lease agreements, performance reviews, and more. Returns an array of { slug, name, description, icon, pageOptions, fonts, dataKeys }. Free, no payment, no auth required. Call this first to discover what fits the user request, then optionally call get_starter to see the expected data shape, then call render_template_to_pdf to produce the PDF. ### `get_starter` (~121 tokens) Fetch the full HTML body, CSS, sampleData, and pageOptions for one starter template by slug. Use this when you need to understand the exact shape of `data` the template expects before calling render_template_to_pdf, or when you want to fork a starter into custom HTML. Free, no payment, no auth required. Input parameters: - `slug` (string, required): The starter slug. Examples: "invoice", "receipt", "certificate", "contract", "nda", "boarding-pass", "menu". Call list_starters to discover all 45 slugs. ### `render_template_to_pdf` (~294 tokens) Prepare a paid PDF render from one of the 45 starter templates. Validates your template + data and returns the exact, ready-to-execute HTTP request to run against pdfzen's render endpoint — POST /v402/render/pdf (x402, $0.006 USDC on Base, no API key) or POST /v1/render/pdf (pdfzen API key, credit-billed). pdfzen renders are executed over HTTP, not streamed in-band over MCP; this tool is the bridge. Your `data` is merged ON TOP of the starter sampleData at render time, so partial payloads inherit demo defaults (e.g. ship just the customer name + total). Input parameters: - `data` (object): Handlebars context. Each starter expects a specific shape — call get_starter to see the sampleData and dataKeys for the chosen slug. Your fields merge ON TOP of sampleData, so you can supply only the… - `pageOptions` (object): Page format/margin/orientation overrides. Defaults come from the starter (most are A4 portrait). Example: { "format": "Letter", "landscape": true }. - `template` (string, required): Slug of the starter to render (e.g. "invoice", "receipt", "certificate"). Call list_starters first if unsure which fits the user request. ### `render_html_to_pdf` (~287 tokens) Prepare a paid PDF render from arbitrary Handlebars-flavoured HTML. Use only when no starter fits (one-off layouts, custom branding). Prefer render_template_to_pdf when a starter matches. Validates your HTML and returns the exact, ready-to-execute HTTP request to run against pdfzen's render endpoint — POST /v402/render/pdf (x402, $0.006 USDC on Base, no API key) or POST /v1/render/pdf (pdfzen API key). pdfzen renders are executed over HTTP, not streamed in-band over MCP; this tool is the bridge. Input parameters: - `css` (string): Optional CSS injected into the document head. Alternative to inline