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
Listing
From the official MCP registry (active).
Recent checks of APICK OCR
CheckedResultHandshake
1 hour agoHandshake completed600 ms
2 days agoHandshake completed685 ms
4 days agoHandshake completed612 ms
5 days agoHandshake completed595 ms
7 days agoHandshake completed599 ms
8 days agoHandshake completed623 ms
9 days agoHandshake completed794 ms
12 days agoHandshake completed615 ms
13 days agoHandshake completed611 ms
15 days agoHandshake completed600 ms
16 days agoHandshake completed603 ms
18 days agoHandshake completed599 ms
19 days agoHandshake completed604 ms
19 days agoHandshake completed606 ms
20 days agoHandshake completed209 ms
21 days agoHandshake completed208 ms
23 days agoHandshake completed200 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.