Remote MCP · Endpoint

three.ws for Grok MCP server

No. three.ws for Grok answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://three.ws/api/mcp-grok

The last check completed an MCP handshake.

Registry name
io.github.nirholas/threews-grok
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
178 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Free text/image to 3D for Grok Bot, plus your three.ws agents once signed in. Never spends.
Listing
From the official MCP registry (active).
Recent checks of three.ws for Grok
CheckedResultHandshake
2 hours agoHandshake completed178 ms
1 day agoHandshake completed79 ms
3 days agoHandshake completed63 ms
3 days agoHandshake completed60 ms
4 days agoHandshake completed67 ms
5 days agoHandshake completed66 ms
7 days agoHandshake completed60 ms
10 days agoHandshake completed70 ms
12 days agoHandshake completed78 ms
15 days agoHandshake completed211 ms
17 days agoHandshake completed79 ms
19 days agoHandshake completed762 ms
21 days agoHandshake completed84 ms
23 days agoHandshake completed76 ms
25 days agoHandshake completed69 ms

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

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