# DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber (remote · dchub.cloud)

DCPI grid-power scores for 300+ markets, plus capacity to buy or lease; query and cite.

- Trust score: 82/100 (high trust)
- Change this week: +9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- remote · `dchub.cloud`: 82/100 (this document), [markdown](https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-claude.md), [page](https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-claude)
- remote · `dchub.cloud`: 84/100, [markdown](https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-grok.md), [page](https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-grok)
- remote · `dchub.cloud`: 78/100, [markdown](https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-registry.md), [page](https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-registry)

## Channel facts

- Endpoint: `https://dchub.cloud/mcp/claude`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.12.37`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 13173 tokens (~196/item across 67 items; 67 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 55/100
  - Stability check failed: schema churn in the 17 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_plan" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 68 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the DC Hub — Data Center Site Selection & Colocation… MCP server?

DC Hub — Data Center Site Selection & Colocation… is a hosted endpoint at https://dchub.cloud/mcp/claude, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http cloud-dchub-mcp-server 'https://dchub.cloud/mcp/claude'
```

### Cursor

```json
{
  "mcpServers": {
    "cloud-dchub-mcp-server": {
      "url": "https://dchub.cloud/mcp/claude"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloud-dchub-mcp-server": {
      "type": "http",
      "url": "https://dchub.cloud/mcp/claude"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cloud-dchub-mcp-server]
url = "https://dchub.cloud/mcp/claude"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloud-dchub-mcp-server": {
      "type": "remote",
      "url": "https://dchub.cloud/mcp/claude",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloud-dchub-mcp-server --url 'https://dchub.cloud/mcp/claude' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cloud-dchub-mcp-server:
    url: "https://dchub.cloud/mcp/claude"
```

### Netclaw

```json
{
  "McpServers": {
    "cloud-dchub-mcp-server": {
      "Transport": "http",
      "Url": "https://dchub.cloud/mcp/claude"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloud-dchub-mcp-server -t streamable-http -u 'https://dchub.cloud/mcp/claude'
```

### Other

```json
{
  "mcpServers": {
    "cloud-dchub-mcp-server": {
      "type": "http",
      "url": "https://dchub.cloud/mcp/claude"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 82, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-14 (score 81, +1)

- [functional] Server version: 2.12.36 → 2.12.37

### 2026-10-12 (score 80, 0)

- [functional] Server version: 2.12.34 → 2.12.36

### 2026-10-11 (score 80, +7)

- [security regression] Stability: 0.17 → fail
- [security regression] Tool “research_task” was removed
- [security improvement] HSTS header: fail → pass
- [security improvement] DNSSEC: fail → pass
- [functional] Server version: 2.12.30 → 2.12.34

### 2026-10-04 (score 73, +1)

- [functional] Server version: 2.12.26 → 2.12.27
- [functional] Server version: 2.12.25 → 2.12.26
- [functional] Server version: 2.12.24 → 2.12.25
- [cosmetic] “source_capacity” added an optional parameter “max_sites”
- [cosmetic] “get_water_risk” added an optional parameter “location”
- [cosmetic] “source_capacity” added an optional parameter “max_providers”
- [cosmetic] “source_capacity” added an optional parameter “min_chunk_kw”
- [cosmetic] “source_capacity” added an optional parameter “target_kw”
- [cosmetic] “source_capacity” added an optional parameter “target_mw”
- [cosmetic] “source_capacity” reworded the description of “available_by”

### 2026-10-02 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-30 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-29 (score 71)

First indexed and scored.

## MCP tools (67)

### `search` (~67 tokens)

Search

Search DC Hub for data-center facilities matching a text query. Returns a list of {id, title, url}; pass an id to fetch for the record.

Input parameters:

- `query` (string, required): Free-text query, e.g. "data centers in Northern Virginia" or "Ashburn hyperscale power"

### `fetch` (~75 tokens)

Fetch

Fetch one DC Hub facility record by an id returned from search. Returns {id, title, text, url, metadata} with name, operator, location, status and market.

Input parameters:

- `id` (string, required): A facility id/slug from a prior `search` result, e.g. equinix-dc1-ashburn

### `execute_plan` (~454 tokens)

Execute Plan

Answer a multi-part data-center infrastructure question in one call. Pass the question as intent; a rule-based planner (no AI model) uses the text to choose the lookups (markets, grid, fiber, water, incentives), runs them, and returns each step's result with a replay of how the answer was built. Logging: the intent text is stored in DC Hub's usage log with the call (up to 4,000 characters, with the time, client name, IP address and API key if one is used) and in a plan-run record (first 500 characters). These records have no automatic deletion date. Privacy policy: https://dchub.cloud/privacy

Input parameters:

- `capacity_mw` (number): Target capacity in MW, e.g. 100.
- `context`: Optional structured hints AND step-arg overrides: {lat, lon, iso, market, capacity_mw, candidate_id, state, since} — user-supplied values beat minted ones. The typed top-level params below are merged…
- `intent` (string, required): The user's infrastructure question, passed through UNCHANGED. Examples: "rank markets for a 200 MW AI campus" · "evaluate 100 MW power headroom for a GPU training cluster in PJM" · "compare Dallas vs…
- `iso` (string): ISO/RTO code to pin geography, e.g. "PJM", "ERCOT".
- `lat` (number): Latitude for a specific site.
- `lon` (number): Longitude for a specific site.
- `market` (string): Metro slug or name to pin the analysis to, e.g. "ashburn". Beats any market the planner would mint.
- `max_fanout`: Max per-finalist fan-out calls for one step, 1-3 (default 2)
- `max_steps`: Max plan steps to execute, 1-8 (default 6)
- `state` (string): US state code, e.g. "VA".

### `search_facilities` (~261 tokens)

Search Facilities

Search data-center facilities by name, country, state, city, operator, capacity range (MW) or Uptime tier. Returns matching facilities with location, operator and capacity where known.

Input parameters:

- `city` (string): City name to filter facilities, e.g. Ashburn, Dallas
- `country` (string): ISO 3166-1 alpha-2 country code, e.g. US, GB, SG
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `max_capacity_mw` (number): Maximum power capacity filter in megawatts (MW)
- `min_capacity_mw` (number): Minimum power capacity filter in megawatts (MW)
- `offset` (integer): Pagination offset, 0-based (skip this many results)
- `operator` (string): Operator/provider company name, e.g. Equinix, Digital Realty
- `query` (string): Free-text search over facility name/operator/location (mapped to the backend `q` param), e.g. "hyperscale Ashburn"
- `state` (string): US state abbreviation or region, e.g. VA, TX
- `tier` (integer): Uptime Institute tier filter (1-4)

### `get_facility` (~201 tokens)

Get Facility Details

Get details for one data-center facility by id, slug or name: operator, address, coordinates, power capacity, cooling, fiber carriers, status, its market's DCPI verdict and nearby facilities.

Input parameters:

- `facility_id`: Facility id from a prior search_facilities/search result (numeric or string), e.g. equinix-dc1-ashburn
- `id`: Alias for facility_id — a facility id/slug from a prior search result
- `include_nearby` (boolean): Include peer facilities near this one in the response (default true)
- `include_power` (boolean): Include power capacity detail (total/used MW) in the response (default true)
- `name` (string): Facility name as a fallback lookup when no id/slug is known, e.g. "QTS Ashburn"
- `slug` (string): Facility slug from a prior search result, e.g. digital-realty-iad8

### `get_market_intel` (~150 tokens)

Market Intelligence

Get market intelligence for one data-center market (by market slug): vacancy, capacity pricing, supply pipeline, main operators and growth.

Input parameters:

- `compare_to` (string): Optional second market slug to compare against, e.g. dallas
- `market` (string): Market slug (metro), e.g. northern-virginia, dallas, frankfurt, singapore — valid slugs come from rank_markets / get_market_dcpi_rank
- `metric` (string): Optional single metric to focus on, e.g. vacancy, pricing, absorption, pipeline
- `period` (string): Optional time window for the metric, e.g. ttm, 12mo, ytd

### `get_market_dcpi_rank` (~91 tokens)

DCPI Market Rank

Get the DC Hub Power Index (DCPI) read for one market: BUILD/CAUTION/AVOID verdict, score bands, time to power, data basis and a short analyst narrative.

Input parameters:

- `market_slug` (string, required): Market slug (metro), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank

### `predict_market_trajectory` (~106 tokens)

Predict Market Trajectory

Project a market's DCPI excess-power and constraint scores 1-8 quarters ahead from its daily history, with confidence bands.

Input parameters:

- `horizon_quarters` (integer): Forecast horizon in quarters (1-8, default 4); 2 = ~6 months ahead
- `market_slug` (string, required): Market slug (metro), e.g. dallas, phoenix, northern-virginia — valid slugs come from rank_markets / get_market_dcpi_rank

### `get_gas_index` (~167 tokens)

Gas Index (DCGI)

Get the Data Center Gas Index (DCGI): a per-US-state natural-gas suitability score for gas-fired or behind-the-meter power.

Input parameters:

- `limit` (integer): Max results to return (1-500; default varies by tool)
- `state` (string): US state abbreviation, e.g. TX, VA, AZ. Returns the DCGI score and verdict, plus `gas_price_series` naming which EIA series priced the state. A state that cannot be priced comes back verdict UNSCORED…

### `get_grid_scoreboard` (~47 tokens)

Grid Scoreboard

Get a live scoreboard of grid operators in the US, Great Britain, Europe and parts of Asia-Pacific and Latin America: demand, fuel mix, renewable share and gas share right now.

### `compare_isos` (~114 tokens)

Compare ISO Regions

Compare 2-4 US ISO grids side by side (comma-separated, e.g. "PJM,ERCOT"): fuel mix, demand, renewable and gas share, queue depth and time to power.

Input parameters:

- `isos` (string, required): Comma-separated list of 2-4 US ISO/RTO grid regions to compare, e.g. "PJM,ERCOT,CAISO" (valid: ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE)

### `get_intelligence_index` (~42 tokens)

Market Intelligence Index

Get a composite 0-100 health index for a data-center market, combining supply and demand, vacancy, absorption, fiber, power availability and pricing trend.

### `list_transactions` (~255 tokens)

M&A Transactions

List data-center M&A and capital transactions since 2019. Filter by buyer, seller, deal value, deal type, date range or region.

Input parameters:

- `buyer` (string): Filter by acquiring company name, e.g. Blackstone, KKR, Digital Realty
- `date_from` (string): Earliest deal date, ISO-8601 (YYYY-MM-DD)
- `date_to` (string): Latest deal date, ISO-8601 (YYYY-MM-DD)
- `deal_type` (string): Deal type filter, e.g. acquisition, jv, refinance, recap
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `max_value_usd` (number): Maximum disclosed deal value in US dollars
- `min_value_usd` (number): Minimum disclosed deal value in US dollars, e.g. 1000000000 for USD 1B+
- `offset` (integer): Pagination offset, 0-based (skip this many results)
- `region` (string): Geographic region filter, e.g. us, eu, apac, americas
- `seller` (string): Filter by selling/target company name, e.g. CyrusOne

### `get_news` (~193 tokens)

Industry News

Get curated data-center industry news. Filter by keyword, category, source and date range.

Input parameters:

- `category` (string): News topic filter, e.g. deals, permits, outages, policy, AI
- `date_from` (string): Earliest published date, ISO-8601 (YYYY-MM-DD)
- `date_to` (string): Latest published date, ISO-8601 (YYYY-MM-DD)
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `min_relevance` (number): Minimum relevance score 0-1 to include an item, e.g. 0.5
- `query` (string): Free-text keyword to filter news, e.g. "Stargate" or "interconnection queue"
- `source` (string): Restrict to one trade source, e.g. DCD, "Data Center Frontier", "Capacity Media"

### `semantic_search` (~135 tokens)

Semantic Search

Search DC Hub news, M&A deals, facilities and market analyses by meaning rather than keywords. Returns ranked records with source fields for citation.

Input parameters:

- `corpus` (string): Optional CSV of corpora: news_articles, deals, discovered_facilities, market_narratives (default: all)
- `k` (number): Number of results, 1-15 (default 8)
- `q` (string): Natural-language query (required), e.g. "grids opening up for AI load in the Southeast"
- `query` (string): Alias for q — the same natural-language query; send exactly one of q/query

### `search_intelligence` (~132 tokens)

Search Intelligence

Search DC Hub news, M&A deals, facilities and market analyses by meaning, choosing corpora by name. Same retrieval as semantic_search with a different call shape.

Input parameters:

- `corpus` (string): Optional corpus to restrict to: news | deals | facilities | market_narratives. CSV of several is allowed; default searches all.
- `limit` (number): Max results to return, 1-15 (default 8)
- `q` (string): Alias for query
- `query` (string): Natural-language query (required), e.g. "grids opening up for AI load in the Southeast"

### `get_market_context` (~123 tokens)

Get Market Context

Get a token-budgeted briefing for one data-center market: DCPI verdict, power and grid facts, outlook, deals, pipeline, operators, risks and news, each section timestamped.

Input parameters:

- `market` (string, required): Market slug (required), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank
- `max_tokens` (number): Token budget for the pack, 200-8000 (default 4000); sections are filled in priority order until the budget is spent

### `get_iso_context` (~115 tokens)

Get Iso Context

Get a token-budgeted briefing for one US ISO/RTO: live grid snapshot, DCPI verdicts across its markets, queue depth, benchmark prices and tracked markets.

Input parameters:

- `iso` (string, required): ISO/RTO grid region (required): ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE
- `max_tokens` (number): Token budget for the pack, 200-8000 (default 4000); sections are filled in priority order until the budget is spent

### `get_pipeline` (~208 tokens)

Construction Pipeline

List data centers that are announced, permitted or under construction. Filter by status, country, operator, minimum capacity or expected completion date.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2 country code, e.g. US, DE, SG
- `expected_completion_before` (string): Only projects with expected commissioning before this ISO-8601 date (YYYY-MM-DD), e.g. 2027-01-01
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `min_capacity_mw` (number): Minimum project power capacity filter in megawatts (MW), e.g. 50 for hyperscale
- `offset` (integer): Pagination offset, 0-based (skip this many results)
- `operator` (string): Operator/provider company name, e.g. Equinix, Digital Realty, AWS
- `status` (string): Pipeline stage filter: announced, permitted, construction, or operational

### `source_capacity` (~754 tokens)

Source Capacity

Search DC Hub Capacity Source: listings of data-center capacity offered for sale or lease (powered land, powered shells, turnkey and colocation). Filter by size (min_kw in kW or min_mw in MW), region, location (a country, state or metro), market, delivery_type or available_by. A size is matched against what a listing can deliver (contiguous_kw, its largest contiguous block, and min_contract_kw, its smallest contractable chunk), not only its headline total. Returns listing cards with market, state, capacity, delivery type, availability and when each was last updated; the provider's identity is not included.

Input parameters:

- `available_by` (string): Browse filter: only listings available by this date, as YYYY-MM or YYYY-MM-DD. With a target it is the date the whole requirement must be deliverable by
- `delivery_type` (string): Browse filter: how the capacity is delivered: land, powered_shell, turnkey or colocation
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `location` (string): Browse filter: comma-separated free text matched against each listing's region, country, state and metro, e.g. "Germany" or "Texas, Phoenix"
- `market` (string): Browse filter: market name as it appears on a listing, e.g. "Dallas"
- `max_providers` (integer): Match mode: how many different providers a bundle may use. Default: the same as max_sites
- `max_sites` (integer): Match mode: how many listings the requirement may be split across. Default one, which allows exact fits only; raise it to allow bundles
- `min_chunk_kw` (number): Default: no minimum
- `min_kw` (number): Matched against what a listing can ACTUALLY deliver, not just its headline total: contiguous_kw is the largest single contiguous block available and min_contract_kw the smallest chunk the provider wi…
- `min_mw` (number): Matched against what a listing can ACTUALLY deliver, not just its headline total: contiguous_kw is the largest single contiguous block available and min_contract_kw the smallest chunk the provider wi…
- `region` (string): Browse filter: comma-separated regions from north_america, latin_america, europe, asia_pacific and middle_east_africa; the aliases emea, apac, latam and americas also work, e.g. "europe" or "emea, ap…
- `slug`: One listing: its slug or numeric id exactly as items[].slug / items[].id return it. Omit to browse teaser cards
- `state` (string): Browse filter: two-letter US state, e.g. "TX"
- `target_kw` (number): Match mode: the whole requirement, in kW (target_mw is the same in MW; give one)
- `target_mw` (number): Match mode: the whole requirement, in MW (target_kw is the same in kW; give one). Returns exact fits, bundles and a shortfall instead of teaser cards. Needs a signed-in human

### `get_power_pipeline` (~160 tokens)

Get Power Pipeline

List planned and under-construction US power generators from EIA-860M, including non-ISO regions. Filter by state, balancing authority, status or minimum MW.

Input parameters:

- `ba` (string): Balancing-authority / ISO code, e.g. PJM, ERCO, SOCO, TVA, AZPS
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `min_mw` (number): Minimum nameplate capacity filter in megawatts (MW)
- `state` (string): US state abbreviation to filter generators, e.g. VA, TX
- `status` (string): Generator status code: P/L/T (planned), U/V (under construction), TS (testing)

### `get_infra_projects` (~384 tokens)

Get Infra Projects

List planned, approved and under-construction gas pipeline and transmission line projects. Filter by type, state, status, capacity, voltage and in-service dates.

Input parameters:

- `in_service_after` (string): Only projects entering service on or after this date (YYYY-MM-DD or YYYY). Gas compares the in-service year; transmission the actual, else projected, in-service date
- `in_service_before` (string): Only projects entering service on or before this date (YYYY-MM-DD or YYYY)
- `include_delisted` (boolean): Also return projects the latest source release no longer lists (completed, withdrawn or dropped). Default false
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `min_capacity` (number): Gas only: minimum pipeline capacity in million cubic feet per day (MMcf/d), e.g. 1000. With type=all it narrows to gas projects
- `min_kv` (number): Transmission only: minimum voltage in kilovolts (kV), e.g. 345. With type=all it narrows to transmission projects
- `new_since` (string): Only projects DC Hub first saw on or after this date (YYYY-MM-DD). The initial backfill is never counted as new
- `state` (string): US state abbreviation, e.g. TX or LA. Gas projects match any state they cross; transmission projects are all TX
- `status` (string): Status, case-insensitive; comma list allowed. Gas: Announced, Pre-applied, Applied, Approved, Construction, On Hold, Completed. Transmission: Planned, Conceptual, Under Construction, Completed, Cance…
- `type` (string): Which project list: gas_pipeline (EIA, US-wide), transmission (ERCOT TPIT, Texas only) or all (default)

### `get_power_availability_timeline` (~143 tokens)

Get Power Availability Timeline

Show year by year when power gets easier in one US state: new generation by confidence class, scheduled retirements, and interconnection-queue depth.

Input parameters:

- `mw` (number): Optional target MW for CONTEXT ONLY — echoed back with an explicit note; never converted into an energize-by date, which this data cannot honestly state
- `state` (string, required): 2-letter US state code (required), e.g. OH, GA, TX — the timeline grain; a state can span ISOs and the response reports ISO membership as context
- `years` (number): Window in years from now, 1-6 (default 5)

### `get_global_power` (~203 tokens)

Get Global Power

List power plants and generating units worldwide (operating and pipeline, all fuels) from the Global Energy Monitor tracker. Filter by country, fuel, status, area or size.

Input parameters:

- `bbox` (string): Viewport filter as minLng,minLat,maxLng,maxLat
- `country` (string): Country/area name to filter, e.g. Germany, India, Brazil, Japan
- `fuel` (string): Fuel/type filter, comma-separated for a union: coal, oil/gas, nuclear, solar, wind, hydro, bioenergy, geothermal
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `min_mw` (number): Minimum unit capacity in MW
- `pipeline` (boolean): true = ONLY the forward pipeline (announced + pre-construction + under-construction)
- `status` (string): Status substring filter, e.g. operating, construction, pre-construction, announced

### `get_interconnection_queue` (~82 tokens)

Interconnection Queue

Get the interconnection queue snapshot per US ISO: queued generation capacity, and for ERCOT the large-load (data-center) queue.

Input parameters:

- `iso` (string): ISO/RTO grid region to drill into: ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE; omit for the all-ISO snapshot

### `get_refined_queue` (~642 tokens)

Get Refined Queue

Filter the US ISO interconnection queue server-side by size, wait time, ISO, fuel, status, fiber distance and geocoding, and return only matching projects.

Input parameters:

- `baseload_only` (boolean): Keep only firm/dispatchable fuel (nuclear, gas, steam, geothermal, hydro, coal); exclude wind/solar/storage. Firm-vs-intermittent split only — does NOT sub-divide peaker vs combined-cycle gas (no dut…
- `developer` (string): ERCOT only: keep projects whose developer name contains this text (case-insensitive substring, e.g. 'tenaska'). Developer names come from ERCOTQueue (ercotqueue.com, Matt Prusak, CC BY 4.0) joined to…
- `fuel_type` (string): Isolate a fuel by inclusive substring match on the raw label; comma/semicolon-separated for a union, e.g. 'gas' hits GAS/Natural Gas, 'nuclear,hydro' unions both. Runs the fuel filter server-side ins…
- `geocoded_only` (boolean): Keep only survivors that carry lat/lng (~83% of the queue) — the ones with a ready site_evaluation_handoff you can pipe into analyze_site. Default false
- `iso` (string): Restrict to one or more ISOs, comma-separated for a union: PJM, ERCOT, MISO, CAISO, SPP, NYISO, ISONE (ISO-NE). e.g. iso=ERCOT,PJM. Omit for all; combines with max_ttp_months as an intersection
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `max_fiber_km` (number): Keep only survivors within N km of the nearest MAPPED long-haul fiber route endpoint — coarse backbone proximity from a sparse ~260-node dataset over a county-centroid origin, NOT last-mile fiber. Im…
- `max_ttp_months` (integer): Max time-to-power in months (ISO-level avg interconnection wait; HARD cut keeping projects in ISOs at/under this — PJM ~51, CAISO ~40, ISO-NE ~34, MISO ~34, ERCOT ~33, NYISO ~31, SPP ~24; <=30 leaves…
- `min_mw` (number): Minimum project capacity in MW, e.g. 1000 for 1 GW+
- `status` (string): Queue status filter. Default 'active' = still progressing (excludes withdrawn/cancelled/suspended/in-commercial-operation) — cross-ISO safe (SPP labels live projects 'IA FULLY EXECUTED/ON SCHEDULE' n…

### `get_retirement_headroom` (~249 tokens)

Get Retirement Headroom

Find scheduled generator retirements within a time horizon that could free grid capacity for a target MW, with the nearest substations to each.

Input parameters:

- `fuel_filter` (string): Optional filter for retiring fuel categories, substring-matched (e.g., 'Coal', 'Natural Gas', 'Petroleum').
- `horizon_months` (integer, required): Time horizon in months to look ahead for planned retirements, 1-120 (e.g., 12, 18, 36).
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `region_iso` (string): Optional target region or ISO (e.g., 'MISO', 'PJM', 'ERCOT', 'SPP', 'CAISO', 'NYISO', 'ISONE'). Matches the generator's own EIA balancing-authority code — real market boundaries, not state lines. Com…
- `target_mw` (number, required): Minimum required headroom in megawatts (MW) — filters to retiring generators at/above this size. Also passed through as the handoff's analyze_site capacity_mw (the DC you are siting).

### `get_hosting_capacity` (~368 tokens)

Feeder Hosting Capacity

Get utility-published feeder hosting capacity near a location or in a market: the MW named distribution feeders can accept, from utility GIS data.

Input parameters:

- `capacity_type` (string): Restrict to one published type: "load" (what a new data-center load can DRAW — the type that answers siting), "gen" (DER/generation EXPORT headroom — NOT available load), or "bus_headroom" (transmiss…
- `lat` (number): Latitude of the point to search around, decimal degrees. Must be paired with lon.
- `latitude` (number): Alias for lat — either name works
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `lng` (number): Alias for lon — either name works
- `lon` (number): Longitude of the point to search around, decimal degrees. Must be paired with lat.
- `longitude` (number): Alias for lon — either name works
- `market` (string): Alias for utility — either name works (e.g. "Northern Virginia · Richmond", "New York City · Westchester").
- `min_mw` (number): Only return feeders whose published capacity is at or above this many MW.
- `radius_km` (number): Search radius in km around lat/lon (default 25, max 150). Ignored when utility/market is passed — that mode covers the utility's entire published extent.
- `utility` (string): Utility or market name, case-insensitive substring — e.g. "Ameren Illinois", "Con Edison", "Providence". Searches that utility's whole published territory instead of a point radius. Call with NO argu…

### `analyze_parcel` (~218 tokens)

Analyze Parcel

Analyze a parcel boundary (GeoJSON, or lat/lon in a hosted county) for acreage, shape and nearby infrastructure.

Input parameters:

- `capacity_mw` (number): Optional target load in MW to pass through into the site_evaluation_handoff
- `geometry`: GeoJSON Polygon or MultiPolygon parcel boundary, e.g. {"type":"Polygon","coordinates":[[[lng,lat],[lng,lat],...]]} — a MultiPolygon carries discontinuous parcels as one envelope. Omit to look up the…
- `lat` (number): Latitude of a point ON the parcel — used with lon when geometry is omitted to look up the containing parcel from the hosted county/state GIS layer
- `latitude` (number): Alias for lat — either name works
- `lng` (number): Alias for lon — either name works
- `lon` (number): Longitude of a point ON the parcel (used with lat when geometry is omitted)
- `longitude` (number): Alias for lon — either name works

### `rank_sites` (~544 tokens)

Rank Sites

Rank candidate sites you pass in (each with lat/lng and metric fields) under hard constraints and weighted objectives, with a normalized score per site.

Input parameters:

- `absolute` (boolean): false (default) = min-max normalize within THIS batch (best-in-set, NOT stable across runs). true = score on a FIXED 0-100 scale for CROSS-RUN-STABLE, auditable scores — use ONLY when the objective f…
- `candidates`: Array of candidate objects. PREFERRED: {candidate_id: "cand_…", <your metric fields>} using ids from get_refined_queue — frozen coordinates/capacity/fiber_km load from the mint (zero transcription dr…
- `constraints`: Hard filters {field: {min?, max?}} — a candidate missing a constrained field is dropped (fail-closed). e.g. {"risk_resilience": {"min": 70}, "estimated_ttp_months": {"max": 34}}
- `objectives`: Weighted objectives {field: signedWeight} — +weight maximizes, -weight minimizes. e.g. {"water_stress": -0.6, "fiber_km": -0.4}. Omit with shortlist_name to reuse the shortlist's saved objectives; re…
- `percentile` (boolean): true = score each objective as its PERCENTILE against the viable-site POPULATION ("better than X% of viable sites") — the strongest cross-run + cross-region comparability. Works for fields with a mai…
- `require_complete` (boolean): true = DROP any candidate missing one or more of your (validated) objectives — dropped candidates are DECLARED in excluded_incomplete, never silent. Default false keeps incomplete candidates ranked o…
- `shortlist_name` (string)
- `top_k` (integer): How many top-ranked sites to return (1-50, default 3)

### `discover_tools` (~74 tokens)

Discover Tools

List DC Hub tools grouped by family (facility, market, grid and power, gas, site, fiber, deals and news), optionally filtered by a query.

Input parameters:

- `query` (string): Optional keyword to filter families/tools, e.g. "site selection", "grid queue", "fiber", "deals", "market"

### `plan_query` (~122 tokens)

Plan Query

Show the step-by-step tool plan DC Hub would run for a question, without running it.

Input parameters:

- `context`: Optional structured hints: {lat, lon, iso, market, capacity_mw, candidate_id, state (2-letter), since} — sharpens args_hint values and routing (e.g. lat/lon boosts the site-analysis route)
- `intent` (string, required): Natural-language description of what you are trying to find out, e.g. "rank markets for a 200MW AI campus" or "how much power is available in ERCOT"

### `get_grid_data` (~118 tokens)

Live Grid Data

Get real-time grid data for one of the 7 US ISOs from EIA hourly data: fuel mix, demand and the 24-hour demand curve.

Input parameters:

- `iso` (string): ISO/RTO grid region (required): ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE
- `metric` (string): Optional metric focus, e.g. fuel_mix, demand, demand_curve
- `period` (string): Optional time window for the metric, e.g. 24h

### `get_changes` (~90 tokens)

Get Changes

List what changed in DC Hub since a timestamp: DCPI market movers, newly found facilities, new deals and news.

Input parameters:

- `limit` (integer): Max results to return (1-500; default varies by tool)
- `since` (string): Return changes since this ISO-8601 timestamp (YYYY-MM-DD or full datetime) or shorthand "24h"/"7d"; default 24h

### `get_facility_risk_delta` (~112 tokens)

Get Facility Risk Delta

Show how a facility's market DCPI health changed over a time window, with direction (improving, worsening or flat).

Input parameters:

- `facility_id` (string): A DC Hub facility id or canonical slug to resolve the market context
- `market` (string): Alternatively, a market name or slug (e.g. "northern-virginia")
- `since` (string): Look-back window, e.g. "7d" or "30d" (default 7d)

### `find_sites` (~391 tokens)

Find Sites

Find candidate data-center sites in a state or around a point, filtered by substation voltage and distance to gas and fiber.

Input parameters:

- `cluster_km` (number): Collapse anchors within this many km into one candidate area (default 8, max 100). Raise it for broader coverage, lower it for denser results
- `exclude_moratorium` (boolean): true = drop candidates in a state with a published data-center moratorium. STATE grain, not jurisdiction grain
- `lat` (number): Latitude of a search centre, e.g. 39.04 — use with lon (+ radius_km) instead of state
- `latitude` (number): Alias for lat — either name works
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `lng` (number): Alias for lon — either name works
- `lon` (number): Longitude of a search centre, e.g. -77.48
- `longitude` (number): Alias for lon — either name works
- `max_fiber_km` (number): Drop candidates farther than this from the nearest fiber route (CHORD approximation — see fiber_distance_basis). Applied ONLY if the fiber layer answers
- `max_gas_km` (number): Drop candidates farther than this from the nearest gas pipeline. Applied ONLY if the gas layer answers — check constraint_coverage
- `min_voltage_kv` (number): Only anchor on substations at or above this voltage in kV (default 115). 230+ for hyperscale, 500 for the largest campuses
- `radius_km` (number): Search radius in km around lat/lon (default 80, clamped 5-400); ignored in state mode
- `state` (string): 2-letter US state to search, e.g. OH — required unless you pass lat + lon

### `analyze_site` (~467 tokens)

Analyze Site

Score one site (lat/lon, a candidate_id from get_refined_queue, or a market name) for data-center suitability: 0-100 overall score with power, gas, fiber, market and risk sub-scores and the nearby infrastructure behind them. Needs a DC Hub account with site-analysis access; without one it returns only a notice.

Input parameters:

- `candidate_id` (string): PREFERRED for queue survivors: a cand_… id from get_refined_queue — coordinates come from the FROZEN mint (lat/lon args are ignored; zero transcription drift; expired ids fail closed with candidate_e…
- `capacity_mw` (number): Target power load for the build in megawatts (MW), e.g. 100 (typical 50-500)
- `include_fiber` (boolean): Include fiber-connectivity analysis (default true)
- `include_grid` (boolean): Include grid-headroom / substation analysis (default true)
- `include_risk` (boolean): Include water/drought/climate risk analysis (default true)
- `lat` (number): Site latitude in decimal degrees (-90 to 90; required unless candidate_id or location given), e.g. 33.45
- `latitude` (number): Alias for lat — either name works
- `lng` (number): Alias for lon — either name works
- `location` (string): Market NAME or metro slug instead of coordinates, e.g. "ashburn", "northern-virginia", "dallas". Resolved to that market's PUBLISHED CENTROID through the DCPI market row, and the answer carries a res…
- `lon` (number): Site longitude in decimal degrees (-180 to 180; required unless candidate_id or location given), e.g. -112.07
- `longitude` (number): Alias for lon — either name works
- `state` (string): US state abbreviation (optional) — improves the tax-incentive lookup, e.g. AZ

### `compare_sites` (~172 tokens)

Compare Sites

Compare 2-4 candidate sites (semicolon-separated "lat,lon" pairs) side by side on the analyze_site scores, and name the highest-scoring one with the reason. Needs a DC Hub account with site-analysis access; without one it returns only a notice.

Input parameters:

- `capacity_mw` (number): Target power load for the build in megawatts (MW), e.g. 50 (typical 50-500)
- `locations` (string): Semicolon-separated list of 2-4 "lat,lon" pairs to compare, e.g. "33.45,-112.07;39.04,-77.48"
- `sites`: Alternative to locations: an array of {lat, lon} (or {lat, lng}) objects, 2-4 sites

### `get_composite_site_score` (~196 tokens)

Get Composite Site Score

Score one lat/lon 0-100 using only measured factors (power and grid, fiber, natural-hazard risk, water), with a BUILD/CAUTION/AVOID verdict and a coverage map of which factors were measured. Needs a DC Hub account with site-analysis access; without one it returns only a notice.

Input parameters:

- `lat` (number): Site latitude in decimal degrees (-90 to 90, required), e.g. 33.45
- `latitude` (number): Alias for lat — either name works
- `lng` (number): Alias for lon — either name works
- `lon` (number): Site longitude in decimal degrees (-180 to 180, required), e.g. -112.07
- `longitude` (number): Alias for lon — either name works
- `state` (string): US state abbreviation (optional) — improves water/context lookups, e.g. AZ

### `generate_site_analysis` (~299 tokens)

Generate Site Analysis

Build a multi-page Site Analysis PDF for one lat/lon (power and transmission, gas, water, air permitting, fiber, latency, market, tax) and return its survey data and a download link valid for about 7 days. Needs a DC Hub account with site-analysis access; without one it returns only a notice.

Input parameters:

- `capacity_mw` (number): Target power load for the build in megawatts (MW), e.g. 150 (typical 50-500)
- `lat` (number): Site latitude in decimal degrees (-90 to 90, required), e.g. 37.694
- `latency_target` (string): Optional metro to measure latency against; default = nearest real carrier hotel
- `latitude` (number): Alias for lat — either name works
- `lng` (number): Alias for lon — either name works
- `lon` (number): Site longitude in decimal degrees (-180 to 180, required), e.g. -88.65
- `longitude` (number): Alias for lon — either name works
- `prepared_by` (string): Your firm name that brands the report; defaults to DC Hub, e.g. "Martone Advisors"
- `prepared_for` (string): Client name printed on the report cover, e.g. "TON Infrastructure"
- `use_case` (string): Optional workload descriptor to tailor the report, e.g. "AI training campus"

### `get_disaster_risk` (~141 tokens)

Get Disaster Risk

Get natural-hazard risk for a US lat/lon from the FEMA National Risk Index: flood, wildfire, hurricane, earthquake, heat, drought, tornado and more.

Input parameters:

- `lat` (number): Site latitude in decimal degrees (-90 to 90, required), e.g. 33.45
- `latitude` (number): Alias for lat — either name works
- `lng` (number): Alias for lon — either name works
- `lon` (number): Site longitude in decimal degrees (-180 to 180, required), e.g. -112.07
- `longitude` (number): Alias for lon — either name works

### `get_climate_intel` (~168 tokens)

Get Climate Intel

Get seismic design values (USGS ASCE 7) and climate normals (NOAA) for a lat/lon, such as cooling degree-days and temperature extremes.

Input parameters:

- `lat` (number): Site latitude in decimal degrees (-90 to 90, required), e.g. 33.45
- `latitude` (number): Alias for lat — either name works
- `lng` (number): Alias for lon — either name works
- `lon` (number): Site longitude in decimal degrees (-180 to 180, required), e.g. -112.07
- `longitude` (number): Alias for lon — either name works
- `radius_km` (number): Max distance (km) to snap to the nearest NOAA station (optional, default 25)

### `get_infrastructure` (~226 tokens)

Nearby Infrastructure

List infrastructure near a location: substations, transmission lines, gas pipelines and power plants, with distance and capacity.

Input parameters:

- `lat` (number): Center latitude in decimal degrees (-90 to 90, required), e.g. 33.45
- `latitude` (number): Alias for lat — either name works
- `layer` (string): Optional single asset layer to return, e.g. substations, transmission, pipelines, power_plants
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `lng` (number): Alias for lon — either name works
- `lon` (number): Center longitude in decimal degrees (-180 to 180, required), e.g. -112.07
- `longitude` (number): Alias for lon — either name works
- `min_voltage_kv` (number): Only include transmission/substations at or above this voltage in kV, e.g. 69
- `radius_km` (number): Search radius in kilometers around the point, e.g. 25

### `get_fiber_intel` (~175 tokens)

Fiber Intelligence

Get fiber route intelligence by carrier, route type or market: long-haul and metro routes and dark-fiber availability.

Input parameters:

- `carrier` (string): Fiber carrier to filter on, e.g. Zayo, Lumen, Cogent, "Crown Castle", Windstream, GTT, Uniti; omit for all carriers
- `include_sources` (boolean): Include upstream data-source/provenance metadata in the response
- `market` (string): Metro name or slug (e.g. "dallas", "ashburn", "northern-virginia") — returns only routes touching that metro (either endpoint within ~1.2°). Great with route_type=longhaul.
- `route_type` (string): Route class: "metro", "longhaul", "dark", or "ix"

### `get_fiber_readiness` (~162 tokens)

Get Fiber Readiness

Assess fiber readiness for a lat/lon: distance to a carrier-served facility, number of reachable carriers, and single-carrier risk.

Input parameters:

- `lat` (number): Site latitude in decimal degrees (-90 to 90, required), e.g. 39.04
- `latitude` (number): Alias for lat — either name works
- `lng` (number): Alias for lon — either name works
- `lon` (number): Site longitude in decimal degrees (-180 to 180, required), e.g. -77.48
- `longitude` (number): Alias for lon — either name works
- `radius_km` (number): Search radius in km for reachable fiber carriers (default 50, range 5-200)

### `get_subsea_cables` (~170 tokens)

Get Subsea Cables

List subsea cable landing points near a coordinate, or the catalogue of tracked subsea cables.

Input parameters:

- `lat` (number): Latitude of the site, e.g. 36.85 — with lon, returns landing points near it; omit both for the cable catalogue
- `latitude` (number): Alias for lat — either name works
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `lng` (number): Alias for lon — either name works
- `lon` (number): Longitude of the site, e.g. -75.98
- `longitude` (number): Alias for lon — either name works
- `radius_km` (number): Search radius in km around lat/lon for landing points (default 200)

### `get_peering_intel` (~156 tokens)

Get Peering Intel

Get internet-exchange and peering density near a lat/lon from PeeringDB, or the top peering facilities overall.

Input parameters:

- `lat` (number): Latitude of the site, e.g. 39.04 — with lon, returns the peering profile around it; omit both for the IXP directory
- `latitude` (number): Alias for lat — either name works
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `lng` (number): Alias for lon — either name works
- `lon` (number): Longitude of the site, e.g. -77.48
- `longitude` (number): Alias for lon — either name works

### `get_metro_fiber` (~99 tokens)

Get Metro Fiber

Get the fiber profile of a US data-center metro: carriers, route miles, on-net buildings, fiber-density score, exchanges and carrier hotels.

Input parameters:

- `market` (string): Optional metro name or slug for a single-market deep dive (carrier-by-carrier + dark fiber), e.g. "Dallas-Fort Worth", "dallas", "Northern Virginia", "ashburn". Omit to list every tracked metro ranke…

### `get_energy_prices` (~106 tokens)

Energy Prices

Get energy prices by US state or ISO: retail electricity, wholesale and natural gas.

Input parameters:

- `data_type` (string): Optional price type focus, e.g. retail, wholesale, gas
- `iso` (string): ISO/RTO grid region (required for ISO pricing): ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE
- `state` (string): US state abbreviation for state-level pricing context, e.g. TX

### `get_renewable_energy` (~170 tokens)

Renewable Energy

Get renewable energy data for a US state or location: renewable generation mix and resource inputs for PPA sizing.

Input parameters:

- `energy_type` (string): Renewable type: "solar", "wind", or "combined"; omit for all
- `lat` (number): Optional latitude in decimal degrees (-90 to 90) to find nearest projects within 50mi
- `latitude` (number): Alias for lat — either name works
- `lng` (number): Alias for lon — either name works
- `lon` (number): Optional longitude in decimal degrees (-180 to 180) to find nearest projects within 50mi
- `longitude` (number): Alias for lon — either name works
- `state` (string): US state abbreviation, e.g. TX, VA, AZ

### `get_tax_incentives` (~58 tokens)

Tax Incentives

List data-center tax incentive programs for a US state: sales-tax exemptions, property-tax abatements and other programs, with thresholds.

Input parameters:

- `state` (string): US state abbreviation (required), e.g. VA, TX, AZ

### `get_water_risk` (~247 tokens)

Water Risk

Get water-stress risk for a US lat/lon or state, for cooling-water planning.

Input parameters:

- `lat` (number): Site latitude in decimal degrees (-90 to 90) for the most precise water-risk read, e.g. 33.45
- `latitude` (number): Alias for lat — either name works
- `lng` (number): Alias for lon — either name works
- `location` (string): Market NAME or metro slug instead of coordinates, e.g. "phoenix", "northern-virginia", "dallas". Resolved to that market's PUBLISHED CENTROID through the DCPI market row, and the answer carries a res…
- `lon` (number): Site longitude in decimal degrees (-180 to 180), e.g. -112.07
- `longitude` (number): Alias for lon — either name works
- `state` (string): US state abbreviation as an alternative to lat/lon, e.g. AZ

### `get_grid_intelligence` (~273 tokens)

Grid Intelligence

Get a grid brief for one US ISO: demand, fuel mix, excess-power and constraint score bands, interconnection queue and time to power.

Input parameters:

- `iso` (string): Alias for region_id — the ISO/RTO or balancing-authority code
- `market` (string): Market NAME or metro slug instead of a grid code, e.g. "Ashburn", "northern-virginia", "dallas". Resolved to its ISO through the published DCPI market row before the brief is built; the answer carrie…
- `region` (string): Alias for region_id — the ISO/RTO or balancing-authority code
- `region_id` (string): Grid region (required): one of the 7 US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE), an EIA balancing-authority code (e.g. SOCO, DUK, AZPS, TVA), or the PJM Dominion zone region_id="PJM-DOM" f…

### `get_backup_status` (~31 tokens)

Platform Health

Get per-feed freshness for DC Hub's data ingest: health, record count and refresh interval for each feed.

### `summarize_for_citation` (~220 tokens)

Citation Block

Build an attribution line for a DC Hub figure you are about to quote, with the licence that applies to its data layer.

Input parameters:

- `as_of` (string): The as_of you read off the cited response (provenance.as_of). Omit it and the line says RETRIEVED instead of claiming a data date.
- `completeness` (string): The completeness flag from the cited response, if it carried one
- `layer` (string): Which layer the figure came from: dcpi | grid_analysis | facility_inventory | physical_infrastructure | deals | other. Decides the licence line; omit and you get the scoped statement rather than a gr…
- `subject` (string): What you are citing, in the words you will show the human, e.g. "Ashburn DCPI verdict" or "ERCOT interconnection queue depth"
- `url` (string): The profile_url or dcpi_url from the cited row. Must be a dchub.cloud URL; anything else is dropped and named in `omitted`.

### `rank_markets` (~234 tokens)

Rank Markets

Rank data-center markets by a chosen criterion, optionally within a region or above a minimum capacity.

Input parameters:

- `criteria` (string): Ranking criterion: "cheapest_power", "most_capacity", "most_operators", "fastest_growing", "best_overall" (default), or "ai_ready" (DCPI buildability — where new AI load can land, for AI-campus sitin…
- `fields`: Return ONLY these row fields (array or comma string) — a token diet.
- `limit` (integer): Number of markets to return, 1-50 (default 10)
- `min_capacity_mw` (number): Minimum existing capacity filter in megawatts (MW), e.g. 100
- `projection` (string): Named field preset, cheaper to send than a field list: market_summary (ranking rows), siting_summary (site/point rows), identity_only (ids + names).
- `region` (string): Region scope: "global", "us" (default), "canada", "eu", "apac", or "americas"

### `find_alternatives` (~153 tokens)

Find Alternative Facilities

Find facilities similar to a given facility nearby, with similarity scores and key differences.

Input parameters:

- `exclude_operator` (boolean): If true, exclude facilities from the same operator as the seed
- `facility_id` (string, required): The seed facility id/slug (required) to find alternatives to, from a prior search result — there is no `name` param; an undeclared key is silently stripped
- `limit` (integer): Max results to return (1-500; default varies by tool)
- `match_on` (string): Optional similarity dimension to weight, e.g. capacity, operator, fiber, market
- `radius_km` (number): Search radius in km for candidate alternatives around the seed facility

### `score_facility` (~91 tokens)

Score Facility

Score one existing facility 0-100 across power, fiber, water, climate risk, tax environment, talent pool and expansion room.

Input parameters:

- `facility_id` (string, required): The facility id/slug to score (required), from a prior search_facilities result
- `weighting` (string): Scoring profile: "balanced" (default), "power_priority", "risk_priority", or "expansion_priority"

### `ai_capacity_index` (~82 tokens)

AI Capacity Index

Rank data-center markets by where large AI training capacity could land in the next 30, 60 or 90 days, with facility and operator counts.

Input parameters:

- `horizon` (integer): Deployment horizon in days: 30, 60, or 90 (default 90)
- `limit` (integer): Number of top markets to return (default 20)

### `hyperscaler_deals` (~48 tokens)

Hyperscaler Deal Tracker

List recent hyperscaler and AI infrastructure deals and announcements, with amounts and MW where stated.

Input parameters:

- `limit` (integer): Number of recent AI-capex deals to return (default 20)

### `site_selection_canvas` (~298 tokens)

Site Selection Canvas

Shortlist US markets for a capacity target, geography and deadline, ranked by DCPI verdict, excess-power headroom and time to power.

Input parameters:

- `capacity_mw` (integer): Target power load for the build in megawatts (MW), 1-5000, e.g. 100
- `iso` (string): ISO/RTO code, e.g. ERCOT or PJM — alias for `region`. Use either; `region` wins if both are sent.
- `limit` (integer): Number of shortlist markets to return
- `max_months` (integer): Maximum acceptable time-to-power in months, 1-120, e.g. 24
- `region` (string): Geography scope: a US state code like TX, an ISO like ERCOT, or a region like us/apac. `state` and `iso` are accepted as aliases for this same filter.
- `state` (string): US state code, e.g. OH — alias for `region`. Use either; `region` wins if both are sent.
- `verdict` (string): Optional DCPI verdict filter: BUILD, CAUTION, or AVOID — or ALL to see every scored market in the geography. Defaults to BUILD,CAUTION, so a geography whose markets are all AVOID returns matched:0 pl…

### `grid_transition_radar` (~81 tokens)

Grid Transition Radar

List US markets and ISOs with the strongest near-term signal of new grid headroom for large loads, with an ISO rollup.

Input parameters:

- `limit` (integer): Number of emerging markets to return
- `max_months` (integer): Maximum acceptable time-to-power in months for the emergence signal, 1-120, e.g. 24

### `deal_autopsy` (~98 tokens)

Deal Autopsy

List recent data-center deals with the DCPI verdict and time to power of each deal's market.

Input parameters:

- `comparables` (string): Comparables detail: "none" (default — count only, cheapest), "summary" (top-2 grounding signals), or "full" (the complete cited set). Escalate only for deals you're drilling into.
- `limit` (integer): Number of recent deals to return (default ~15)

### `get_permitting_intel` (~92 tokens)

Permitting & Moratorium Intel

List data-center permitting and moratorium records by jurisdiction: moratoriums, zoning restrictions, tax changes and utility pauses, each stage-tagged with a source.

Input parameters:

- `class` (string): Record class: "moratorium" | "zoning" | "tax" | "utility_pause" (optional)
- `state` (string): US state filter, e.g. NY or MN (optional)

### `simulate_scenario` (~222 tokens)

Market Scenario Simulator

Re-score DC Hub power markets under what-if changes you set (power price, time to power, queue wait, reserve margin, curtailment) and show how rankings move.

Input parameters:

- `avg_kwh_cents_pct` (number): Power price % change, e.g. 30 for +30% or -20 for -20%
- `curtailment_pct_delta` (number): Percentage POINTS added/removed from curtailment
- `market` (string): Score ONE market by slug (optional), e.g. abilene — slugs from rank_markets
- `queue_wait_months_delta` (number): Months added/removed from interconnection queue wait
- `reserve_margin_pct_delta` (number): Percentage POINTS added/removed from reserve margin, e.g. -5
- `time_to_power_months_delta` (number): Months added (+) or removed (-) from time-to-power, e.g. 12
- `top_n` (integer): Markets to return, ranked by |score delta| (default 10)

### `plan_fiber_leadin` (~184 tokens)

Plan Fiber Leadin

Plan diverse road-following fiber lead-in routes from a site to a carrier hotel or POP, with distances, indicative build cost and shared-corridor points.

Input parameters:

- `bore_m` (integer): River/rail bore length in metres to add to the route, 0-100000 (optional)
- `fibre` (string): Fibre count spec for cost estimate: "720F" or "1440F"
- `from` (string, required): Origin site as "lat,lng" OR a street address, e.g. "250 Paringa Road, Murarrie QLD"
- `n` (integer): Number of diverse routes to plan, 1-6 (default 4)
- `to` (string, required): Destination carrier hotel/POP as "lat,lng" OR an address, e.g. "20 Wharf Street, Brisbane City QLD"

### `cluster_sites_by_latency` (~257 tokens)

Cluster Sites By Latency

Group 2-8 sites into low-latency clusters using physics-bound round-trip time floors between each pair.

Input parameters:

- `candidate_ids`: Array (or comma-separated string) of candidate_id values from get_refined_queue — each resolves to its FROZEN mint coordinates (zero transcription drift); expired/unknown are dropped and declared in…
- `max_latency_us` (number): Round-trip latency budget in microseconds (default 1000 µs = 1 ms; sync replication is typically 1000-2000 µs)
- `min_confidence` (string): Minimum evidence tier a pair must meet to count as viable: "published" | "tracked" | "inferred" (default inferred = include all)
- `sites` (string): Semicolon-separated "lat,lon" pairs, 2-8 sites (same format as compare_sites locations); optional per-site labels via "lat,lon:label", e.g. "39.04,-77.48:ashburn;39.29,-76.61:baltimore". cand_… token…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-claude#diagnostics

## Score history

- 2026-10-16: 82
- 2026-10-15: 81
- 2026-10-14: 81
- 2026-10-13: 80
- 2026-10-12: 80
- 2026-10-11: 80
- 2026-10-04: 73
- 2026-10-03: 72
- 2026-10-02: 72
- 2026-10-01: 71
- 2026-09-30: 71
- 2026-09-29: 71

## Common questions

### What is the DC Hub — Data Center Site Selection & Colocation… MCP server?

DC Hub — Data Center Site Selection & Colocation… is an MCP server listed in the public MCP registry as cloud.dchub/mcp-server. DCPI grid-power scores for 300+ markets, plus capacity to buy or lease; query and cite. This page covers its hosted endpoint (https://dchub.cloud/mcp/claude).

### Is the DC Hub — Data Center Site Selection & Colocation… MCP server safe to use?

DC Hub — Data Center Site Selection & Colocation… scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DC Hub — Data Center Site Selection & Colocation… MCP server expose?

DC Hub — Data Center Site Selection & Colocation… exposes 67 tools: search, fetch, execute_plan, search_facilities, get_facility, and 62 more. Their descriptions and schemas cost roughly 12,966 tokens of context every time the server is loaded.

### Does the DC Hub — Data Center Site Selection & Colocation… MCP server require authentication?

No. We connected to DC Hub — Data Center Site Selection & Colocation… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DC Hub — Data Center Site Selection & Colocation… MCP server still maintained?

DC Hub — Data Center Site Selection & Colocation… is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://dchub.cloud/mcp/claude
- Repository: https://github.com/azmartone67/dchub-mcp-server
- Website: https://dchub.cloud/
- Changelog RSS feed: https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-claude.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-claude.json
- HTML version of this page: https://verifymcp.io/servers/cloud-dchub-mcp-server/mcp-claude