MCP.Market

url-to-pdf MCP server

online · 100% uptime
by strayly·io.github.strayly/url-to-pdf·v0.2.1

Convert public web pages to PDF, images, Markdown, or JSON using one API key.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed url-to-pdf yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

url-to-pdf tools (5)

write = sends, deletes, buys or posts
  • list_capabilitiesFree

    Free. Returns what this server can do, the price of each paid tool, and where to buy an API key.

  • url_to_extractFree

    Extract structured data from a page as JSON: title, meta description, canonical URL, language, main text and links. Readability-first, no LLM involved. Requires an API key purchased at https://url-pdf.hammbox.com/buy. Same auth as the other paid tools.

  • url_to_markdownFree

    Extract page content as clean Markdown. Requires an API key purchased at https://url-pdf.hammbox.com/buy. If this MCP request carries a valid "x-api-key" or "Authorization: Bearer" header, it renders directly and returns a 1-hour download URL; otherwise it returns purchase guidance.

  • url_to_pdfFree

    Render a web page to PDF. Requires an API key purchased at https://url-pdf.hammbox.com/buy. If this MCP request carries a valid "x-api-key" or "Authorization: Bearer" header, it renders directly and returns a 1-hour download URL; otherwise it returns purchase guidance.

  • url_to_screenshotFree

    Capture a page as an image. Requires an API key purchased at https://url-pdf.hammbox.com/buy. If this MCP request carries a valid "x-api-key" or "Authorization: Bearer" header, it renders directly and returns a 1-hour download URL; otherwise it returns purchase guidance.

Public scan report

scanner v0.1.10 · 2026-10-09 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 414ms20/20
  • Tool poisoning5 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How url-to-pdf compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
105 ms
faster than 83% of 30,031 servers

What its tools let an agent do: 5 read

Install url-to-pdf in Claude Code, Cursor or VS Code

claude mcp add --transport http url-to-pdf https://url-pdf.hammbox.com/mcp
Add to Cursor

What the publisher says

From the url-to-pdf repository's README, as published. We do not edit it. Read it on GitHub

url-to-pdf

Turn any public web page into a PDF, a full-page screenshot, or clean Markdown — with one API key.

No browser farm to run, no headless Chrome to babysit. url-to-pdf renders pages on Cloudflare's infrastructure and hands you a download link. Use it from any MCP-compatible AI client (Claude Desktop, Cursor, and friends) by just talking, or call the HTTP API directly from your scripts.

Why you'll like it

  • Four outputs, one key. PDF (A4 / Letter / Legal, portrait or landscape), full-page PNG/JPEG screenshots, clean Markdown (navigation stripped out), and structured JSON (title, description, canonical URL, language, main text, links).
  • Your assistant actually sees the result. Small outputs (≤1 MB) are returned inline — screenshots come back as images the model can look at, not just a link it has to read out loud.
  • Every render comes with a receipt. Final URL after redirects, HTTP status, capture time, duration, byte size and a SHA-256 of the artifact, so a result can be quoted and verified later.
  • Just talk to it. Connect it as an MCP server and say "turn https://example.com into a PDF" — your client does the rest. No curl, no JSON to hand-write.
  • Also a plain HTTP API. Every tool is a single POST with your x-api-key. Great for scripts, backends, and low-code platforms.
  • Mobile, retina and dark mode. Set any viewport (320–3840 × 240–2160), device pixel ratio up to 3, and render with prefers-color-scheme: dark.
  • SSRF-protected. Only public http(s) URLs are accepted; internal and reserved addresses are rejected at the edge.
  • Private by design. Outputs are kept for 1 hour then auto-deleted. We never see your card (Paddle handles payments) and your email is used only to recover your key.

Get your API key

  1. Go to url-pdf.hammbox.com/buy and complete checkout (Paddle — major credit cards).
  2. Your key appears on screen the moment payment completes. Copy it and keep it safe.
  3. Lost it? Recover it anytime at /portal/claim with the email you used at checkout. No password, no support ticket.

Use it as an MCP server (recommended for AI clients)

Add url-to-pdf to your client's MCP configuration. With Claude Desktop, Cursor, or any client that supports Streamable HTTP:

{
  "mcpServers": {
    "url-to-pdf": {
      "type": "http",
      "url": "https://url-pdf.hammbox.com/mcp",
      "headers": { "x-api-key": "YOUR_API_KEY" }
    }
  }
}

That's it — no local install. Then just ask your assistant in natural language:

"Convert https://news.ycombinator.com to a PDF and give me the download link."

The client calls the tool, passes your key, and shows you the result.

Use it as an HTTP API (for scripts & backends)

Every render is a POST to a /tools/* endpoint with your key in the header.

# Web page → PDF
curl -X POST https://url-pdf.hammbox.com/tools/url-to-pdf \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{"url":"https://example.com","format":"A4"}'

# Full-page screenshot
curl -X POST https://url-pdf.hammbox.com/tools/url-to-screenshot \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{"url":"https://example.com","fullPage":true,"format":"png"}'

# Extract Markdown
curl -X POST https://url-pdf.hammbox.com/tools/url-to-markdown \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{"url":"https://example.com"}'

# Structured data as JSON
curl -X POST https://url-pdf.hammbox.com/tools/url-to-extract \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{"url":"https://example.com","maxLinks":50}'

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

url-to-pdf: common questions

Is url-to-pdf MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the url-to-pdf safety report
How do I install url-to-pdf?
It runs remotely at url-pdf.hammbox.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does url-to-pdf need an API key?
Yes. The registry entry asks for x-api-key.
Is url-to-pdf maintained?
The last commit was 26 days ago (2026-10-09). The latest release is v0.2.1.
Is url-to-pdf up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of url-to-pdf?
Servers from other publishers that do the same job: kordoc MCP server and Front-End Checklist MCP server.
How does url-to-pdf compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to url-to-pdf

Same job from other publishers: the closest match first, then the best rated.

  • kordoc
    Parse Korean documents (HWP, HWPX, PDF, XLSX, DOCX, PPTX) to Markdown; fill forms, diff, render.
    A
  • Front-End Checklist
    Review frontend code and live pages against 386 quality-gated web development rules.
    A