Remote MCP · Endpoint

SteamGPT MCP server

No. SteamGPT answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://steamgpt.net/mcp

The last check completed an MCP handshake.

Registry name
net.steamgpt/steamgpt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
6.74 s
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Steam profiles, SteamID conversion, bans, FACEIT stats, friends and comparisons. Free, no API key.
Listing
From the official MCP registry (active).
Recent checks of SteamGPT
CheckedResultHandshake
1 hour agoHandshake completed6.74 s
2 days agoHandshake completed832 ms
4 days agoHandshake completed166 ms
5 days agoHandshake completed134 ms
7 days agoHandshake completed145 ms
8 days agoHandshake completed374 ms
9 days agoHandshake completed434 ms
12 days agoHandshake completed150 ms
13 days agoHandshake completed150 ms
15 days agoHandshake completed195 ms
17 days agoHandshake completed129 ms
18 days agoHandshake completed135 ms
19 days agoHandshake completed142 ms
20 days agoHandshake completed138 ms
21 days agoHandshake completed140 ms
21 days agoHandshake completed160 ms
23 days agoHandshake completed588 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 SteamGPT and makes no claim about it beyond what these checks measured.