Remote MCP · Endpoint

Steam MCP server

No. Steam answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/steam/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/steam
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
82 ms
Tools exposed
58 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Steam Web API MCP.
Listing
From the official MCP registry (active).
Recent checks of Steam
CheckedResultHandshake
1 hour agoHandshake completed82 ms
21 hours agoHandshake completed142 ms
2 days agoHandshake completed229 ms
3 days agoHandshake completed961 ms
4 days agoHandshake completed528 ms
5 days agoHandshake completed175 ms
6 days agoHandshake completed115 ms
8 days agoHandshake completed136 ms
11 days agoHandshake completed73 ms
13 days agoHandshake completed82 ms
15 days agoHandshake completed1.62 s
18 days agoHandshake completed91 ms
20 days agoHandshake completed65 ms
22 days agoHandshake completed53 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed1.23 s
27 days agoHandshake completed59 ms
29 days agoHandshake completed69 ms

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