Remote MCP · Endpoint

WordSearchClub MCP server

No. WordSearchClub answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://wordsearchclub.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.iyuyoung/wordsearchclub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
219 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find fixed word searches and their matching printable puzzles and separate answer sheets.
Listing
From the official MCP registry (active).
Recent checks of WordSearchClub
CheckedResultHandshake
44 minutes agoHandshake completed219 ms
8 days agoHandshake completed539 ms
9 days agoHandshake completed227 ms
11 days agoHandshake completed199 ms
12 days agoHandshake completed346 ms
13 days agoHandshake completed345 ms
14 days agoHandshake completed193 ms
14 days agoHandshake completed278 ms
16 days agoHandshake completed262 ms
19 days agoHandshake completed213 ms
21 days agoHandshake completed178 ms
24 days agoHandshake completed326 ms
26 days agoHandshake completed289 ms
28 days agoHandshake completed201 ms

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