Verdict. Wvdsh Wavedash MCP server was the more reliable of the two over the last 30 days: 100% uptime against 99.95% (0.05 points). Wvdsh Wavedash MCP server answers faster (502 vs 1029 ms median). Both are graded on the same Glimind checks.
Data as of .
| Metric | Codefmt MCP server | Wvdsh Wavedash MCP server |
|---|---|---|
| Uptime, 30 days | 99.95% | 100% |
| Median handshake latency | 1029 ms | 502 ms |
| p95 handshake latency | 3586 ms | 2397 ms |
| Checks in 30 days | 4,931 | 4,924 |
| Outages, 90 days | 8 | 0 |
| Median recovery | 6 min | — |
| Agent-readiness score | 100/100 (A) | 100/100 (A) |
| Tools | 3 | 4 |
| Tool-list size for an agent | ~582 tokens | ~987 tokens |
| Days observed | 29 | 29 |
Wvdsh Wavedash MCP server was the more reliable of the two over the last 30 days: 100% uptime against 99.95% (0.05 points). Wvdsh Wavedash MCP server answers faster (502 vs 1029 ms median). Both are graded on the same Glimind checks.
Claude Code
claude mcp add --transport http codefmt-mcp-server https://codefmt.dev/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"codefmt-mcp-server": {
"type": "http",
"url": "https://codefmt.dev/api/mcp"
}
}
}
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"
}
}
}
Third-party servers, listed as discovered. Glimind is not affiliated with either. Figures are automated measurements from one region and may lag.