Remote MCP · Endpoint

CSPriceAPI – CS2 skin prices MCP server

No. CSPriceAPI – CS2 skin prices answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://api.cspriceapi.com/mcp

The last check completed an MCP handshake.

Registry name
com.cspriceapi/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
291 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Live CS2 skin prices: BUFF163, YouPin, Skinport, CSFloat, Steam and 8 more markets, Doppler phases
Listing
From the official MCP registry (active).
Recent checks of CSPriceAPI – CS2 skin prices
CheckedResultHandshake
57 minutes agoHandshake completed291 ms
13 hours agoHandshake completed301 ms
1 day agoHandshake completed303 ms
2 days agoHandshake completed311 ms
4 days agoHandshake completed291 ms
7 days agoHandshake completed298 ms
9 days agoHandshake completed295 ms
12 days agoHandshake completed316 ms
14 days agoHandshake completed304 ms
16 days agoHandshake completed293 ms
18 days agoHandshake completed294 ms
20 days agoHandshake completed294 ms
22 days agoHandshake completed293 ms
23 days agoHandshake completed306 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 CSPriceAPI – CS2 skin prices and makes no claim about it beyond what these checks measured.