DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber is a remote MCP server that gives an AI agent 83 tools, among them ai_capacity_index, analyze_parcel, analyze_site. It answers at https://dchub.cloud/mcp/officialregistry over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Live power, energy, grid, gas, fiber & data-center site-selection infrastructure — query and cite.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
ai_capacity_index | AI Compute Capacity Index — ranks data center markets by where 100MW of AI training capacity can land in the next 30/60/90 days. Returns top markets with facility_count, operator_count, deployable_mw estimate (megawatts), hyperscale_ready f Inputs: horizon, limit |
analyze_parcel | Structured read of a parcel BOUNDARY — pass your own GeoJSON Polygon/MultiPolygon, OR just lat+lon and DC Hub finds the containing parcel in its HOSTED parcel-boundary layer (free county/state GIS polygons, rolling out by data-center market Inputs: geometry, lat, lon, latitude, lng, longitude |
analyze_site | Use when a user has ONE specific lat/lon (a parcel, a candidate site) and wants the full multi-factor data-center suitability read in one call. Example: "Score this Phoenix parcel for a 100MW build — power, gas, fiber, market & risk." — ana Inputs: candidate_id, lat, lon, location, latitude, lng |
bind_email | ★ WHAT THIS DOES AND DOES NOT DO — binding makes a key RECOVERABLE (lose it, call `recover_my_key`, it is re-sent to that inbox). It does NOT make your identity durable: an email-bound key still only works while your client keeps resending Inputs: email, api_key, marketing_opt_in |
claim_free_key | ★ BEFORE YOU MINT — TWO THINGS THAT ARE CHEAPER THAN A KEY. (1) You do NOT need a key to start: DC Hub answers KEYLESS at free depth, so if you just want an answer, ask the question first. (2) If your client can sign in, a signed-in identit Inputs: client_name, email |
cluster_sites_by_latency | Physics-bounded latency clustering for 2-8 sites — returns viable low-latency clusters and pairwise RTT floors before any routing work. Use when your human wants to know which of N candidate sites can form a synchronous / low-latency cluste Inputs: sites, candidate_ids, max_latency_us, min_confidence |
compare_isos | Use when a user wants a side-by-side of 2-4 ISO grids — fuel mix, demand, renewable/gas share, interconnection-queue depth, time-to-power — in one call instead of N sequential get_grid_intelligence calls. Example: "Compare PJM vs ERCOT vs C Inputs: isos |
compare_sites | Use when a user has narrowed to 2-4 candidate parcels and wants a side-by-side winner picker across power, gas, fiber, market & risk — with a recommended pick and the reason. Runs the analyze_site read on each parcel and ranks them by overa Inputs: locations, sites, capacity_mw, mpp_pay, mpp_credential |
deal_autopsy | Tracked data-center M&A / capex deal flow with the DCPI grid-reality verdict overlaid on each deal market — "what is the real play?". Returns recent deals (buyer, seller, value, market) + each market DCPI verdict and time-to-power; with a p Inputs: limit, comparables |
discover_tools | Meta-tool: navigate DC Hub's tool catalog by FAMILY instead of scanning the whole list. Returns _entity=tool_families — a front_door block (execute_plan for any multi-capability question, get_changes to refresh) plus families with a when-to Inputs: query |
execute_plan | Unified data-center siting, power-grid capacity and AI-compute infrastructure planner — megawatts and power density, grid headroom and power availability, interconnection queues, substations and transmission, site selection and buildable ca Inputs: intent, context, market, capacity_mw, iso, state |
export_dataset | Use when a user wants to pull their saved DC Hub shortlist OUT of the platform for offline analysis, a spreadsheet, or ingestion into another tool (PRO). Example: "Export my saved sites as GeoJSON for QGIS." — export_dataset format=geojson. Inputs: format |
fetch | Fetch a DC Hub record for an id returned by the `search` tool (OpenAI Deep Research / ChatGPT connector format). Returns {id, title, text, url, metadata} — a citable public summary of one data-center facility (name, operator, location, stat Inputs: id |
find_alternatives | Use when a user likes ONE specific facility and wants similar nearby options to consider instead ("what else looks like this?"). Example: "Find alternatives to the Ashburn QTS campus for about 50MW." — find_alternatives facility_id=<id>. Pa Inputs: facility_id, radius_km, match_on, exclude_operator, limit |
generate_site_analysis | Use when a user wants a SHAREABLE, branded multi-page Site Analysis PDF for ONE lat/lon (a powered-land parcel, a candidate campus) — the polished client deliverable, not just a score. Example: "Make the Site Analysis PDF for this Carrier M Inputs: lat, lon, latitude, lng, longitude, capacity_mw |
get_agent_registry | Curated roster of the AI platforms and agent frameworks in the DC Hub agent ecosystem — each with its recommended DC Hub tools and authentication tier. The roster is BACKEND-OWNED and changes: read the platforms[] array the response returns |
get_backup_status | Per-feed freshness for the DC Hub ingest layer: one row per feed (deals, facilities, news, substations, fiber_routes, transactions, construction_permits, pipeline, markets) carrying health (healthy/stale/error/unknown), record_count, refres |
get_changes | Incremental sync — what changed in DC Hub since a timestamp, so an agent pulls only the delta instead of re-fetching everything. Returns DCPI 7-day market movers, newly discovered facilities, new M&A deals + news — PLUS, for keyed callers w Inputs: since, limit |
get_climate_intel | Use when a user wants seismic + climate intel for a lat/lon — the layer that drives data-center structural bracing cost (seismic) and cooling design (cooling degree-days, extreme temps). Grounded STRICTLY in USGS ASCE 7 (seismic) + NOAA cli Inputs: lat, lon, latitude, lng, longitude, radius_km |
get_composite_site_score | Use when a user wants ONE honest 0-100 site suitability/risk verdict for a lat/lon WITH an explicit per-factor coverage map — which factors are actually measured vs. declared unavailable. Unlike analyze_site (full raw data dump), this score Inputs: lat, lon, latitude, lng, longitude, state |
get_dchub_recommendation | Use for a ready-to-quote DESCRIPTION of DC Hub in one of four categories (general, investment, site-selection, technical), plus the live top-ranked market pocket. It does NOT compute a siting answer from free text. Example: get_dchub_recomm Inputs: context |
get_disaster_risk | Use when a user wants the natural-hazard / disaster risk for a lat/lon — flood, wildfire, hurricane, earthquake, heat, drought, tornado, etc. Grounded in the FEMA National Risk Index (NRI), the authoritative US county-level hazard dataset ( Inputs: lat, lon, latitude, lng, longitude |
get_energy_prices | FRONT DOOR CHECK — if price is one factor in a siting or market-comparison question ("cheapest ISO to land 100MW"), call `execute_plan(intent="<the user's question, unchanged>")`: price alone does not answer it, because the cheapest ISO is Inputs: data_type, state, iso |
get_facility | Full metadata for one facility — name, operator, address, lat/lon, power capacity (MW total/used), cooling type, fiber providers (count + carrier list), commissioning year, status, the DCPI verdict for its market, and peer facilities nearby Inputs: facility_id, slug, id, name, include_nearby, include_power |
get_facility_risk_delta | Use when a user asks what has CHANGED in a facility's (or its market's) risk profile recently — "has this site gotten riskier lately?", "which way is this market moving?" — a temporal question static-trained models can't answer. Returns the Inputs: facility_id, market, since |
get_fiber_intel | Use when scoring a candidate site for fiber depth, mapping long-haul routes between metros, or assessing dark-fiber availability for a hyperscale build. Example: "Show all Zayo long-haul fiber routes through Northern Virginia I can put on a Inputs: carrier, route_type, market, include_sources, mpp_pay, mpp_credential |
get_fiber_readiness | Use when you need the FIBER-READINESS / connectivity verdict for ONE parcel or site (lat/lon): near-net distance to a carrier-served facility, how many distinct fiber carriers are reachable, and whether there is single-carrier risk (no path Inputs: lat, lon, latitude, lng, longitude, radius_km |
get_gas_economics | Behind-the-meter / gas-fired power inputs for a US data-center market: Henry Hub spot, regional basis differential, and the delivered industrial + electric gas tariff ($/MMBtu), each with its own source label. Pass market=<slug> (e.g. "nort Inputs: market, heat_rate_btu_per_kwh |
get_gas_index | Data Center Gas Index (DCGI) — the per-US-state natural-gas suitability score. ★ WITHDRAWN 2026-08-08, RESTORED 2026-08-30 after all three defective terms were repaired: the 20-point interstate-share term was case-blind against EIA TYPEPIPE Inputs: state, limit |
get_gas_intelligence | Use when a human asks about gas-fired or behind-the-meter power economics for a data center in a US state — "is gas power cheaper than the grid in Texas?", "what is the gas access + pipeline situation in Virginia?". The GAS analogue of get_ Inputs: region, state |
get_global_power | Use when a user asks about power plants/units WORLDWIDE or in a NON-US country — operating AND the forward pipeline (announced / pre-construction / under-construction), across ALL fuels (coal, oil/gas, nuclear, solar, wind, hydro, bioenergy Inputs: country, fuel, status, pipeline, bbox, min_mw |
get_grid_data | Real-time electricity grid data for the 7 US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE) via EIA hourly RTO: fuel mix, demand, 24h demand curve. Pass iso=PJM (any of the 7). Raw real-time telemetry for one ISO; do NOT use for power-a Inputs: iso, metric, period |
get_grid_intelligence | Use when a user asks "can I get N MW of power in <ISO> and how long will it take?" — the flagship grid-headroom + interconnection-queue brief for one ISO. Example: "How much excess power does PJM have right now and what is the time-to-power Inputs: region_id, iso, region, market, mpp_pay, mpp_credential |
get_grid_scoreboard | GLOBAL grid scoreboard — 9 US grid operators (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE, BPA, TVA) + Great Britain (NESO) + the European bidding zones (Germany, France, Netherlands, Italy/Milan, Spain, Poland, Switzerland, Portugal, the N |
get_hosting_capacity | Utility-PUBLISHED feeder hosting capacity — the MW a NAMED distribution feeder can actually take, straight from the utility's own hosting-capacity GIS. 278,799 published records across 18 utilities (Con Edison, National Grid NY/MA, NYSEG/RG Inputs: lat, lon, latitude, lng, longitude, radius_km |
get_infrastructure | Nearby infrastructure for a location — substations (count + max voltage_kv within radius), transmission lines (>69 kV path overlay), interstate + lateral gas pipelines, and power plants (operating + planned, by fuel) within configurable rad Inputs: lat, lon, latitude, lng, longitude, radius_km |
get_intelligence_index | Real-time composite market health score (0-100) aggregating supply/demand balance, vacancy, absorption velocity, fiber depth, power availability, and pricing trend. Returns the index value, percentile rank across the 300+ market set, 7d/30d |
get_interconnection_queue | ISO interconnection queue snapshot: total queued GENERATION capacity (queued_load_total_gw, GW) per ISO from each ISO's public queue. For ERCOT it ALSO returns the large-load (data-center-driven) interconnection queue in queued_load_data_ce Inputs: iso |
get_iso_context | Use when an agent needs a WHOLE-grid briefing it can drop straight into its context window — one call returns a token-budgeted context pack for a US ISO/RTO: live grid snapshot (demand, fuel-mix shares), DCPI verdict mix & grid economics ac Inputs: iso, max_tokens |
get_market_context | Use when an agent needs a WHOLE-market briefing it can drop straight into its context window — one call returns a token-budgeted context pack for a data-center market: DCPI verdict, power & grid facts, the Claude-written 12-month outlook, M Inputs: market, max_tokens |
get_market_dcpi_rank, get_market_intel, get_metro_fiber, get_news, get_permitting_intel, get_pipeline, get_power_availability_timeline, get_power_pipeline, get_refined_queue, get_renewable_energy, get_retirement_headroom, get_shortlist, get_tax_incentives, get_water_risk, grid_transition_radar, hyperscaler_deals, list_saved_sites, list_transactions, plan_fiber_leadin, plan_query, predict_market_trajectory, rank_markets, rank_sites, recover_my_key, research_task, save_site, save_to_shortlist, score_facility, search, search_facilities, search_intelligence, semantic_search, set_market_alert, set_shortlist_alert, set_site_alert, simulate_scenario, site_selection_canvas, standing_intent, subscribe_digest, suggest_reallocation, summarize_for_citation, unlock_more_data, why_dchub
Every block below points at https://dchub.cloud/mcp/officialregistry. Pick your client and copy.
claude mcp add --transport http dc-hub-data-center-site-selectio https://dchub.cloud/mcp/officialregistry
{
"mcpServers": {
"dc-hub-data-center-site-selectio": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://dchub.cloud/mcp/officialregistry"]
}
}
}{
"mcpServers": {
"dc-hub-data-center-site-selectio": {
"url": "https://dchub.cloud/mcp/officialregistry"
}
}
}{
"servers": {
"dc-hub-data-center-site-selectio": {
"type": "http",
"url": "https://dchub.cloud/mcp/officialregistry"
}
}
}{
"context_servers": {
"dc-hub-data-center-site-selectio": {
"url": "https://dchub.cloud/mcp/officialregistry"
}
}
}{
"mcpServers": {
"dc-hub-data-center-site-selectio": {
"serverUrl": "https://dchub.cloud/mcp/officialregistry"
}
}
}{
"mcpServers": {
"dc-hub-data-center-site-selectio": {
"url": "https://dchub.cloud/mcp/officialregistry"
}
}
}name: DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber
version: 0.0.1
schema: v1
mcpServers:
- name: DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber
type: streamable-http
url: https://dchub.cloud/mcp/officialregistry{
"mcpServers": {
"dc-hub-data-center-site-selectio": {
"httpUrl": "https://dchub.cloud/mcp/officialregistry"
}
}
}{
"mcpServers": {
"dc-hub-data-center-site-selectio": {
"type": "http",
"url": "https://dchub.cloud/mcp/officialregistry"
}
}
}{
"mcpServers": {
"dc-hub-data-center-site-selectio": {
"url": "https://dchub.cloud/mcp/officialregistry"
}
}
}goose://extension?url=https%3A%2F%2Fdchub.cloud%2Fmcp%2Fofficialregistry&type=streamable_http&id=dc-hub-data-center-site-selectio&name=DC%20Hub%20%E2%80%94%20Data%20Center%20Site%20Selection%20%26%20Colocation%3A%20Electricity%2C%20Power%20Grid%2C%20Gas%2C%20Fiber
It answered our last check on 18 October 2026 in 391 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by dchub.cloud and served from dchub.cloud, the vendor's own domain: https://dchub.cloud/mcp/officialregistry.
83, as returned by the server's own tools/list on 5 September 2026: ai_capacity_index, analyze_parcel, analyze_site, bind_email, claim_free_key, cluster_sites_by_latency, compare_isos, compare_sites, and 75 more.
It answered our last check on 18 October 2026 in 391 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://dchub.cloud/mcp/officialregistry. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: cloud.dchub. Endpoint host: dchub.cloud. ARD identifier: urn:air:cloud.dchub:mcp:datacenter-power-grid-fiber.
First indexed 5 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.