Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory
Menu

DC Hub — Data Center Energy, Electricity & Power Grid Data: Site Selection, Colocation, Gas, Fiber (/mcp/core)

MCP server · dchub.cloud · found in a public list · checked since 2026-11-09

Live, handshake completed · latest check

As JSON

Scores data center sites by power, grid and energy data, and compares candidate locations.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/7). What this means

Placed in Energy and fuel data: Household and business electricity and gas tariffs, grid and generation data, fuel prices and solar estimates.

https://dchub.cloud/mcp/core MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person. See 6 endpoints from dchub.cloud.

Our checks

An unpaid request daily, from eastern North America

Last 1 checks, oldest to newest; room for 29 more

1 passed, 0 failed, 29 not run.

Passed, 30 daysshort history1 of 1 run
Checks missed0in 30 days
Response, latest349 mswhole handshake
Scheduledailyset by usage; rule below
Checked since2026-11-09under 1 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hourssince 2026-11-0910——————
7 dayssince 2026-11-0910——————
30 dayssince 2026-11-0910——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

compare_sitesevaluate_sitefacility_lookupfiber_connectivityfind_sitesget_evidencegrid_powermarket_snapshotplan_and_answerrank_markets

Tools
10
This list since
2026-11-09
First listed to us
2026-11-09
List changes, 90 days
0

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
tools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

Calls it declares

  • plan_and_answer intent query question dry_run market state iso lat lon capacity_mw
  • find_sites mode state lat lon radius_km min_voltage_kv max_gas_km max_fiber_km capacity_mw region iso max_months limit
  • evaluate_site lat lon location state capacity_mw include
  • compare_sites locations* capacity_mw
  • market_snapshot market* detail
  • rank_markets criteria region limit min_capacity_mw
  • grid_power iso market state capacity_mw include
  • fiber_connectivity lat lon market radius_km include
  • facility_lookup id name query country state city operator min_capacity_mw limit
  • get_evidence subject layer as_of source_url since

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Maps, places and weather / Energy and fuel data (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/7, tree/3) on 2026-11-09. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:EWR		 Live, handshake completed HTTP 200 349 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for under 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_30f624e0fa765380