Remote MCP · Endpoint
3Q PDF & SheetKit MCP server
No. 3Q PDF & SheetKit answered an MCP handshake 9 hours ago.
UpLast checked 9 hours ago
Server URL
https://getwold.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.getwold/3q-pdf
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 127 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- One-time purchase, no subscription: Windows PDF app with 36 offline commands and 8 Excel templates.
- Website
- https://getwold.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 9 hours ago | Handshake completed | 127 ms |
| 4 days ago | Handshake completed | 154 ms |
| 14 days ago | Handshake completed | 107 ms |
| 15 days ago | Handshake completed | 154 ms |
| 15 days ago | Handshake completed | 166 ms |
| 17 days ago | Handshake completed | 100 ms |
| 18 days ago | Handshake completed | 126 ms |
| 19 days ago | Handshake completed | 111 ms |
| 20 days ago | Handshake completed | 127 ms |
| 21 days ago | Handshake completed | 94 ms |
| 23 days ago | Handshake completed | 2.48 s |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 3Q PDF & SheetKit and makes no claim about it beyond what these checks measured.