Remote MCP · Endpoint

APICK Web MCP server

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

UpLast checked 1 hour ago

Server URL

https://apick.app/mcp/web

The last check completed an MCP handshake.

Registry name
app.apick/web
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
647 ms
Tools exposed
36 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Domain/IP, web capture, Google search/maps, YouTube, Instagram, TikTok, X and Amazon data jobs
Listing
From the official MCP registry (active).
Recent checks of APICK Web
CheckedResultHandshake
1 hour agoHandshake completed647 ms
2 days agoHandshake completed641 ms
4 days agoHandshake completed618 ms
5 days agoHandshake completed647 ms
7 days agoHandshake completed654 ms
8 days agoHandshake completed625 ms
9 days agoHandshake completed619 ms
12 days agoHandshake completed603 ms
13 days agoHandshake completed596 ms
15 days agoHandshake completed598 ms
17 days agoHandshake completed198 ms
18 days agoHandshake completed205 ms
19 days agoHandshake completed207 ms
20 days agoHandshake completed208 ms
20 days agoHandshake completed588 ms
21 days agoHandshake completed208 ms
23 days agoHandshake completed205 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 Web and makes no claim about it beyond what these checks measured.