Verdict. Isitdns MCP server was the more reliable of the two over the last 30 days: 100% uptime against 99.78% (0.22 points). Isitdns MCP server answers faster (538 vs 1211 ms median). Both are graded on the same Glimind checks.
Data as of .
| Metric | Uptimeify MCP server | Isitdns MCP server |
|---|---|---|
| Uptime, 30 days | 99.78% | 100% |
| Median handshake latency | 1211 ms | 538 ms |
| p95 handshake latency | 3937 ms | 2489 ms |
| Checks in 30 days | 4,147 | 4,941 |
| Outages, 90 days | 11 | 0 |
| Median recovery | 7 min | — |
| Agent-readiness score | 100/100 (A) | 96/100 (A) |
| Tools | 20 | 6 |
| Tool-list size for an agent | ~3,703 tokens | ~1,785 tokens |
| Days observed | 29 | 29 |
Isitdns MCP server was the more reliable of the two over the last 30 days: 100% uptime against 99.78% (0.22 points). Isitdns MCP server answers faster (538 vs 1211 ms median). Both are graded on the same Glimind checks.
Claude Code
claude mcp add --transport http uptimeify-mcp-server https://uptimeify.io/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"uptimeify-mcp-server": {
"type": "http",
"url": "https://uptimeify.io/mcp"
}
}
}
Claude Code
claude mcp add --transport http isitdns-mcp-server https://isitdns.net/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"isitdns-mcp-server": {
"type": "http",
"url": "https://isitdns.net/mcp"
}
}
}
Third-party servers, listed as discovered. Glimind is not affiliated with either. Figures are automated measurements from one region and may lag.