Verdict. Ticktape MCP server and Failecho MCP server had the same 30-day uptime in Glimind's checks (100%). Failecho MCP server answers faster (540 vs 677 ms median). Ticktape MCP server had fewer outages in 90 days (0 vs 7).
Data as of .
| Metric | Ticktape MCP server | Failecho MCP server |
|---|---|---|
| Uptime, 30 days | 100% | 100% |
| Median handshake latency | 677 ms | 540 ms |
| p95 handshake latency | 2807 ms | 2210 ms |
| Checks in 30 days | 4,997 | 5,012 |
| Outages, 90 days | 0 | 7 |
| Median recovery | — | 5 min |
| Agent-readiness score | 100/100 (A) | 100/100 (A) |
| Tools | 5 | 4 |
| Tool-list size for an agent | ~998 tokens | ~1,545 tokens |
| Days observed | 29 | 29 |
Ticktape MCP server and Failecho MCP server had the same 30-day uptime in Glimind's checks (100%). Failecho MCP server answers faster (540 vs 677 ms median). Ticktape MCP server had fewer outages in 90 days (0 vs 7).
Claude Code
claude mcp add --transport http ticktape-mcp-server https://ticktape.cc/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ticktape-mcp-server": {
"type": "http",
"url": "https://ticktape.cc/mcp"
}
}
}
Claude Code
claude mcp add --transport http failecho-mcp-server https://failecho.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"failecho-mcp-server": {
"type": "http",
"url": "https://failecho.com/mcp"
}
}
}
Third-party servers, listed as discovered. Glimind is not affiliated with either. Figures are automated measurements from one region and may lag.