Remote MCP · Endpoint

APICK Skills MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://apick.app/mcp/skills

The last check failed: the server returned an HTTP error.

Registry name
app.apick/skills
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Search, quote and run reviewed Skills; points are charged only when a validated result returns
Listing
From the official MCP registry (deprecated).
Recent checks of APICK Skills
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoHandshake completed582 ms
5 days agoHandshake completed582 ms
7 days agoHandshake completed612 ms
9 days agoHandshake completed605 ms
11 days agoHandshake completed782 ms
13 days agoHandshake completed604 ms
15 days agoHandshake completed609 ms
17 days agoHandshake completed609 ms
18 days agoHandshake completed612 ms
19 days agoHandshake completed2.31 s
21 days agoHandshake completed608 ms
23 days agoHandshake completed590 ms
25 days agoHandshake completed603 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 14.

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 Skills and makes no claim about it beyond what these checks measured.