Remote MCP · Endpoint

LevelRoam MCP server

No. LevelRoam answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://levelroam.com/mcp

The last check completed an MCP handshake.

Registry name
com.levelroam/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
362 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only game, setup, place, evidence and travel decision tools with explicit provenance.
Listing
From the official MCP registry (active).
Recent checks of LevelRoam
CheckedResultHandshake
1 hour agoHandshake completed362 ms
2 days agoHandshake completed376 ms
4 days agoHandshake completed308 ms
5 days agoHandshake completed419 ms
7 days agoHandshake completed357 ms
8 days agoHandshake completed613 ms
9 days agoHandshake completed497 ms
12 days agoHandshake completed382 ms
13 days agoHandshake completed534 ms
15 days agoHandshake completed572 ms
16 days agoHandshake completed363 ms
17 days agoHandshake completed397 ms
18 days agoHandshake completed362 ms
19 days agoHandshake completed290 ms
20 days agoHandshake completed366 ms
21 days agoHandshake completed367 ms
22 days agoHandshake completed328 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 LevelRoam and makes no claim about it beyond what these checks measured.