Remote MCP · Endpoint

compute.wick.pics MCP server

No. compute.wick.pics answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://compute.wick.pics/mcp/

The last check completed an MCP handshake.

Registry name
pics.wick.compute/market
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
820 ms
Tools exposed
25 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
Live GPU spot market: 1,700+ offers, 10 provider feeds. History, watches, limit orders, no fee
Listing
From the official MCP registry (deprecated).
Recent checks of compute.wick.pics
CheckedResultHandshake
2 hours agoHandshake completed820 ms
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoHandshake completed790 ms
4 days agoHandshake completed806 ms
5 days agoHandshake completed777 ms
6 days agoHandshake completed838 ms
8 days agoHandshake completed1.32 s
11 days agoHandshake completed916 ms
13 days agoHandshake completed916 ms
15 days agoHandshake completed886 ms
18 days agoHandshake completed829 ms
20 days agoHandshake completed815 ms
22 days agoHandshake completed839 ms
24 days agoHandshake completed844 ms
26 days agoHandshake completed818 ms
27 days agoHandshake completed874 ms
29 days agoHandshake completed838 ms

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

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