DC Hub
v2.12.59Orchestration layer for data center and energy intelligence. Start with execute_plan.
Endpoint health
online- Last checked
- 11/20/2026, 5:18:13 AM
- Latency
- 181 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:cloud.dchub%2Fmcp-server
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"cloud.dchub/mcp-server": {
"url": "https://dchub.cloud/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Analyze Parcel
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 its HOSTED parcel-boundary layer (free county/state GIS polygons, covering a set of priority data-center counties in VA, IL, TX, OH, UT, OR, IA and WY; a point outside it returns parcel_not_covered with the analyze_site preview + the coverage list, never a guess). Returns _entity=parcel_analysis: geodesic total_acres, a per-member acreage breakdown, a contiguous flag, representative_point = the centroid of the LARGEST-area member (never the multi-part geometric center, which can land off-parcel on a highway median or river and poison every point-keyed read), and hosted_parcel {parcel_id, county, state, acres_per_source} when the polygon came from the hosted layer. Also returns a site_evaluation_handoff to pipe into analyze_site + get_water_risk at that anchor. For multi-step data center or energy questions, start with execute_plan.
Schema valid · SHA-256 f1551b0bb76a…
View input schema
{ "type": "object", "properties": { "geometry": { "description": "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 hosted parcel containing lat/lon instead" }, "lat": { "description": "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", "type": "number" }, "lon": { "description": "Longitude of a point ON the parcel (used with lat when geometry is omitted)", "type": "number" }, "latitude": { "description": "Alias for lat — either name works", "type": "number" }, "lng": { "description": "Alias for lon — either name works", "type": "number" }, "longitude": { "description": "Alias for lon — either name works", "type": "number" }, "capacity_mw": { "description": "Optional target load in MW to pass through into the site_evaluation_handoff", "type": "number" } } }
Connections
streamable-http
https://dchub.cloud/mcp