Remote MCP · Endpoint

Wavedash MCP server

No. Wavedash answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://mcp.wavedash.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.wvdsh/wavedash
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
180 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Wavedash docs and workflow guidance for building and publishing browser games.
Listing
From the official MCP registry (active).
Recent checks of Wavedash
CheckedResultHandshake
3 hours agoHandshake completed180 ms
9 days agoHandshake completed137 ms
10 days agoHandshake completed170 ms
11 days agoHandshake completed113 ms
12 days agoHandshake completed150 ms
14 days agoHandshake completed145 ms
14 days agoHandshake completed154 ms
15 days agoHandshake completed309 ms
17 days agoHandshake completed224 ms
19 days agoHandshake completed278 ms
21 days agoHandshake completed127 ms
24 days agoHandshake completed152 ms
26 days agoHandshake completed227 ms
28 days agoHandshake completed211 ms

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

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