Verdict. Pipe2 MCP server and Racecalendar F1 MCP server had the same 30-day uptime in Glimind's checks (100%). Pipe2 MCP server answers faster (908 vs 1228 ms median). Racecalendar F1 MCP server had fewer outages in 90 days (0 vs 4).
Data as of .
| Metric | Pipe2 MCP server | Racecalendar F1 MCP server |
|---|---|---|
| Uptime, 30 days | 100% | 100% |
| Median handshake latency | 908 ms | 1228 ms |
| p95 handshake latency | 2937 ms | 3768 ms |
| Checks in 30 days | 4,917 | 4,869 |
| Outages, 90 days | 4 | 0 |
| Median recovery | 3 min | — |
| Agent-readiness score | 100/100 (A) | 100/100 (A) |
| Tools | 5 | 15 |
| Tool-list size for an agent | ~703 tokens | ~3,986 tokens |
| Days observed | 29 | 29 |
Pipe2 MCP server and Racecalendar F1 MCP server had the same 30-day uptime in Glimind's checks (100%). Pipe2 MCP server answers faster (908 vs 1228 ms median). Racecalendar F1 MCP server had fewer outages in 90 days (0 vs 4).
Claude Code
claude mcp add --transport http pipe2-mcp-server https://mcp.pipe2.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"pipe2-mcp-server": {
"type": "http",
"url": "https://mcp.pipe2.ai/mcp"
}
}
}
Claude Code
claude mcp add --transport http racecalendar-f1-mcp-server https://racecalendar.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"racecalendar-f1-mcp-server": {
"type": "http",
"url": "https://racecalendar.app/mcp"
}
}
}
Third-party servers, listed as discovered. Glimind is not affiliated with either. Figures are automated measurements from one region and may lag.