Remote MCP · Endpoint

WonderKit Discover MCP server

No. WonderKit Discover answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://wonderkit.app/mcp

The last check completed an MCP handshake.

Registry name
app.wonderkit/discover
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only city guides and public itineraries for family and group trips.
Listing
From the official MCP registry (active).
Recent checks of WonderKit Discover
CheckedResultHandshake
1 hour agoHandshake completed150 ms
3 days agoHandshake completed122 ms
12 days agoHandshake completed115 ms
13 days agoHandshake completed128 ms
15 days agoHandshake completed111 ms
15 days agoHandshake completed207 ms
17 days agoHandshake completed120 ms
18 days agoHandshake completed134 ms
18 days agoHandshake completed134 ms
20 days agoHandshake completed147 ms
22 days agoHandshake completed100 ms
25 days agoHandshake completed114 ms
27 days agoHandshake completed440 ms
29 days agoHandshake completed125 ms

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

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 WonderKit Discover and makes no claim about it beyond what these checks measured.