Remote MCP · Endpoint
pdfzen MCP server
No. pdfzen answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.pdfzen.site/mcp
The last check completed an MCP handshake.
- Registry name
- site.pdfzen/render
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 369 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Render PDFs from 45 starter templates or raw HTML. Pay-per-render with USDC via x402.
- Website
- https://pdfzen.site/
- Repository
- https://github.com/yalamber/pdfzen
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 369 ms |
| 1 day ago | Handshake completed | 161 ms |
| 2 days ago | Handshake completed | 162 ms |
| 3 days ago | Handshake completed | 283 ms |
| 4 days ago | Handshake completed | 206 ms |
| 5 days ago | Handshake completed | 363 ms |
| 6 days ago | Handshake completed | 578 ms |
| 8 days ago | Handshake completed | 399 ms |
| 11 days ago | Handshake completed | 226 ms |
| 13 days ago | Handshake completed | 190 ms |
| 15 days ago | Handshake completed | 449 ms |
| 18 days ago | Handshake completed | 211 ms |
| 20 days ago | Handshake completed | 178 ms |
| 22 days ago | Handshake completed | 184 ms |
| 24 days ago | Handshake completed | 256 ms |
| 26 days ago | Handshake completed | 177 ms |
| 27 days ago | Handshake completed | 66 ms |
| 29 days ago | Handshake completed | 262 ms |
| 29 days ago | Handshake completed | 320 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with pdfzen and makes no claim about it beyond what these checks measured.