Remote MCP · Endpoint

APICK Identity MCP server

No. APICK Identity answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://apick.app/mcp/identity

The last check completed an MCP handshake.

Registry name
app.apick/identity
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
637 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Korean ID document verification and PII masking APIs
Website
https://apick.app/dev_guide/mcp
Repository
https://github.com/lead788/apick-mcp
Listing
From the official MCP registry (active).
Recent checks of APICK Identity
CheckedResultHandshake
1 hour agoHandshake completed637 ms
2 days agoHandshake completed620 ms
4 days agoHandshake completed589 ms
5 days agoHandshake completed626 ms
7 days agoHandshake completed622 ms
8 days agoHandshake completed608 ms
9 days agoHandshake completed1.90 s
12 days agoHandshake completed613 ms
13 days agoHandshake completed655 ms
15 days agoHandshake completed629 ms
16 days agoHandshake completed600 ms
18 days agoHandshake completed598 ms
19 days agoHandshake completed607 ms
19 days agoHandshake completed588 ms
20 days agoHandshake completed592 ms
21 days agoHandshake completed204 ms
23 days agoHandshake completed208 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with APICK Identity and makes no claim about it beyond what these checks measured.