Remote MCP · Endpoint

NameWheel MCP server

No. NameWheel answered an MCP handshake 7 hours ago.

UpLast checked 7 hours 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
384 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
7 hours agoHandshake completed384 ms
2 days agoHandshake completed350 ms
5 days agoHandshake completed509 ms
7 days agoHandshake completed357 ms
9 days agoHandshake completed561 ms
11 days agoHandshake completed380 ms
13 days agoHandshake completed368 ms
15 days agoHandshake completed355 ms
17 days agoHandshake completed333 ms
19 days agoHandshake completed373 ms
20 days agoHandshake completed341 ms
21 days agoHandshake completed341 ms
23 days agoHandshake completed332 ms

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

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.