Remote MCP · Endpoint
Wavedash MCP server
No. Wavedash answered an MCP handshake 1 day ago.
UpLast checked 1 day 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
- 130 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Wavedash docs and workflow guidance for building and publishing browser games.
- Repository
- https://github.com/wvdsh/ai
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 day ago | Handshake completed | 130 ms |
| 3 days ago | Handshake completed | 224 ms |
| 5 days ago | Handshake completed | 266 ms |
| 7 days ago | Handshake completed | 173 ms |
| 9 days ago | Handshake completed | 49 ms |
| 10 days ago | Handshake completed | 209 ms |
| 11 days ago | Handshake completed | 268 ms |
| 13 days ago | Handshake completed | 137 ms |
| 15 days ago | Handshake completed | 117 ms |
| 17 days ago | Handshake completed | 149 ms |
| 18 days ago | Handshake completed | 201 ms |
| 19 days ago | Handshake completed | 149 ms |
| 21 days ago | Handshake completed | 118 ms |
| 22 days ago | Handshake completed | 138 ms |
| 22 days ago | Handshake completed | 120 ms |
| 23 days ago | Handshake completed | 212 ms |
| 24 days ago | Handshake completed | 120 ms |
The last 17 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 Wavedash and makes no claim about it beyond what these checks measured.