Remote MCP · Endpoint
OCRmyPDF by pagespool MCP server
No. OCRmyPDF by pagespool answered an MCP handshake 43 minutes ago.
UpLast checked 43 minutes ago
Server URL
https://api.pagespool.com/mcp/ocrmypdf/
The last check completed an MCP handshake.
- Registry name
- com.pagespool/ocrmypdf
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 320 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Hosted OCRmyPDF: add a searchable text layer to scanned PDFs and images, returned as PDF/A.
- Website
- https://pagespool.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 43 minutes ago | Handshake completed | 320 ms |
| 9 days ago | Handshake completed | 115 ms |
| 10 days ago | Handshake completed | 122 ms |
| 11 days ago | Handshake completed | 110 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 OCRmyPDF by pagespool and makes no claim about it beyond what these checks measured.