DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber
REMOTE · DCHUB.CLOUD · 3 COMPONENTS
DCPI grid-power scores for 300+ markets, plus capacity to buy or lease; query and cite.
Available components
Last scanned (21 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Cloud Infrastructure
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management55
- Stability check failed: schema churn in the 17 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 68 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 14 Oct 26 +1
- Server version: 2.12.36 → 2.12.37 functional
- 12 Oct 26 0
- Server version: 2.12.34 → 2.12.36 functional
- 11 Oct 26 +7
- Stability: 0.17 → fail ▼ security
- Tool “research_task” was removed ▼ security
- HSTS header: fail → pass ▲ security
- DNSSEC: fail → pass ▲ security
- Server version: 2.12.30 → 2.12.34 functional
- 4 Oct 26 +1
- 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 functional
- “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” cosmetic
- 2 Oct 26 +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.
- 30 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Sept 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://dchub.cloud/mcp/claude
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dchub.cloud | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7cadce02bd1e9275139023d74dbd768c |
| SANs: dchub.cloud | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of dchub.cloud. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | present | 7041 | 13 | Verified |
| dchub.cloud. | present | 2371 | 13 | Verified |
| dchub.cloud. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dchub.cloud/mcp/claude | Verified | 200 | |
| http (plaintext) | http://dchub.cloud/mcp/claude | HTTPS enforced | 301 | https://dchub.cloud/mcp/claude |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
grid_transition_radar Grid Transition Radar ~81
List US markets and ISOs with the strongest near-term signal of new grid headroom for large loads, with an ISO rollup.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
hyperscaler_deals Hyperscaler Deal Tracker ~48
List recent hyperscaler and AI infrastructure deals and announcements, with amounts and MW where stated.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of recent AI-capex deals to return (default 20) |
No output schema declared.
No examples provided.
list_transactions M&A Transactions ~255
List data-center M&A and capital transactions since 2019. Filter by buyer, seller, deal value, deal type, date range or region.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
plan_fiber_leadin Plan Fiber Leadin ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Destination carrier hotel/POP as "lat,lng" OR an address, e.g. "20 Wharf Street, Brisbane City QLD" |
No output schema declared.
No examples provided.
plan_query Plan Query ~122
Show the step-by-step tool plan DC Hub would run for a question, without running it.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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" |
No output schema declared.
No examples provided.
predict_market_trajectory Predict Market Trajectory ~106
Project a market's DCPI excess-power and constraint scores 1-8 quarters ahead from its daily history, with confidence bands.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon_quarters | integer | – | Forecast horizon in quarters (1-8, default 4); 2 = ~6 months ahead |
| market_slug | string | yes | Market slug (metro), e.g. dallas, phoenix, northern-virginia — valid slugs come from rank_markets / get_market_dcpi_rank |
No output schema declared.
No examples provided.
rank_markets Rank Markets ~234
Rank data-center markets by a chosen criterion, optionally within a region or above a minimum capacity.
| Name | Type | Req | Description |
|---|---|---|---|
| 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" |
No output schema declared.
No examples provided.
rank_sites Rank Sites ~544
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
score_facility Score Facility ~91
Score one existing facility 0-100 across power, fiber, water, climate risk, tax environment, talent pool and expansion room.
| Name | Type | Req | Description |
|---|---|---|---|
| facility_id | string | yes | 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" |
No output schema declared.
No examples provided.
search Search ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text query, e.g. "data centers in Northern Virginia" or "Ashburn hyperscale power" |
No output schema declared.
No examples provided.
search_facilities Search Facilities ~261
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
search_intelligence Search Intelligence ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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" |
No output schema declared.
No examples provided.
semantic_search Semantic Search ~135
Search DC Hub news, M&A deals, facilities and market analyses by meaning rather than keywords. Returns ranked records with source fields for citation.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
simulate_scenario Market Scenario Simulator ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
site_selection_canvas Site Selection Canvas ~298
Shortlist US markets for a capacity target, geography and deadline, ranked by DCPI verdict, excess-power headroom and time to power.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
source_capacity Source Capacity ~754
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
summarize_for_citation Citation Block ~220
Build an attribution line for a DC Hub figure you are about to quote, with the licence that applies to its data layer.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
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.
remote · dchub.cloud
claude mcp add --transport http cloud-dchub-mcp-server 'https://dchub.cloud/mcp/claude'
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.