Remote MCP · Endpoint

NameWheel MCP server

No. NameWheel answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://mcp.namewheel.org/mcp

The last check completed an MCP handshake.

Registry name
org.namewheel/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
397 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Fair random picks with the wheel in your chat: pick names, split teams, run certified draws.
Listing
From the official MCP registry (active).
Recent checks of NameWheel
CheckedResultHandshake
42 minutes agoHandshake completed397 ms
3 days agoHandshake completed351 ms
13 days agoHandshake completed399 ms
13 days agoHandshake completed374 ms
15 days agoHandshake completed348 ms
15 days agoHandshake completed339 ms
17 days agoHandshake completed366 ms
18 days agoHandshake completed390 ms
18 days agoHandshake completed358 ms
20 days agoHandshake completed384 ms
22 days agoHandshake completed384 ms
25 days agoHandshake completed350 ms
27 days agoHandshake completed509 ms
30 days agoHandshake completed357 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 23.

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 NameWheel and makes no claim about it beyond what these checks measured.