Verdict. Wvdsh Wavedash MCP server and Imqueue MCP server had the same 30-day uptime in Glimind's checks (100%). Imqueue MCP server answers faster (489 vs 502 ms median). Compare readiness below.
Data as of .
| Metric | Wvdsh Wavedash MCP server | Imqueue MCP server |
|---|---|---|
| Uptime, 30 days | 100% | 100% |
| Median handshake latency | 502 ms | 489 ms |
| p95 handshake latency | 2397 ms | 2761 ms |
| Checks in 30 days | 4,924 | 4,905 |
| Outages, 90 days | 0 | 0 |
| Median recovery | — | — |
| Agent-readiness score | 100/100 (A) | 100/100 (A) |
| Tools | 4 | 7 |
| Tool-list size for an agent | ~987 tokens | ~2,036 tokens |
| Days observed | 29 | 29 |
Wvdsh Wavedash MCP server and Imqueue MCP server had the same 30-day uptime in Glimind's checks (100%). Imqueue MCP server answers faster (489 vs 502 ms median). Compare readiness below.
Claude Code
claude mcp add --transport http wvdsh-wavedash-mcp-server https://mcp.wavedash.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"wvdsh-wavedash-mcp-server": {
"type": "http",
"url": "https://mcp.wavedash.com/mcp"
}
}
}
Claude Code
claude mcp add --transport http imqueue-mcp-server https://mcp.imqueue.org/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"imqueue-mcp-server": {
"type": "http",
"url": "https://mcp.imqueue.org/mcp"
}
}
}
Third-party servers, listed as discovered. Glimind is not affiliated with either. Figures are automated measurements from one region and may lag.