# DC Hub Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## DC Hub

Live data center, power, grid, fiber and deal data for AI agents and site selection.

- Record: https://musedirectory.ai/connector/dc-hub
- Category: Research & Data
- Developer: DC Hub (https://dchub.cloud)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 313ms, checked 2026-10-29T12:15:51Z
- Endpoint: https://dchub.cloud/mcp
- Auth: No account needed; Pricing: freemium
- Screening: Screened, no issues found (2026-10-28T12:00:30Z)
- Source: Submitted by its builder and screened before listing

DC Hub is the live data layer for data-center site selection. Its DCPI is a daily score of where data centers can get grid power, across 300+ markets. 94 MCP tools at https://dchub.cloud/mcp plus a REST API at https://dchub.cloud/api/v1. Free previews need no key; OAuth or an API key unlocks full depth.

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use DC Hub to help me. It is a free service with an MCP server at https://dchub.cloud/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- execute_plan: Use this when a data center question spans several topics: one-call planner over megawatts and power density, grid headroom and power availability, interconnection queues, substations and transmission, site selection and buildable capacity, colocation and wholesale data-center ma
- claim_free_key: Use this when the user wants more DC Hub data center data than keyless allows, or asks for a key; no key is needed to start. Mints a free key and returns it plus connect_url, a connector URL with the key embedded (the only thing hosted chat clients keep). Free key: previews plus 
- search: Use this when a Deep Research or ChatGPT-connector client needs a data center facility search (search/fetch format). Returns a list of matching data-center facilities as {id, title, url}; pass an id to the `fetch` tool for the record, or open the url to cite the live facility pag
- fetch: Use this when you have an id from `search` and need that data center facility record (search/fetch format). Returns {id, title, text, url, metadata} — a citable public summary of one data-center facility (name, operator, location, status, market). For full structured specs (capac
- search_facilities: Use this when the user asks which data centers exist, or who operates in a city, state or country; filters: country, state, city, operator, MW range, tier or text. Returns name, operator, location, market, status and MW where disclosed; each row is flagged verified or unverified_
- get_facility: Use this when the user asks about one data center facility: name, operator, address, lat/lon, power capacity (MW total/used), cooling type, fiber providers (count + carrier list), commissioning year, status, the DCPI verdict for its market, and peer facilities nearby. Answers "wh
- get_market_intel: Use this when the user asks about a data-center market (metro supply, operators, pipeline, pricing): facility count, tracked MW, status mix, top providers, recent facilities or lease pricing. Pass market as a slug (e.g. northern-virginia). Returns stats, by_status, top_providers,
- get_market_dcpi_rank: Use this when the user asks where a data center can get grid power, how fast, or whether a market is a BUILD, CAUTION or AVOID (e.g. "Where can a 100 MW data center get power fastest?"): DCPI scores 300+ markets daily on Excess Power and Grid Constraint, CC BY 4.0. DCPI rank for 
- predict_market_trajectory: Use this when the user asks where a data center market's power outlook is heading (next 1-8 quarters). Projects excess_power_score and constraint_score forward with confidence bands that WIDEN with horizon, from DC Hub's daily DCPI snapshot history, a time-series DC Hub owns. Use
- get_gas_index: Use this when the user asks which US states suit gas-fired data center power: the Data Center Gas Index (DCGI), a per-state score. ★ DO NOT COMPARE a DCGI figure published before 2026-08-08 with one published now — they are different indices; the full record is at /api/v1/dcgi/me
- get_gas_economics: Use this when the user asks what behind-the-meter gas power costs in a US data-center market: Henry Hub spot, regional basis differential, and the delivered industrial + electric gas tariff ($/MMBtu), each with its own source label. Pass market=<slug> (e.g. "northern-virginia", "
- get_grid_scoreboard: Use this when the user asks how power grids compare: demand, fuel mix or renewable share. GLOBAL grid scoreboard — 9 US grid operators (the 7 US ISOs PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE, plus BPA and TVA) + Great Britain (NESO) + the European bidding zones (Germany, Franc
- compare_isos: Use this when the user asks to compare two to four power grids side by side — fuel mix, demand, renewable/gas share, and for the US ISOs interconnection-queue depth and time-to-power — in one call instead of N sequential get_grid_intelligence calls. Example: "Compare PJM vs ERCOT
- get_intelligence_index: Use this when the user asks how healthy a data center market is: composite score (0-100) aggregating supply/demand balance, vacancy, absorption velocity, fiber depth, power availability, and pricing trend. Returns the index value, percentile rank across the 300+ market set, 7d/30
- list_transactions: Use this when the user asks about data center M&A, acquisitions or capital deals — 1,800+ tracked deals (2019-present), each with its disclosed value where public (many private deals are undisclosed). Returns deal name, buyer, seller, value, date, market, target operator, type (a
- get_news: Use this when the user asks for data center industry news or headlines (execute_plan also pulls news inside a broader market question). Curated data center industry news from 40+ trade sources (DCD, Data Center Knowledge, Data Center Frontier, Capacity Media, The Register Data Ce
- semantic_search: Use this when a data center or energy question is conceptual or fuzzy and keyword filters fall short — semantic (meaning-based) retrieval across DC Hub's industry news, M&A deals, the global facility map, per-market DCPI deep-dive narratives, press releases, announcements, permit
- search_intelligence: Use this when you need meaning-based search over DC Hub's data center intelligence corpus, choosing corpora — industry news, M&A deals, discovered facilities, per-market DCPI narratives, press releases, announcements, permitting intel, construction permits, tax incentives and the
- get_market_context: Use this when you need a whole data center market briefing for your context window — one call returns a token-budgeted context pack for a data-center market: DCPI verdict, power & grid facts, the Claude-written 12-month outlook, M&A deals, construction pipeline, operator footprin
- get_iso_context: Use this when you need a whole power grid (ISO) briefing for your context window — one call returns a token-budgeted context pack for a US ISO/RTO: live grid snapshot (demand, fuel-mix shares), DCPI verdict mix & grid economics across the ISO's tracked markets (queue wait, power 
- get_pipeline: Use this when the user asks what data centers are being built, announced or permitted in a market or by an operator. Example: "What data centers are under construction in Northern Virginia and when do they come online?" — get_pipeline country=US status=construction (there is no `
- get_power_pipeline: Use this when the user asks where new power generation is coming online (the forward supply pipeline) — e.g. "how much new generation is planned in Virginia / the Southeast / ERCOT, and when?". Planned, permitting, and under-construction generators NATIONWIDE from EIA-860M, INCLU
- get_infra_projects: Use this when the user asks what gas pipeline or transmission line projects are planned, proposed, approved or under construction — the forward build-out, not the existing network. e.g. "which interstate gas pipelines are under construction into Louisiana?", "what 345 kV transmis
- get_power_availability_timeline: Use this when the user asks when power will be available, or about time-to-power, in a US state: year by year. Composes: new generation coming online from EIA-860M monthly, split by confidence class (under-construction vs planned vs testing — never blended); scheduled retirements
- get_global_power: Use this when the user asks about power plants worldwide or in a non-US country — operating AND the forward pipeline (announced / pre-construction / under-construction), across ALL fuels (coal, oil/gas, nuclear, solar, wind, hydro, bioenergy, geothermal). Global Energy Monitor Gl
- get_interconnection_queue: Use this when the user asks about grid interconnection queues: how congested an ISO's queue is or how much data-center load is waiting. Returns queued generation GW per ISO. The projects field changes shape: with iso= it is an array of per-project rows; without iso it is an all-I
- get_refined_queue: Use this when you need interconnection queue projects filtered server-side. Instead of pulling the raw queue into context to filter (token-expensive, error-prone), push the predicates to the data layer and get back ONLY the survivors. Filter by min_mw, max_ttp_months (ISO-level a
- get_retirement_headroom: Use this when the user asks where retiring power plants free grid capacity: scans EIA-860M retirements to find near-term transmission grid headroom — a retiring plant is a CONCRETE headroom event (its POI frees injection capacity), from FILED data, not forecasts. Returns _entity=
- get_hosting_capacity: Use this when the user asks how many MW a distribution feeder can take: utility-published hosting capacity — the MW a NAMED distribution feeder can actually take, straight from the utility's own hosting-capacity GIS. Published records from many utilities (e.g. Con Edison, Nationa
- 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 se
- rank_sites: Use this when you have enriched candidate data center sites to rank under constraints — the normalization contract that lets you compare sites across separate analyze_site calls WITHOUT dropping into code. Pass candidates you already enriched (each an object with lat/lng + metric
- discover_tools: Use this when you are unsure which DC Hub data center, power or grid tool fits: lists tools by family. Returns _entity=tool_families — a front_door block (execute_plan for any multi-capability question, get_changes to refresh) plus families with a when-to-use note + their tools (
- plan_query: Use this when you want to see the plan for a data center question without running it (execute_plan runs the same planner and returns the answers). Reach for plan_query only to review, log, diff or audit a plan before executing it yourself. Deterministic keyword routing over the t
- save_to_shortlist: Use this when the user wants to keep a data center site on a named shortlist that survives across conversations (Phase 5 statefulness). Snapshots the site's objectives + its current percentile objective_score, so you can re-score it later against the evolving national baseline. U
- get_shortlist: Use this when the user wants to see a saved data center site shortlist. With refresh=true (default) each site is RE-SCORED against the current national percentile baseline and returns saved_score, current_score, and score_delta_since_saved — so you see whether a site slipped beca
- set_shortlist_alert: Use this when the user wants a drift alert on a saved site shortlist so you can stop polling and be notified when a site's national standing moves materially (Phase 5). Fires when any site in the shortlist has current percentile score < percentile_below OR score_delta_since_saved
- suggest_reallocation: Use this when a saved data center site drifts (its national standing dropped — surfaced by get_shortlist refresh or a set_shortlist_alert firing), get replacement candidates from the rest of that shortlist so the alert becomes an action, not just a warning (Phase 5). Returns TWO 
- get_grid_data: Use this when the user asks for live electricity grid data (power demand, fuel mix) for one grid: the 7 US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE), TVA, BPA, 40+ US utility balancing authorities (e.g. AZPS, SOCO, DUK, FPL, or a city: PHOENIX, ATLANTA), Canada (IESO, AE
- get_changes: Use this when the user asks what changed in data center markets, facilities or deals since a date. Returns DCPI 7-day market movers, newly discovered facilities, new M&A deals + news — PLUS, for keyed callers with saved sites, a `portfolio` block answering "did MY sites move?": p
- get_facility_risk_delta: Use this when the user asks how a data center facility's (or its market's) power risk changed recently — "has this site gotten riskier lately?". Returns the REAL DCPI market-health delta (excess-power score change over the window, direction improving/worsening/flat) from DC Hub's

Screening checks:
- MCP handshake: pass (Answered in 295ms)
- Domain against threat feeds (Cloudflare security DNS): pass (dchub.cloud not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (94 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 311 days ago)
- AI review of purpose and tool behavior: n/a (Automated checks only)