Remote MCP · Endpoint

DC Hub MCP server

No. DC Hub answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://dchub.cloud/mcp/claude

The last check completed an MCP handshake.

Registry name
cloud.dchub/mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
194 ms
Tools exposed
67 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Orchestration layer for data center and energy intelligence. Start with execute_plan.
Listing
From the official MCP registry (active).
Recent checks of DC Hub
CheckedResultHandshake
5 hours agoHandshake completed194 ms
9 days agoHandshake completed256 ms
10 days agoHandshake completed198 ms
11 days agoHandshake completed208 ms
12 days agoHandshake completed126 ms
14 days agoHandshake completed225 ms
14 days agoHandshake completed208 ms
15 days agoHandshake completed198 ms
17 days agoHandshake completed300 ms
19 days agoHandshake completed219 ms
21 days agoHandshake completed320 ms
24 days agoHandshake completed211 ms
26 days agoHandshake completed172 ms
28 days agoHandshake completed251 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 25 responding of 25.

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 and makes no claim about it beyond what these checks measured.