Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

pdfrender

REMOTE · API.PDFRENDER.DEV · SCANNED OCT 4

HTML and CSS to PDF MCP server with page headers, footers and page numbers. No headless browser.

+7 this week 89 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 208 tokens (~208/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
Install

How do I install the pdfrender MCP server?

pdfrender is a hosted endpoint at https://api.pdfrender.dev/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.pdfrender.dev

# add to Claude Code
claude mcp add --transport http dev-pdfrender-pdfrender 'https://api.pdfrender.dev/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-pdfrender-pdfrender": {
      "url": "https://api.pdfrender.dev/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-pdfrender-pdfrender": {
      "type": "http",
      "url": "https://api.pdfrender.dev/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-pdfrender-pdfrender]
url = "https://api.pdfrender.dev/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-pdfrender-pdfrender": {
      "type": "remote",
      "url": "https://api.pdfrender.dev/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-pdfrender-pdfrender --url 'https://api.pdfrender.dev/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-pdfrender-pdfrender:
    url: "https://api.pdfrender.dev/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-pdfrender-pdfrender": {
      "Transport": "http",
      "Url": "https://api.pdfrender.dev/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add dev-pdfrender-pdfrender -t streamable-http -u 'https://api.pdfrender.dev/mcp/'
// mcp.json
{
  "mcpServers": {
    "dev-pdfrender-pdfrender": {
      "type": "http",
      "url": "https://api.pdfrender.dev/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 3 Oct 26 +1
    • Stability: 0.97 → pass security
  • 2 Oct 26 −1
    • Tool “render_html_to_pdf” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Stability: pass → 0.97 functional
  • 1 Oct 26 +11
    • Transport: fail → pass ▲ security
    • Schema quality: 134 → 171 ▼ functional
    • “render_html_to_pdf” added an optional parameter “pdf_variant” cosmetic
  • 30 Sept 26 −10
    • Transport: pass → fail ▼ security
  • 28 Sept 26 +6
    • Authorization: unverified → partial ▲ security
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +3
    • Tool “render_html_to_pdf” rewrote its description, which is the text the model reads security
    • Tool coverage: 0% → 100% ▲ functional
    • Server version: 3.4.2 → 1 functional
    • “render_html_to_pdf” reworded the description of “html” cosmetic
    • Tool “render_html_to_pdf” changed its title: Render an HTML document to a PDF cosmetic
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • Tool “render_html_to_pdf” rewrote its description, which is the text the model reads security
Diagnostics

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 7 Oct 2026 · Probed https://api.pdfrender.dev/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.pdfrender.dev CN=YE2,O=Let's Encrypt,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA384 5cd6032666414bfae8801d66cc0b475891c
SANs: api.pdfrender.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
CN=ISRG Root X1,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 4 Jun 2015 4 Jun 2035 RSA 4096 SHA256-RSA 8210cfb0d240e3594463e0bb63828b00

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.pdfrender.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
pdfrender.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; connect-src 'self' https://api.pdfrender.dev; worker-src 'self' blob:; font-src 'self' data:; frame-ancestors 'none'; form-action 'self' https://polar.sh https://*.polar.sh https://sandbox.polar.sh; base-uri 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.pdfrender.dev/mcp/ Verified 200
http (plaintext) http://api.pdfrender.dev/mcp/ HTTPS enforced 301 https://api.pdfrender.dev/mcp/
MCP tools · 1 exposed · ~208 tokens

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 →

Tool Tokens
render_html_to_pdf ~208

Render up to 256 KB of HTML to a PDF. Returns a download link to the PDF. Give the user the `download_url` so they can open the PDF. The link works for 15 minutes; after that, render again. The result is `{"download_url": "<link>", "pages": <page count>, "size_bytes": <PDF size>, "expires_in_minutes": 15}`. Only HTML and CSS are rendered; JavaScript is not run. For documents larger than 256 KB, use the REST API (`POST /v1/render`). Credits: 1 per call.

NameTypeReqDescription
htmlstringyesA complete HTML document, up to 256 KB. Inline images, fonts and CSS as data: URIs; external resources are not loaded.
pdf_variant––Write the PDF as PDF/A-2b or PDF/A-3b, for archiving. Paid plans only. Leave it out for a regular PDF.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the pdfrender MCP server?

pdfrender is an MCP server listed in the public MCP registry as dev.pdfrender/pdfrender. HTML and CSS to PDF MCP server with page headers, footers and page numbers. No headless browser. This page covers its hosted endpoint (https://api.pdfrender.dev/mcp/).

Is the pdfrender MCP server safe to use?

pdfrender scores 89 out of 100 on VerifyMCP. 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 pdfrender MCP server expose?

pdfrender exposes 1 tool: render_html_to_pdf. Their descriptions and schemas cost roughly 208 tokens of context every time the server is loaded.

Does the pdfrender MCP server require authentication?

No. We connected to pdfrender without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the pdfrender MCP server still maintained?

pdfrender is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.