Remote MCP · Endpoint
APICK OCR MCP server
No. APICK OCR answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://apick.app/mcp/ocr
The last check completed an MCP handshake.
- Registry name
- app.apick/ocr
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 600 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- OCR for images and Korean ID documents
- Repository
- https://github.com/lead788/apick-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 600 ms |
| 2 days ago | Handshake completed | 685 ms |
| 4 days ago | Handshake completed | 612 ms |
| 5 days ago | Handshake completed | 595 ms |
| 7 days ago | Handshake completed | 599 ms |
| 8 days ago | Handshake completed | 623 ms |
| 9 days ago | Handshake completed | 794 ms |
| 12 days ago | Handshake completed | 615 ms |
| 13 days ago | Handshake completed | 611 ms |
| 15 days ago | Handshake completed | 600 ms |
| 16 days ago | Handshake completed | 603 ms |
| 18 days ago | Handshake completed | 599 ms |
| 19 days ago | Handshake completed | 604 ms |
| 19 days ago | Handshake completed | 606 ms |
| 20 days ago | Handshake completed | 209 ms |
| 21 days ago | Handshake completed | 208 ms |
| 23 days ago | Handshake completed | 200 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 APICK OCR and makes no claim about it beyond what these checks measured.