Remote MCP · Endpoint

Spelling Bee Hive MCP server

No. Spelling Bee Hive answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://www.spellingbeehive.com/mcp

The last check completed an MCP handshake.

Registry name
com.spellingbeehive/spelling-bee
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
104 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Spelling bee words: spellings, pronunciations, definitions, practice quizzes and winning words.
Listing
From the official MCP registry (active).
Recent checks of Spelling Bee Hive
CheckedResultHandshake
3 hours agoHandshake completed104 ms
18 hours agoHandshake completed110 ms
1 day agoHandshake completed79 ms
3 days agoHandshake completed159 ms
4 days agoHandshake completed83 ms
5 days agoHandshake completed98 ms
6 days agoHandshake completed91 ms
6 days agoHandshake completed73 ms
8 days agoHandshake completed75 ms
11 days agoHandshake completed110 ms
13 days agoHandshake completed118 ms
16 days agoHandshake completed100 ms
18 days agoHandshake completed99 ms
20 days agoHandshake completed108 ms
22 days agoHandshake completed128 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 Spelling Bee Hive and makes no claim about it beyond what these checks measured.