get_grid_scoreboardLABSCO SUMMARY
Time-to-power is the question, and the queue data is why it can be answered.
Facility directories are common; what is not is pairing them with interconnection-queue depth and live ISO telemetry, because that is what turns 'is there a site here' into 'when could it actually energise'. The per-ISO verdicts are the project's own scoring, not raw filings, so the methodology resource is worth reading before quoting one. Note also that queue depth for large loads exists only where the ISO publishes it, which is a smaller set than the map suggests.
What it is
A hosted MCP server for data-centre and power-grid intelligence. It combines a facility database, the physical infrastructure around it and live grid telemetry into one surface, aimed at site selection, energy analysis and market research — the questions where the answer is normally spread across a regulator's filings, an ISO's dashboard and a PDF.
What you get
- 18,800+ data centre facilities across 170+ countries with operator, capacity, location and fiber connectivity, and 126,000+ substations with voltage class and capacity estimates
- Live load and generation mix across the 7 US ISOs and 40+ EIA balancing authorities, plus Great Britain, 24 European ENTSO-E zones, Taiwan and Australia, refreshed roughly every 5 min
- Interconnection-queue snapshots with per-ISO BUILD, CAUTION or AVOID verdicts, including live large-load queue depth where the ISO publishes it
- Transmission lines, gas pipelines and fiber routes; NEPA filings for upcoming federal energy and data centre projects; tax incentives by state with eligibility
- 1,900+ tracked M&A transactions, an AI capacity index and a hyperscaler deal tracker; 300+ markets scored daily with the same BUILD/CAUTION/AVOID verdicts
- 82 MCP tools by the README's count, across facility search, market intel, grid and interconnection, renewables, site analysis, deals, fiber routing and infrastructure
- 13 guided prompts that appear as slash commands in the client —
/dchub:analyze-site,/dchub:pick-a-market,/dchub:power-availability,/dchub:site-report,/dchub:compare-markets,/dchub:fiber-plan,/dchub:grid_and_queue,/dchub:water_risk,/dchub:hyperscaler_activity,/dchub:whats_changedamong them - Citable resources for the methodology and coverage behind an answer —
dchub://about,dchub://methodology,dchub://data-sources,dchub://coverage
Requirements
Nothing to start: add https://dchub.cloud/mcp over HTTP transport and anonymous access allows 5 calls/day with no key at all. An email signup gives a free key with 50 calls/day, and paid tiers run from Starter at $9/mo for 200 calls/day up to enterprise volumes. Data sources are named — EIA hourly RTO data, the HIFLD substation database, OpenStreetMap, PeeringDB, regulations.gov NEPA filings, USGS, EPA eGRID and FEMA NRI. The transport layer is open source; the data and business logic are hosted.
Setup effort
One command — npx -y @smithery/cli install @azmartone67/dchub --client claude
USE CASES
Working out where a given load can actually land
Ask for power availability and time-to-power in an ISO, with the interconnection queue read alongside the capacity numbers.
Shortlisting markets for a build
Rank markets by the composite index, then take the finalists through a per-market verdict and a grid reality check.
Assessing one specific site
Run a full buildability read on an address or coordinate — power, gas, fiber, market and hazard exposure in one brief.
Tracking what the hyperscalers are doing
Pull recent deals and forward pipeline to see who is buying and building in a region before you commit to it.
10 tools
Listed in project docs. Your client may show a different list.
rank_marketsget_grid_intelligenceget_interconnection_queueget_composite_site_scoreget_disaster_riskget_climate_intelhyperscaler_dealslist_transactionsdeal_autopsyBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
npx
Smithery
npx -y @smithery/cli install @azmartone67/dchub --client claudeHosted endpoint
https://dchub.cloud/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Claude Desktop
In Claude Desktop, go to Customize → Connectors, click + and then Add custom connector.
Enter https://dchub.cloud/mcp as the remote MCP server URL and click Add.
Claude Code
claude mcp add dchub --transport http https://dchub.cloud/mcpCline
{
"mcpServers": {
"dchub": {
"url": "https://dchub.cloud/mcp",
"type": "streamableHttp"
}
}
}Continue
name: DC Hub
version: 0.0.1
schema: v1
mcpServers:
- name: dchub
type: streamable-http
url: https://dchub.cloud/mcpSave this as a .yaml file in a .continue/mcpServers folder at the top level of your workspace. MCP tools work in Continue's agent mode.
VS Code
Name: dchub
Type: http
URL: https://dchub.cloud/mcp