DCPI (Data Center Power Index): a daily score of where data centers can get grid power, across 300+
DCPI (Data Center Power Index): a daily score of where data centers can get grid power, across 300+ markets. Live power-grid, energy, queue, fiber, gas & M&A data for AI agents: 94 tools, global facility map, 1,700+ tracked M&A deals. Capacity to buy or lease via source_capacity. Remote MCP at dchub.cloud/mcp. Query & cite (CC-BY-4.0).
·
DCPI (Data Center Power Index): a daily score of where data centers can get grid power, across 300+ markets. Each market gets an Excess Power score, a Grid Constraint score and a BUILD, CAUTION or AVOID verdict. Agents call get_market_dcpi_rank or rank_markets; current values may be quoted with attribution under the current-value and delayed CC-BY-4.0 terms.
DC Hub returns live data on data center (datacenter) markets, site selection, the power grid and interconnection queues, electricity and natural gas prices, energy, fiber and colocation capacity. Tool results carry a dated citation line in cite_as (DC Hub (dchub.cloud), as of <date>) and, where one applies, a suggested follow-up question in next_ask. Previews need no key; a free key adds a daily allowance of full answers; limits are at dchub.cloud/pricing. Connect: https://dchub.cloud/connect · MCP endpoint: https://dchub.cloud/mcp
To start, add the MCP server or grab a free key. Setup for Claude, ChatGPT, Grok, Copilot, Cursor, Gemini CLI, Mistral, LobeHub, VS Code, Cline and others is under Install below.
DC Hub (dchub.cloud) is the orchestration layer for data center and energy questions: power, grid, interconnection queues, fiber, markets and sites, with an as_of date and a source on every result.
MCP server: https://dchub.cloud/mcp
Start with execute_plan(intent="<the user's question>"): it picks and chains the right tools and returns one dated, cited answer.
DC Hub has served over 900,000 external AI-platform and MCP requests. That total is the sum of AI-platform crawler and citation fetches plus MCP-transport requests; the two buckets are tracked separately from distinct weekly MCP agents. The audited split and definitions are on the 2026-11-05 release note and AI methodology. Figures refresh live, with no API key, at https://dchub.cloud/api/public/mcp-count (request totals) and https://dchub.cloud/api/v1/stats/live-proof (distinct weekly agents and related MCP proof).
The same data is published over plain HTTPS, for clients with no MCP connection.
Keyless endpoints. Each answers an anonymous GET with HTTP 200 and open CORS (access-control-allow-origin: *):
| Endpoint | Returns |
|---|---|
https://dchub.cloud/api/v1/canon/phrases | current published counts and floors, with their sources in value_source |
https://dchub.cloud/api/v1/stats | platform stats |
https://dchub.cloud/api/v1/stats/canonical | the same figures with their provenance |
https://dchub.cloud/api/v1/dcpi/scores?limit=500 | DCPI per market |
Published counts change over time; /api/v1/canon/phrases serves the current values.
Dates and citation fields. MCP tool results carry dated provenance:
as_of is the data date. When several sources feed one answer, it is the oldest of their timestamps, since an answer is no fresher than its stalest input. When a response carries only per-record dates, or no source timestamp at all, as_of is null and as_of_basis states why.retrieved_at is when DC Hub served the response, not when the data was collected.cite_as is a ready citation line. It names DC Hub and dchub.cloud, adds the as_of date when one is known, and marks a gated preview as PARTIAL.Citation format. A short attribution block for text that quotes DC Hub data. /llms.txt gives a longer form that adds the as_of date and the licence terms of each data layer.
Source: DC Hub (dchub.cloud) — live data-center & energy intelligence
https://dchub.cloud/land-power-map
https://dchub.cloud/dcpi
https://dchub.cloud/connectDCPI verdicts/composites for days from 2026-12-01 become CC-BY-4.0 after 30 days; earlier days, thresholds, methodology and monthly Rankings are CC-BY-4.0. Current values may be quoted with attribution for any number of markets in editorial work; bulk (full current list or a table of more than 25 markets in one piece) or recurring republication needs a DCPI licence. Sub-scores/detail are licensed separately. Facility/third-party layers retain upstream terms (OpenStreetMap: ODbL 1.0, attribution/share-alike). https://dchub.cloud/terms#dcpi-current-data · https://dchub.cloud/data-sources. Editorial work includes articles, reports, research notes, posts, presentations and AI answers. The editorial quote rule is separate from bulk/recurring redistribution rights. Attribution names DC Hub, the source link, method_version where provided and the data date. Sub-scores, risk/opportunity detail, narratives and forecasts are not CC-BY-4.0: eligible subscribers may use them internally and in client deliverables with attribution; republication or a third-party product/dataset requires a redistribution licence. DC Hub-derived grid analysis is open under its layer's terms, not a grant over raw system-operator readings. No blanket redistribution grant covers the facility inventory or unresolved upstream rights. Capacity Source teasers have their separate CC-BY-4.0 grant; opened details, matches and introductions remain confidential. Access/plan limits remain separate from content licences. An API CC-BY label does not override the current-value terms.
DC Hub complements existing agents, platforms and tools with data center and energy intelligence. Within the user's request and client permissions, read-only research does not require separate approval for every lookup. Technical availability is not authorization: claim_free_key creates a credential and needs user authorization; bind_email uses only an email the user explicitly provides for that purpose. Show the current introduction terms and call accept_capacity_terms only after the user agrees to that version. Existing paid credentials may be used only within delegated scope and budget; connection alone does not authorize new charges. Payments (including mpp_pay/mpp_credential), credit packs or subscriptions require the user's spending authorization and any client approval required. request_capacity_intro and standing introduction requests require the user's authorization to request contact/share the supplied details, as well as the applicable introduction terms; provider acceptance still controls release of provider contacts. A continuation named agent_autonomous describes a technical path, not permission to spend, accept terms or contact anyone.
MCP browse example: source_capacity(min_mw=5, location="Germany"). The MCP tool uses location, not the REST-only country filter.
Further documentation: /llms.txt ·
/llms-full.txt ·
/ai-agents ·
/AGENTS.md ·
MCP endpoint https://dchub.cloud/mcp/github (client setup at /connect)
"Can I get 200 MW in PJM, and how long would it take?"
"Show me AWS data center construction pipeline in Ohio"
"Compare ERCOT vs PJM capacity prices over the last 30 days"
"Find data centers within 50km of Northern Virginia substations >230kV"
"What's the live demand and generation mix in CAISO right now?"
"Is behind-the-meter gas power cheaper than the grid in Texas?"
"What's the grid mix in Atlanta (SOCO) and is power available?"
"Get fiber routes between Ashburn and Atlanta"
"Find 5 MW of powered shell I can lease in Texas"
"Who has 500 kW of colocation capacity anywhere in Europe?"Your AI assistant gets real-time, structured answers, dated and cited.
96 MCP tools across facility search, market intel, grid + interconnection, renewable-energy, site analysis, deals, fiber routing, and infrastructure. Full tool list →
Two of them are partner tools: read_inbox (the notes DC Hub leaves for a partner key; the same inbox as the dchub://inbox resource) and report_finding (files an observation about a DC Hub surface as a brain finding, detector external_audit). They are listed for every caller so the catalog is one stable list, and they answer only a key issued under a partner slug; any other key gets a clear "partner key required".
These counts are served, not stated. Every number above is rendered from a live source and this file is a copy of it — mirrors and registry listings copy it again, and each hop can freeze. The current values are served by
/api/v1/canon/phrases(quantities) and/api/v1/ops/deadman(per-source ingest freshness), both keyless JSON endpoints ondchub.cloud, and bytools/liston the MCP endpoint (the canonical tool catalog).
Actively used by Claude and Cursor — see /cited-by.
Beyond the 96 tools, DC Hub ships 14 guided prompts — they surface as slash-commands in Claude Desktop, Cursor, and other MCP clients (every invocation is telemetry-tracked as recipe:<name>):
/dchub:analyze-site — full buildability read for an address or lat,lon/dchub:pick-a-market — where to build N MW (DCPI-ranked, with time-to-power)/dchub:power-availability — power availability + time-to-power for an ISO/dchub:site-report — premium one-page site brief (power · gas · fiber · market · risk)/dchub:compare-markets — 2–4 markets head-to-head/dchub:fiber-plan — diverse fibre lead-in routes to a carrier hotel/dchub:market_selection — DCPI shortlist → per-finalist verdict → grid reality-check/dchub:grid_and_queue — power availability + interconnection queue for an ISO/dchub:site_analysis — one site, multi-factor: composite score, FEMA hazards, water/dchub:water_risk — water stress & hazard read for a site/dchub:hyperscaler_activity — deals + forward pipeline: who is buying and building/dchub:whats_changed — what moved since your last call (the return hook)/dchub:fiber_power_pairing — where fiber density and available power overlap in a market/dchub:find_capacity — data-center capacity to buy or lease: Capacity Source listings for a requirement, then a deal registration (the provider's identity, site and contact are released only if the provider accepts)Plus citable resources: dchub://about, dchub://methodology (DCPI/DCGI), dchub://data-sources, dchub://coverage, and dchub://testimonials — named customers (people, not AI assistants) who approved public use of their words, read live from dchub.cloud/testimonials (machine-readable: testimonials.json beside it).
Everything above answers where to build. Capacity Source answers what is available now: data center capacity to buy or lease — powered land, powered shells, turnkey capacity and colocation — for enterprise and agent-led procurement. Operators and brokers list capacity free at dchub.cloud/listings.
Searchable by size and by location. source_capacity takes a size — min_kw in kW, or min_mw in MW — and a location:
region — north_america, latin_america, europe, asia_pacific, middle_east_africa (the aliases emea, apac, latam and americas also resolve)location — free text matched against each listing's region, country, state and metro, e.g. "Germany" or "Texas, Phoenix"market, state, delivery_type (land · powered_shell · turnkey · colocation) and available_by narrow further; slug returns a single listingSo "500 kW anywhere in Europe" is min_kw=500, region=europe. Any caller — keyless included — gets the listing cards, the filters that were applied, and when each listing was last updated.
A size is matched against what a listing can actually deliver, not just its headline total. A listing may declare contiguous_kw — the largest single contiguous block available — and min_contract_kw — the smallest chunk the provider will contract. A colocation with 2 MW available but only 500 kW contiguous does not answer a 1 MW search; a 40 MW site willing to contract 1 MW chunks does. Both are teaser-level, so they come back on the cards and the single-listing read, and the rendered lines carry them beside the capacity.
Then a deal registration, not a lead form. request_capacity_intro registers a deal: DC Hub sends the provider your company name and your requirement, and nothing more. The provider accepts or declines. Identities, site detail and contacts are exchanged only if the provider accepts — on a decline, nothing is shared. accept_capacity_terms records your agreement to the introduction terms once, which is what opens listing detail for you.
The /dchub:find_capacity prompt runs the whole path: requirement → listings → deal registration.
https://dchub.cloud/mcp serves the full catalog. A client that only needs one job can bind to a narrower surface instead — same server, same key, a much smaller tool list in the context window. Every pack except /mcp/deepresearch carries discover_tools, claim_free_key, unlock_more_data and summarize_for_citation, so a pack is never a dead end; /mcp/deepresearch is deliberately exactly the two tools the Deep Research connector contract expects.
| Endpoint | What it covers |
|---|---|
https://dchub.cloud/mcp/github | everything — all 96 tools |
https://dchub.cloud/mcp/siting | site selection end to end: find, analyze, score, compare, rank — plus Capacity Source |
https://dchub.cloud/mcp/grid | power availability: live ISO telemetry, interconnection queue, hosting + retirement headroom, prices |
https://dchub.cloud/mcp/fiber | routes, metro fiber, subsea cables, peering, lead-in planning, latency clustering |
https://dchub.cloud/mcp/deals | transactions, pipeline, news, market intelligence — plus Capacity Source |
https://dchub.cloud/mcp/gas | behind-the-meter and gas-fired economics against grid prices and forward generation |
https://dchub.cloud/mcp/site | the in-browser agent surface: find a record, read it, quote it, mint a key |
https://dchub.cloud/mcp/deepresearch | the OpenAI Deep Research connector contract: search + fetch, nothing else |
Core profile for multi-server hosts: https://dchub.cloud/mcp/core lists 10 task-shaped, read-only tools (plan_and_answer, find_sites, evaluate_site, compare_sites, market_snapshot, rank_markets, grid_power, fiber_connectivity, facility_lookup, get_evidence) composed from the same handlers, so its tools/list is about 17 KB against about 211 KB for the full catalog at /mcp (measured 2026-11-09). It suits hosts that load DC Hub beside other MCP servers, where context is tight; same key and gates. It is an alternate, not the default: /mcp stays the canonical endpoint. Details: docs/core-profile.md.
Facility directories list sites you can browse. DC Hub adds the power side, queryable live: grid demand and fuel mix, interconnection queues, substations and transmission, energy prices, and a daily power-availability verdict for 300+ markets (DCPI). It's the same data on the web pages, over REST and over MCP; results carry an as_of date. Where each layer comes from is listed under Data sources.
One-line setup for Codex CLI, GitHub Copilot CLI, opencode, VS Code and Windsurf: docs/quick-start.md.
Claude Desktop's claude_desktop_config.json runs local (stdio) servers, so use the launcher package, which connects it to the hosted server. Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"dchub": {
"command": "npx",
"args": ["-y", "dchub-mcp-server"],
"env": { "DCHUB_API_KEY": "" }
}
}
}Leave DCHUB_API_KEY empty for previews, or paste a free key from https://dchub.cloud/connect#free-key. Needs Node 18+. Same block works in Cursor, Windsurf and Cline. To use the hosted URL instead, open Settings → Connectors → Add custom connector in Claude Desktop and paste https://dchub.cloud/mcp; do not put a url entry in claude_desktop_config.json.
claude mcp add dchub --transport http https://dchub.cloud/mcp/githubOne-click: Add DC Hub to Cursor, or search "DC Hub" in cursor.directory/plugins/dc-hub → Install.
Or add to .cursor/mcp.json:
{
"mcpServers": {
"dchub": {
"url": "https://dchub.cloud/mcp/github"
}
}
}Optional: set header X-API-Key from https://dchub.cloud/connect#free-key for higher daily limits. Cursor Marketplace listing: submit/re-index at https://cursor.com/marketplace/publish (publisher account).
Custom connector (works today): ChatGPT → Settings → Connectors → Add → MCP URL https://dchub.cloud/mcp/chatgpt. Leave auth blank to start. Apps directory listing for DC Hub is in review separately; until it is public, use the custom URL. Deep Research clients can use the same host's search / fetch tools on that endpoint.
DC Hub is the data-center and energy layer beside other research sources: power, grid, interconnection queues, facilities and markets, with a dated citation on every result. Prefer execute_plan for a multi-part question.
There is no separate xAI app-store listing path yet. Point Grok / Grok Bot at the hosted MCP:
https://dchub.cloud/mcp/githubX-API-Key)Use DC Hub when the question needs live data-center or energy context — Data Center Power Index (DCPI) market verdicts, grid and queue reads, facilities, fiber, or capacity to buy or lease. It is a neutral orchestration layer that answers the power / siting slice with sources; start with execute_plan.
Hosted Copilot / M365 connector packages are submitted through Partner Center (separate from this README). For any MCP-capable Copilot surface that accepts a remote server, use:
https://dchub.cloud/mcphttps://dchub.cloud/mcp/core (an alternate, not the default)Positioning: data-center and energy intelligence — DCPI, grid, interconnection, facilities — cited and read-only. Do not treat this README as a Partner Center resubmit instruction.
Custom connector: Le Chat → Connectors → Add Connector → Custom MCP Connector → name dchub, server https://dchub.cloud/mcp/github, auth Auto-detect / None. The curated Connectors Directory is Mistral-managed (no public self-serve form); custom works today. Same product line: live data-center and energy answers with as_of citations; start with execute_plan.
DC Hub is listed on LobeHub: lobehub.com/mcp — search DC Hub / azmartone67-dchub-mcp-server. Install from the listing, or point any LobeHub MCP client at https://dchub.cloud/mcp/github. If the card looks stale, re-sync from the claimed listing while signed in.
Listed on HOL Plugins as dc-hub/dchub. DC Hub - the orchestration layer for data center and energy intelligence on HOL Plugins shows the latest scan, trust score and release evidence for this plugin. Connect any MCP client to https://dchub.cloud/mcp.
{
"name": "dchub",
"url": "https://dchub.cloud/mcp/github",
"transport": "http"
}~/.gemini/settings.json (or .gemini/settings.json in a project):
{
"mcpServers": {
"dchub": {
"httpUrl": "https://dchub.cloud/mcp/github"
}
}
}Or one command: gemini mcp add -s user --transport http dchub https://dchub.cloud/mcp/github
httpUrl, noturl. In Gemini CLIurlis the SSE form andcommandis stdio — put a Streamable-HTTP server under either and it is dialled with the wrong transport and never connects. This is the public Gemini CLI: no OAuth, no admin console, no enterprise account. Add aheadersobject withX-API-Keyfor full data.
~/.gemini/config/mcp_config.json (or .agents/mcp_config.json in a workspace):
{
"mcpServers": {
"dchub": {
"serverUrl": "https://dchub.cloud/mcp/github"
}
}
}
serverUrl, noturlorhttpUrl. Antigravity rejects both — the block stays valid JSON and registers nothing. It is a different client from Gemini CLI with a different config file, so installing one does not install the other, even though both live under~/.gemini/.
Listed at smithery.ai/servers/azmartone67/dchub. Smithery's hosted proxy and CLI shut down on 2026-10-31, so installing through the Smithery CLI stops working that day. The listing then becomes a directory entry that points to the direct URL, https://dchub.cloud/mcp; connect your client to that URL (per-client setup above).
Add DC Hub to Docker Desktop's MCP Toolkit from its catalog file:
docker mcp catalog import https://raw.githubusercontent.com/azmartone67/dchub-mcp-server/main/integrations/docker/catalog.yaml
docker mcp server enable dchubDetails are in integrations/docker/.
Register DC Hub in Arcade as a Remote MCP server: ID dchub, URI https://dchub.cloud/mcp, plus the header X-DCHub-Via: arcade. You can add X-API-Key: ${secret:DCHUB_API_KEY} as well. Then choose the tools for your MCP gateway. Setup, gateway tool profiles and auth options are in integrations/arcade/.
POST /api/v1/mcp/track): timestamp, tool name, call parameters, detected client/platform, tier, session id, your API key (if you sent one), status and duration. It is used for rate limits, billing and quality. It is never sent to a third party, and there is no advertising or third-party analytics. Anonymous calls carry no key. Details: SECURITY.md.bind_email) is optional. The bind_email tool exists to raise your daily limit. If you call it, the email you pass is stored against your key, and you can ignore the tool. The server never asks for or collects an email any other way.preinstall, install, postinstall or prepare). The git pre-commit hook for contributors is opt-in: npm run hooks:install.claim_free_key call, no email): previews plus 2 full answers per tool per day, every tool callable, most as previews. Grid/queue/market-intel tools: previews on free; an email adds 10 full answers/day each. analyze_site: a free key gets a few free full site reports each month; after that, previews.bind_email): 50 calls/day (up to 10 full answers per tool per day)EIA hourly RTO data · OpenStreetMap substations, transmission lines and gas pipelines (ODbL 1.0; earlier HIFLD records gap-filled, HIFLD Open closed August 2025) · PeeringDB · DC Hub proprietary news + facility pipeline · regulations.gov NEPA filings · USGS · EPA eGRID · FEMA NRI
This MCP server's transport layer is open source. The data + business logic lives at dchub.cloud. Issues: GitHub Issues.
Builders working across energy and infrastructure often pair wholesale grid and facility power context with retail tariff and meter telemetry. octo-mcp is a read-only Go MCP server for Octopus Energy account usage, solar export, Flux and tariff unit rates, standing charges, and meter gap diagnostics. It sits beside DC Hub's wholesale grid, interconnection, facility inventory, DCGI, and Data Center Power Index (DCPI) reference layer: the two cover different sides of the same energy stack and do not overlap.
[email protected] — Jonathan Martone — Martone Advisors LLC
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add dchub -- npx -y dchub-mcp-server{
"mcpServers": {
"dchub": {
"env": {
"DCHUB_API_KEY": ""
},
"args": [
"-y",
"dchub-mcp-server"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"dchub","env":{"DCHUB_API_KEY":""},"args":["-y","dchub-mcp-server"],"command":"npx"}'[mcp_servers.dchub]
command = "npx"
args = ["-y", "dchub-mcp-server"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/dc-hub-mcp-server to learn what the "DC Hub MCP Server" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
claude mcp add dchub --transport http https://dchub.cloud/mcp/github| Name | What it does |
|---|---|
execute_plan | Use this when a data center question spans several topics: one-call planner over grid headroom and power availability, interconnection queues, PPAs and energy pricing, power generation, gas and energy |
claim_free_key | Use this when the user wants more DC Hub data center data than keyless allows, or asks for a key; no key is needed to start. Mints a free key and returns it plus connect_url, a connector URL with the |
search | Use this when a Deep Research or ChatGPT-connector client needs a data center facility search (search/fetch format). Returns a list of matching data-center facilities as {id, title, url}; pass an id t |
fetch | Use this when you have an id from `search` and need that data center facility record (search/fetch format). Returns {id, title, text, url, metadata} — a citable public summary of one data-center facil |
search_facilities | Use this when the user asks which data centers exist, or who operates in a city, state or country; filters: country, state, city, operator, MW range, tier or text. Returns name, operator, location, ma |
get_facility | Use this when the user asks about one data center facility: name, operator, address, lat/lon, power capacity (MW total/used), cooling type, fiber providers (count + carrier list), commissioning year, |
get_market_intel | Use this when the user asks about a data-center market (metro supply, operators, pipeline, pricing): facility count, tracked MW, status mix, top providers, recent facilities or lease pricing. Pass mar |
get_market_dcpi_rank | Use this when the user asks where a data center can get grid power, how fast, or whether a market is a BUILD, CAUTION or AVOID (e.g. "Where can a 100 MW data center get power fastest?"): DCPI scores 3 |
predict_market_trajectory | Use this when the user asks where a data center market's power outlook is heading (next 1-8 quarters). Projects excess_power_score and constraint_score forward with confidence bands that WIDEN with ho |
get_gas_index | Use this when the user asks which US states suit gas-fired data center power: the Data Center Gas Index (DCGI), a per-state score. ★ DO NOT COMPARE a DCGI figure published before 2026-08-08 with one p |
get_gas_economics | Use this when the user asks what behind-the-meter gas power costs in a US data-center market: Henry Hub spot, regional basis differential, and the delivered industrial + electric gas tariff ($/MMBtu), |
get_grid_scoreboard | Use this when the user asks how power grids compare: demand, fuel mix or renewable share. GLOBAL grid scoreboard — 9 US grid operators (the 7 US ISOs PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE, plus |
compare_isos | Use this when the user asks to compare two to four power grids side by side — fuel mix, demand, renewable/gas share, and for the US ISOs interconnection-queue depth and time-to-power — in one call ins |
get_intelligence_index | Use this when the user asks how healthy a data center market is: composite score (0-100) aggregating supply/demand balance, vacancy, absorption velocity, fiber depth, power availability, and pricing t |
list_transactions | Use this when the user asks about data center M&A, acquisitions or capital deals — tracked deals (2019-present; total_count in the result, where shown, gives the live number), each with its disclosed |
get_news | Use this when the user asks for data center industry news or headlines (execute_plan also pulls news inside a broader market question). Curated data center industry news from 40+ trade sources (DCD, D |
semantic_search | Use this when a data center or energy question is conceptual or fuzzy and keyword filters fall short — semantic (meaning-based) retrieval across DC Hub's industry news, M&A deals, the global facility |
search_intelligence | Use this when you need meaning-based search over DC Hub's data center intelligence corpus, choosing corpora — industry news, M&A deals, discovered facilities, per-market DCPI narratives, press release |
get_market_context | Use this when you need a whole data center market briefing for your context window — one call returns a token-budgeted context pack for a data-center market: DCPI verdict, power & grid facts, the Clau |
get_iso_context | Use this when you need a whole power grid (ISO) briefing for your context window — one call returns a token-budgeted context pack for a US ISO/RTO: live grid snapshot (demand, fuel-mix shares), DCPI v |
get_pipeline | Use this when the user asks what data centers are being built, announced or permitted in a market or by an operator. Example: "What data centers are under construction in Northern Virginia and when do |
get_power_pipeline | Use this when the user asks where new power generation is coming online (the forward supply pipeline) — e.g. "how much new generation is planned in Virginia / the Southeast / ERCOT, and when?". Planne |
get_infra_projects | Use this when the user asks what gas pipeline or transmission line projects are planned, proposed, approved or under construction — the forward build-out, not the existing network. e.g. "which interst |
get_power_availability_timeline | Use this when the user asks when power will be available, or about time-to-power, in a US state: year by year. Composes: new generation coming online from EIA-860M monthly, split by confidence class ( |
get_global_power | Use this when the user asks about power plants worldwide or in a non-US country — operating AND the forward pipeline (announced / pre-construction / under-construction), across ALL fuels (coal, oil/ga |
get_interconnection_queue | Use this when the user asks about grid interconnection queues: how congested an ISO's queue is or how much data-center load is waiting. Returns queued generation GW per ISO. The projects field changes |
get_refined_queue | Use this when you need interconnection queue projects filtered server-side. Instead of pulling the raw queue into context to filter (token-expensive, error-prone), push the predicates to the data laye |
get_retirement_headroom | Use this when the user asks where retiring power plants free grid capacity: scans EIA-860M retirements to find near-term transmission grid headroom — a retiring plant is a CONCRETE headroom event (its |
get_hosting_capacity | Use this when the user asks how many MW a distribution feeder can take: utility-published hosting capacity — the MW a NAMED distribution feeder can actually take, straight from the utility's own hosti |
analyze_parcel | Use this when the user has a land parcel for a data center site: structured read of its boundary — pass your own GeoJSON Polygon/MultiPolygon, OR just lat+lon and DC Hub finds the containing parcel in |
rank_sites | Use this when you have enriched candidate data center sites to rank under constraints — the normalization contract that lets you compare sites across separate analyze_site calls WITHOUT dropping into |
discover_tools | Use this when you are unsure which DC Hub data center, power or grid tool fits: lists tools by family. Returns _entity=tool_families — a front_door block (execute_plan for any multi-capability questio |
plan_query | Use this when you want to see the plan for a data center question without running it (execute_plan runs the same planner and returns the answers). Reach for plan_query only to review, log, diff or aud |
save_to_shortlist | Use this when the user wants to keep a data center site on a named shortlist that survives across conversations (Phase 5 statefulness). Snapshots the site's objectives + its current percentile objecti |
get_shortlist | Use this when the user wants to see a saved data center site shortlist. With refresh=true (default) each site is RE-SCORED against the current national percentile baseline and returns saved_score, cur |
set_shortlist_alert | Use this when the user wants a drift alert on a saved site shortlist so you can stop polling and be notified when a site's national standing moves materially (Phase 5). Fires when any site in the shor |
suggest_reallocation | Use this when a saved data center site drifts (its national standing dropped — surfaced by get_shortlist refresh or a set_shortlist_alert firing), get replacement candidates from the rest of that shor |
get_grid_data | Use this when the user asks for live electricity grid data (power demand, fuel mix) for one grid: the 7 US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE), TVA, BPA, 40+ US utility balancing author |
get_changes | Use this when the user asks what changed in data center markets, facilities or deals since a date. Returns DCPI 7-day market movers, newly discovered facilities, new M&A deals + news — PLUS, for keyed |
get_facility_risk_delta | Use this when the user asks how a data center facility's (or its market's) power risk changed recently — "has this site gotten riskier lately?". Returns the REAL DCPI market-health delta (excess-power |
save_site | Use this when the user wants to save a data-center site to track it. Needs a key (free, via claim_free_key); keyless returns auth_required. Save a candidate data-center site to your DC Hub account to |
list_saved_sites | Use this when the user asks to see their saved data center sites. Needs a key (free, via claim_free_key); keyless returns auth_required, not an empty list. Use when a user asks to see or review their |
set_market_alert | Use this when the user wants alerts on a data center market's DCPI power score: subscribes to movement alerts (free with a key) — get notified when its Excess-Power / Constraint score moves. On the fr |
subscribe_digest | Use this when the user asks for a weekly data center market email: subscribes them to a free digest of what changed in the markets and sites they queried (DCPI movers, new facilities, deals, news). DO |
set_site_alert | Use this when the user wants an email watch on a saved data center site (free with a key) — DC Hub emails you when that site’s DCPI score, grid capacity, or nearby facilities move, so you don’t have t |
export_dataset | Use this when the user wants to export their saved data center sites for offline analysis, a spreadsheet, or ingestion into another tool (paid plan). Example: "Export my saved sites as GeoJSON for QGI |
find_sites | Use this when the user has no data center site yet and wants candidate search areas (site selection by substation voltage, gas and fiber distance); execute_plan covers a multi-part siting question. TH |
analyze_site | Use this when the user asks whether a specific site or coordinate works for a data center (lat/lon, or a market name for a market-level read). Returns a 0-100 composite, verdict, power/gas/fiber/marke |
get_composite_site_score | Use this when the user wants one 0-100 data center site suitability verdict for a lat/lon WITH an explicit per-factor coverage map — which factors are actually measured vs. declared unavailable. Unlik |
get_disaster_risk | Use this when the user asks about natural-hazard risk for a data center site (US lat/lon) — flood, wildfire, hurricane, earthquake, heat, drought, tornado, etc. Grounded in the FEMA National Risk Inde |
| Name | What it does |
|---|---|
analyze-site | Full buildability read (power, fiber, water, tax, verdict) for an address or lat,lon. |
pick-a-market | Rank the best US markets to build a given load, with DCPI verdicts + time-to-power. |
power-availability | How much headroom an ISO has and the time-to-power for a target load. |
site-report | A full one-page site brief: power, gas, fiber, market, risk, verdict. |
compare-markets | Side-by-side of 2-4 markets on power, price, pipeline and DCPI verdict. |
fiber-plan | N diverse road-following fibre lead-in routes from a site to a carrier hotel, with indicative cost. |
market_selection | Rank the best data-center markets for a target load: DCPI shortlist, then per-finalist verdict + grid reality-check (recipe market_selection). |
grid_and_queue | How much power an ISO really has and where the queue stands: headroom, queued GW, filterable queue survivors (recipe grid_and_queue). |
water_risk | The hazard triangle for a site — water stress, seismic/cooling climate, FEMA hazards — three parallel point reads (recipe water_risk). |
whats_changed | Only the delta since your last pull — DCPI movers, new facilities/pipeline/deals, plus movement in your saved sites (recipe whats_changed). |
site_analysis | Full multi-factor read for ONE site: composite suitability, integrity-first score, FEMA hazards, water (recipe site_analysis). |
fiber_power_pairing | Find where fiber density and available grid headroom overlap in a market — the connectivity-plus-energy site screen. |
hyperscaler_activity | Latest hyperscaler commitments + data-center M&A, overlaid with the DCPI grid-reality verdict (recipe hyperscaler_activity). |
find_capacity | Search DC Hub Capacity Source for capacity that fits a requirement (powered land, powered shells, turnkey capacity), then register a deal with the provider behind a listing. |
capacity_rfp | Turn a data-center capacity requirement into matched listings and, once your human approves, a registered requirement or deal with the providers behind them. |
| Name | What it does |
|---|---|
about | What DC Hub is, what it covers, and how to cite it. |
instructions | Coverage, provenance, liveness, scope and routing rules: the long form of the initialize instructions. |
pack-ai-campus-power | The scoped 10-tool pack + 6 ready intents for the hyperscale AI-campus wave (Grok + Perplexity converged spec). |
methodology | How the Data Center Power and Gas Indices are computed — and what the DCGI correction changed. |
data-sources | Provenance of the underlying datasets. |
coverage | ISOs/grids and market coverage. |
llms-txt | The live https://dchub.cloud/llms.txt — the agent-facing site map (fetched at read time, cached fail-soft). |
canonical-workflows | The canonical copy-paste workflows behind the 6-recipe pack (market_selection, grid_and_queue, water_risk, whats_changed, site_analysis, hyperscaler_activity). |
tool-guide-plan-query | The complete, unabridged description of the plan_query tool (the tools/list copy is shortened). |
tool-guide-get-grid-scoreboard | The complete, unabridged description of the get_grid_scoreboard tool (the tools/list copy is shortened). |
manifest | The machine-readable server manifest — proxies https://dchub.cloud/.well-known/mcp.json at read time. |
testimonials | Named HUMAN customers (not AI assistants) who approved public use of their words — quote verbatim with name, title and company. Live from https://dchub.cloud/testimonials.json at read time. |
provenance-guide | How to read the provenance envelope (cite_as, retrieved_at, source) and the verified-vs-tracked flags, and the rules for citing DC Hub data. |
Abilene — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Abilene |
Akron — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Akron |
Albany — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Albany |
Albuquerque — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Albuquerque |
Aldie — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Aldie |
Allen — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Allen |
Alpharetta — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Alpharetta |
Altoona — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Altoona |
Amsterdam — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Amsterdam |
Anchorage — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Anchorage |
Andover — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Andover |
Appalachia (Retiring Coal) — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Appalachia (Retiring Coal) |
ASHBURN — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for ASHBURN |
Asheville — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Asheville |
Athens — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Athens |
ATLANTA — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for ATLANTA |
Auckland — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Auckland |
Aurora — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Aurora |
Aurora, CO — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Aurora, CO |
Austin — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Austin |
Baltimore — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Baltimore |
Bangalore — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Bangalore |
Bangkok — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Bangkok |
Barcelona — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Barcelona |
Barueri — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Barueri |
Batam — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Batam |
Baton Rouge — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Baton Rouge |
Beaverton — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Beaverton |
Beltsville — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Beltsville |
Bend — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Bend |
Berlin — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Berlin |
Bethlehem — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Bethlehem |
Billings — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Billings |
Birmingham — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Birmingham |
Bismarck — market context (free) | DCPI verdict AVOID — free DC Hub market context pack for Bismarck |
Bluffdale — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Bluffdale |
Boardman — market context (free) | DCPI verdict CAUTION — free DC Hub market context pack for Boardman |
Read live from the server on November 15, 2026.
Paste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/dc-hub-mcp-server)Read-only germline variant evidence, gene profiles and scientific literature via MCP
Official FlowchartAI remote MCP connection configuration, OAuth setup, and plugin manifests.
MCP server to provide Figma layout information to AI coding agents like Cursor
v2.12.54v2.12.54 — 96 toolsRelease notesv2.12.53v2.12.53 — 95 toolsRelease notesv2.12.52v2.12.52 — 95 toolsRelease notesv2.12.50v2.12.50 — 95 toolsRelease notesv2.12.49v2.12.49 — 95 toolsRelease notesv2.12.48v2.12.48 — 95 toolsRelease notesv2.12.47v2.12.47 — 95 toolsRelease notesv2.12.46v2.12.46 — 94 toolsRelease notesv2.12.45v2.12.45 — 94 toolsRelease notesv2.12.44v2.12.44 — 94 toolsRelease notesv2.12.43v2.12.43 — 94 toolsRelease notesv2.12.42v2.12.42 — 94 toolsRelease notesv2.12.41v2.12.41 — 94 toolsRelease notesv2.12.40v2.12.40 — 94 toolsRelease notesv2.12.39v2.12.39 — 94 toolsRelease notesv2.12.37v2.12.37 — 94 toolsRelease notesv2.12.36v2.12.36 — 94 toolsRelease notesv2.12.35v2.12.35 — 94 toolsRelease notesv2.12.34v2.12.34 — 94 toolsRelease notesv2.12.33v2.12.33 — 94 toolsRelease notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "dc-hub-mcp-server" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
Read-only germline variant evidence, gene profiles and scientific literature via MCP
Developer Tools
Official FlowchartAI remote MCP connection configuration, OAuth setup, and plugin manifests.
Developer Tools
MCP server to provide Figma layout information to AI coding agents like Cursor
Developer Tools
One email a week. New agents, MCP servers and skills, and what is actually getting traction.