Remote MCP · Endpoint

Roblox MCP server

No. Roblox answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/roblox
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
144 ms
Tools exposed
55 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
Roblox MCP.
Listing
From the official MCP registry (active).
Recent checks of Roblox
CheckedResultHandshake
1 hour agoHandshake completed144 ms
21 hours agoHandshake completed271 ms
2 days agoHandshake completed138 ms
3 days agoHandshake completed91 ms
4 days agoHandshake completed132 ms
5 days agoHandshake completed110 ms
6 days agoHandshake completed1.36 s
8 days agoHandshake completed102 ms
11 days agoHandshake completed69 ms
13 days agoHandshake completed73 ms
16 days agoHandshake completed65 ms
18 days agoHandshake completed55 ms
20 days agoHandshake completed53 ms
22 days agoHandshake completed74 ms
24 days agoFailed - the request timed out—
26 days agoFailed - the request timed out—
27 days agoHandshake completed56 ms
29 days agoHandshake completed69 ms

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