Verdict. Ship Page MCP server and Co Buildmydigital Scanner MCP server had the same 30-day uptime in Glimind's checks (100%). Co Buildmydigital Scanner MCP server answers faster (645 vs 997 ms median). Compare readiness below.
Data as of .
| Metric | Ship Page MCP server | Co Buildmydigital Scanner MCP server |
|---|---|---|
| Uptime, 30 days | 100% | 100% |
| Median handshake latency | 997 ms | 645 ms |
| p95 handshake latency | 3382 ms | 2993 ms |
| Checks in 30 days | 4,961 | 4,887 |
| Outages, 90 days | 0 | 0 |
| Median recovery | — | — |
| Agent-readiness score | 100/100 (A) | 100/100 (A) |
| Tools | 11 | 3 |
| Tool-list size for an agent | ~2,301 tokens | ~522 tokens |
| Days observed | 29 | 29 |
Ship Page MCP server and Co Buildmydigital Scanner MCP server had the same 30-day uptime in Glimind's checks (100%). Co Buildmydigital Scanner MCP server answers faster (645 vs 997 ms median). Compare readiness below.
Claude Code
claude mcp add --transport http ship-page-mcp-server https://ship.page/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ship-page-mcp-server": {
"type": "http",
"url": "https://ship.page/mcp"
}
}
}
Claude Code
claude mcp add --transport http co-buildmydigital-scanner-mcp-server https://buildmydigital.co.uk/mcp/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"co-buildmydigital-scanner-mcp-server": {
"type": "http",
"url": "https://buildmydigital.co.uk/mcp/"
}
}
}
Third-party servers, listed as discovered. Glimind is not affiliated with either. Figures are automated measurements from one region and may lag.