Remote MCP · Endpoint

SkinGrind MCP server

No. SkinGrind answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cloud.skingrind.com/mcp

The last check completed an MCP handshake.

Registry name
com.skingrind/skingrind
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
330 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
CS2 skin prices, case odds and ROI, Armory value, and Trade Up contracts.
Listing
From the official MCP registry (active).
Recent checks of SkinGrind
CheckedResultHandshake
1 hour agoHandshake completed330 ms
2 days agoHandshake completed325 ms
4 days agoHandshake completed316 ms
5 days agoHandshake completed327 ms
7 days agoHandshake completed356 ms
8 days agoHandshake completed350 ms
9 days agoHandshake completed319 ms
12 days agoHandshake completed305 ms
13 days agoHandshake completed531 ms
15 days agoHandshake completed1.31 s
16 days agoHandshake completed496 ms
17 days agoHandshake completed338 ms
19 days agoHandshake completed318 ms
20 days agoHandshake completed319 ms
20 days agoHandshake completed322 ms
21 days agoHandshake completed474 ms
22 days agoHandshake completed485 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 SkinGrind and makes no claim about it beyond what these checks measured.