Remote MCP · Endpoint

Zovo Word Guess MCP server

No. Zovo Word Guess answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://word-guess.zovo.one/mcp

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/word-guess
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
217 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Make your own custom word-guessing game and send it to a friend.
Listing
From the official MCP registry (active).
Recent checks of Zovo Word Guess
CheckedResultHandshake
44 minutes agoHandshake completed217 ms
3 days agoHandshake completed159 ms
13 days agoHandshake completed265 ms
13 days agoHandshake completed239 ms
15 days agoHandshake completed200 ms
15 days agoHandshake completed178 ms
17 days agoHandshake completed268 ms
18 days agoHandshake completed206 ms
18 days agoHandshake completed232 ms
20 days agoHandshake completed262 ms
22 days agoHandshake completed180 ms
25 days agoHandshake completed171 ms
27 days agoHandshake completed201 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 Zovo Word Guess and makes no claim about it beyond what these checks measured.