INDIVIDUAL MCP TOOL

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 frequently the one with no headroom.

dchub.cloudnone authenticationAvailability not checked

LIVE ENDPOINT

https://dchub.cloud/mcp/registry

No auth detected

Connect to this endpoint to inspect the live schema for get_energy_prices and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

dchub.cloud

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dc-hub-intelligence]
url = "https://dchub.cloud/mcp/registry"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dc-hub-intelligence": {
      "type": "http",
      "url": "https://dchub.cloud/mcp/registry"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dc-hub-intelligence
Remote MCP URL: https://dchub.cloud/mcp/registry

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dc-hub-intelligence": {
      "url": "https://dchub.cloud/mcp/registry"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dc-hub-intelligence": {
      "type": "http",
      "url": "https://dchub.cloud/mcp/registry"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dc-hub-intelligence",
  "transport": "streamable-http",
  "url": "https://dchub.cloud/mcp/registry"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

search — Search DC Hub for relevant records (OpenAI Deep Research / ChatGPT connector format).
fetch — Fetch a DC Hub record for an id returned by the `search` tool (OpenAI Deep Research / ChatGPT connector format).
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 capacity, colocation and wholesale data-center markets, AI/GPU compute campuses, fiber routes, diversity and latency, PPAs and energy pricing, tax incentives and permitting, water and climate risk, data-center M&A and deals, power generation, gas and energy infrastructure.
search_facilities — FRONT DOOR CHECK — if the ask is "find <N> MW in <market>" or otherwise wants power / fiber / water / verdict context ATTACHED to the hits, call `execute_plan(intent="<the user's question, unchanged>")` instead of hand-chaining this with three more tools.
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.
get_market_intel — Use when a user asks about ONE data-center market — vacancy, capacity pricing, supply pipeline, dominant operators, YoY growth — across any of 300+ markets.
get_market_dcpi_rank — DCPI rank for a single market: BUILD/CAUTION/AVOID verdict, 0-100 composite_score (verdict-aware), excess_power_score, constraint_score, time_to_power_months.
predict_market_trajectory — Forecast a DCPI market's near-term trajectory (next 1-8 quarters).