mcpbeat Sign in

Blinkpdf MCP Server

answering

Blinkpdf is answering right now. Last checked 9 min ago.

Render Markdown and LLM output into accessible PDF/UA-1 PDFs. No headless Chromium.

Uptime history 91 days of history · worst day 96%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
336 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Blinkpdf every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add blinkpdf --transport http https://mcp.blinkpdf.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.blinkpdf.io/mcp
~/.codex/config.toml
[mcp_servers.blinkpdf]
url = "https://mcp.blinkpdf.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "blinkpdf": {
      "url": "https://mcp.blinkpdf.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "blinkpdf": {
      "type": "http",
      "url": "https://mcp.blinkpdf.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.blinkpdf.io/mcp streamable-http sign-in 233 ms 9 min ago

Alternatives to Blinkpdf

same job, measured the same way
Makespdf
by makespdf

Compliant PDFs (PDF/A-2A + PDF/UA-1) from markdown or a compact DSL - fast, no headless browser.

11 tools answering
Charlotte
by ticktockbent

Renders web pages into structured, agent-readable representations using headless Chromium.

348 installs/wk local only
PDFLoom
by pdfloom

HTML or URL to PDF with headless Chrome, and invoice/receipt/quote PDFs from JSON.

answering
Blueprint Chart
by blueprint-chart

The open chart format an LLM writes and the browser renders — to interactive, accessible SVG.

90 installs/wk local only
Unblink
by christopherdavenport

Pure-Go browser for AI: fetch pages, render JS without Chromium, return clean Markdown over MCP.

local only
pdfrender
by pdfrender

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

1 tools answering
A11yScope
by perceivable

WCAG 2.2 AA accessibility checks for pages and HTML, run locally in headless Chrome.

89 installs/wk local only
Shotlane
by shotlane

Screenshot web pages, read them as clean Markdown (JS rendered), and render HTML to PDF.

answering

Blinkpdf — questions

Answers built from our own checks of this server.

Why is there no tool list for Blinkpdf?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Blinkpdf working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 336 ms. The bar chart above shows every period we have measured.
How do I connect Blinkpdf?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Blinkpdf?
No API key is involved. Blinkpdf answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Blinkpdf?
It answers our handshake in 336 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.