Remote MCP · Endpoint
DC Hub — Data Center Energy, Electricity & Power Grid Data: Site Selection, Colocation, Gas, Fiber MCP server
No. DC Hub — Data Center Energy, Electricity & Power Grid Data: Site Selection, Colocation, Gas, Fiber answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://dchub.cloud/mcp/registry
The last check completed an MCP handshake.
- Registry name
- cloud.dchub/mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 287 ms
- Tools exposed
- 94 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Data center energy, electricity & power grid data: DCPI to query and cite, capacity to buy or lease.
- Website
- https://dchub.cloud/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 287 ms |
| 1 day ago | Handshake completed | 225 ms |
| 2 days ago | Handshake completed | 208 ms |
| 3 days ago | Handshake completed | 198 ms |
| 4 days ago | Handshake completed | 271 ms |
| 5 days ago | Handshake completed | 337 ms |
| 7 days ago | Handshake completed | 236 ms |
| 9 days ago | Handshake completed | 206 ms |
| 12 days ago | Handshake completed | 195 ms |
| 14 days ago | Handshake completed | 222 ms |
| 17 days ago | Handshake completed | 157 ms |
| 19 days ago | Handshake completed | 305 ms |
| 21 days ago | Handshake completed | 229 ms |
| 23 days ago | Handshake completed | 193 ms |
| 25 days ago | Handshake completed | 185 ms |
| 26 days ago | Handshake completed | 203 ms |
| 28 days ago | Handshake completed | 231 ms |
| 29 days ago | Handshake completed | 180 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with DC Hub — Data Center Energy, Electricity & Power Grid Data: Site Selection, Colocation, Gas, Fiber and makes no claim about it beyond what these checks measured.