Remote MCP · Endpoint
compute.wick.pics MCP server
No. compute.wick.pics answered an MCP handshake 1 hour ago.
UpLast checked 1 hour 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
- 815 ms
- Tools exposed
- 25 tools
- Uptime, last 30 days
- 100% from 17 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).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 815 ms |
| 2 days ago | Handshake completed | 839 ms |
| 4 days ago | Handshake completed | 844 ms |
| 5 days ago | Handshake completed | 818 ms |
| 7 days ago | Handshake completed | 874 ms |
| 8 days ago | Handshake completed | 838 ms |
| 9 days ago | Handshake completed | 360 ms |
| 12 days ago | Handshake completed | 776 ms |
| 13 days ago | Handshake completed | 780 ms |
| 15 days ago | Handshake completed | 774 ms |
| 17 days ago | Handshake completed | 764 ms |
| 18 days ago | Handshake completed | 773 ms |
| 19 days ago | Handshake completed | 759 ms |
| 20 days ago | Handshake completed | 787 ms |
| 21 days ago | Handshake completed | 788 ms |
| 21 days ago | Handshake completed | 799 ms |
| 23 days ago | Handshake completed | 761 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 compute.wick.pics and makes no claim about it beyond what these checks measured.