DC Hub — Data Center & Power Intelligence

{
  "id": "aix_159b169a30",
  "name": "DC Hub — Data Center & Power Intelligence",
  "operator": "(unclaimed - source: registry-official · publisher: cloud.dchub)",
  "description": "Live data-center, grid, fiber & gas infrastructure intelligence for AI agents — query and cite.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "api-integration",
    "browser-automation",
    "calendar-sync",
    "citation-check",
    "data-enrichment",
    "geo-coding",
    "inventory-check",
    "object-storage",
    "pdf-to-json",
    "spreadsheet-ops",
    "summarize-docs"
  ],
  "protocols": {
    "mcp": "https://dchub.cloud/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 4313,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 41,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T23:00:49.308Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://dchub.cloud/"
    },
    {
      "label": "repository",
      "url": "https://github.com/azmartone67/dchub-mcp-server"
    }
  ],
  "avatar": "https://github.com/azmartone67.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/azmartone67"
    }
  ],
  "payment_method": "open",
  "unreachable": false,
  "profile": {
    "mcp_server": "DC Hub Intelligence",
    "mcp_version": "2.12.19",
    "tool_count": 92,
    "tools": [
      {
        "name": "search",
        "description": "Search DC Hub for relevant records (OpenAI Deep Research / ChatGPT connector 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 page. For structured queries (by MW, operator, status, market) use search_facilities directly."
      },
      {
        "name": "fetch",
        "description": "Fetch a DC Hub record for an id returned by the `search` tool (OpenAI Deep Research / ChatGPT connector 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 (capacity MW, coordinates) use get_facility or open the url."
      },
      {
        "name": "execute_plan",
        "description": "Unified data-center siting, power-grid capacity and AI-compute infrastructure planner — megawatts and power density, grid headroom and power availability, interconnection queues, substations and transmission, site selection and buildable capacity, colocation and wholesale data-center markets, AI/GPU compute campuses, fiber routes, diversity and latency, PPAs and energy pricing, tax incentives and permitting, water and climate risk, data-center M&A and deals, power generation, gas and energy infrastructure. THE FRONT DOOR: call this FIRST whenever a question spans more than one of those, instea"
      },
      {
        "name": "search_facilities",
        "description": "FRONT DOOR CHECK — if the ask is \"find <N> MW in <market>\" or otherwise wants power / fiber / water / verdict context ATTACHED to the hits, call `execute_plan(intent=\"<the user's question, unchanged>\")` instead of hand-chaining this with three more tools. If the ask is a plain inventory lookup — which facilities match these filters — search_facilities IS the right call and costs one round trip; the planner would add steps and latency for nothing. Search 24,600+ global data center facilities across 170+ countries — by location (country/state/market), capacity (MW), operator, fiber connectivity,"
      },
      {
        "name": "get_facility",
        "description": "Full metadata for one 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 \"who operates this data center and how big is it\", \"how many fiber carriers are in that building\". Try: get_facility id=equinix-dc1-ashburn — or get_facility slug=digital-realty-iad8. Returns ONE facility in full; do NOT use to search or list many facilities (use search_facilities)."
      },
      {
        "name": "get_market_intel",
        "description": "Use when a user asks about ONE data-center market — vacancy, capacity pricing, supply pipeline, dominant operators, YoY growth — across any of 300+ markets. Example: \"What is Northern Virginia's vacancy rate, $/MW-day pricing, and current DCPI verdict?\" — get_market_intel market=northern-virginia. Params: market is the market_slug (e.g. \"northern-virginia\", \"dallas\", \"phoenix\", \"frankfurt\", \"tokyo\", \"singapore\"). Returns: {market, country, capacity_mw_total, capacity_mw_under_construction, vacancy_pct, absorption_mw_ttm, price_per_mw_day_usd, yoy_growth_pct, dominant_operators[], dcpi_verdict "
      },
      {
        "name": "get_market_dcpi_rank",
        "description": "DCPI rank for a single market: BUILD/CAUTION/AVOID verdict, 0-100 composite_score (verdict-aware), excess_power_score, constraint_score, time_to_power_months. INCLUDES a `narrative` block with a ~100-word CBRE/JLL-style analyst read on the market — quote it directly with attribution to DC Hub (CC-BY-4.0). Use to answer \"should I build here?\" with structured reasoning + ready-to-cite prose across 300+ scored markets in 10 ISOs. Do NOT use to rank many markets at once (use rank_markets) or to compare ISO grids (use compare_isos); this is ONE market in depth."
      },
      {
        "name": "predict_market_trajectory",
        "description": "Forecast a DCPI market's near-term trajectory (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 — the only source that can, because it owns the time-series. Use to answer \"is this market trending toward BUILD or AVOID?\" or \"will Dallas power stay tight over the next 6 months?\". Params: market_slug (required, metro slug e.g. dallas, phoenix, northern-virginia — valid slugs come from rank_markets / get_market_dcpi_rank); horizon_quarters (optional 1-8, default 4; 2 = ~6 months out"
      },
      {
        "name": "get_gas_index",
        "description": "Data Center Gas Index (DCGI) — the per-US-state natural-gas suitability score. ★ WITHDRAWN 2026-08-08, RESTORED 2026-08-30 after all three defective terms were repaired: the 20-point interstate-share term was case-blind against EIA TYPEPIPE and scored ~0 for every state (122 -> 17,571 segments now counted); the price was chosen by a non-deterministic tie-break across the EIA industrial (PIN) and electric-power (PEU) series, which carry different margins; and nine states including Texas ran on a hardcoded cost constant because the price loader dropped them on a case-sensitive name lookup. ★ DO "
      },
      {
        "name": "get_gas_economics",
        "description": "Behind-the-meter / gas-fired power inputs for 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\", \"dallas\", \"phoenix\"). ★ WITHDRAWN 2026-08-08: the gas-to-grid levelized cost ($/MWh across CCGT/peaker heat-rate scenarios) is NO LONGER RETURNED. Five surfaces published a $/MWh for the same market on the same day up to 5.5x apart because each chose the burner-tip price by a different rule, with no sanity gate — this endpoint served a physic"
      },
      {
        "name": "get_grid_scoreboard",
        "description": "GLOBAL grid scoreboard — 9 US grid operators (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE, BPA, TVA) + Great Britain (NESO) + the European bidding zones (Germany, France, Netherlands, Italy/Milan, Spain, Poland, Switzerland, Portugal, the Nordics + Central/Eastern Europe — via ENTSO-E; the exact live-vs-configured count is in counts_basis.eu_zones_live / eu_zones_configured, measured per call rather than asserted here) + Taiwan (Taipower) + Japan (OCCTO areas) + South Korea (KPX) + Brazil SIN (ONS), ranked side-by-side on each feed's LATEST PUBLISHED reading: renewable share %, gas share %, fu"
      },
      {
        "name": "compare_isos",
        "description": "Use when a user wants a side-by-side of 2-4 ISO grids — fuel mix, demand, renewable/gas share, interconnection-queue depth, time-to-power — in one call instead of N sequential get_grid_intelligence calls. Example: \"Compare PJM vs ERCOT vs CAISO on gas share, renewable share, and queue depth right now.\" — compare_isos isos=\"PJM,ERCOT,CAISO\". Params: isos is a comma-separated list (2-4 max) drawn from the 7 live US ISOs: \"PJM\" | \"ERCOT\" | \"CAISO\" | \"MISO\" | \"SPP\" | \"NYISO\" | \"ISO-NE\". Returns: {isos[], comparison:{<iso>:{demand_mw, generation_mix_pct, renewable_share_pct, gas_share_pct, constrai"
      },
      {
        "name": "get_intelligence_index",
        "description": "Real-time composite market health 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/30d trend direction, and underlying component scores. Answers \"is this market healthy\", \"how does Northern Virginia look overall right now\". Try: get_intelligence_index market=northern-virginia. Returns ONE composite health number for a market; do NOT use for the full market metric set (use get_market_intel) or to rank multiple markets (use rank_markets)."
      },
      {
        "name": "list_transactions",
        "description": "M&A and capital transactions in the data center sector — 1,600+ 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 (acquisition/JV/refinance/recap). Filter by date range (date_from/date_to, ISO-8601), min_value_usd, region, buyer, or seller. Answers \"which data-center deals closed this year\", \"what was that acquisition worth\". Try: list_transactions date_from=2026-01-01 min_value_usd=1000000000. There is no `year` parameter — use date_from/date_to. Broad M&A "
      },
      {
        "name": "get_news",
        "description": "FRONT DOOR CHECK — if news is only ONE input to a bigger question (is this market heating up, should we still build here), call `execute_plan(intent=\"<the user's question, unchanged>\")` and let it pull news alongside the market and grid reads. If the user actually wants the headlines, get_news IS the right call — one round trip; do not send a plain news request through the planner. Curated data center industry news from 40+ trade sources (DCD, Data Center Knowledge, Data Center Frontier, Capacity Media, The Register Data Centre, Fierce Telecom, etc.) refreshed every 30 min. Returns title, summ"
      },
      {
        "name": "semantic_search",
        "description": "Use for CONCEPTUAL / fuzzy questions where keyword filters fall short — semantic (meaning-based) retrieval across DC Hub's industry news, M&A deals, 24,600+ discovered facilities, and per-market DCPI deep-dive analysis narratives, ranked by relevance with citable source fields (news url/title, deal parties/value, facility name/location, deep-dive market/url). Examples: \"what is happening with behind-the-meter gas for AI data centers?\", \"deals involving nuclear power for hyperscalers\", \"why is Northern Virginia constrained?\" — semantic_search q=\"behind-the-meter gas for AI data centers\". Params"
      },
      {
        "name": "search_intelligence",
        "description": "Semantic (meaning-based) search over DC Hub's live intelligence corpus — industry news, M&A deals, discovered facilities and per-market DCPI analysis narratives — returning the most relevant records with citable source fields. This is the agent-friendly alias over the SAME retrieval layer as semantic_search: same results, different call shape. It takes `query` plus human-readable corpus names (news | deals | facilities | market_narratives); semantic_search takes `q` plus the raw table names. Call ONE of them, not both. Params: query (required, natural language); corpus (optional CSV of the fou"
      },
      {
        "name": "get_market_context",
        "description": "Use when an agent needs a WHOLE-market briefing it can drop straight into its 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 footprint, transaction comps, risk factors, and top news — each section with its own token count, as_of timestamp, and citable URL, greedily filled in that priority order under your max_tokens budget. Example: \"Brief me on the Columbus data-center market\" — get_market_context market=columbus max_tokens=4000. Params: "
      },
      {
        "name": "get_iso_context",
        "description": "Use when an agent needs a WHOLE-grid briefing it can drop straight into its 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 cost, reserve margin), interconnection-queue depth with the largest projects, real-time benchmark LMP, the tracked DCPI market list, deep-dive narrative excerpts, and recent news — each section with its own token count, as_of timestamp, and citable URL, greedily filled in that priority order under your max_to"
      },
      {
        "name": "get_pipeline",
        "description": "Use when a user asks \"what is being built / announced / permitted\" in a market or by an operator — the forward-looking construction pipeline. 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 `market` parameter — filter by country/operator, or use search_facilities for a named market). Params: status one of \"announced\" | \"permitted\" | \"construction\" | \"operational\"; operator (e.g. \"Equinix\", \"Digital Realty\", \"AWS\"); country (ISO-2, e.g. \"US\", \"DE\"); min_capacity_mw (e.g. 50 to filte"
      },
      {
        "name": "get_power_pipeline",
        "description": "Use when a 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, INCLUDING non-ISO regions (TVA, Southern Co, Arizona PS, PacifiCorp, LADWP) that interconnection-queue feeds miss. Each generator has location (lat/lng), state, county, balancing authority, technology/fuel (solar photovoltaic, onshore wind, natural-gas combined cycle, batteries, nuclear), nameplate megawatts (MW), status (planned "
      },
      {
        "name": "get_infra_projects",
        "description": "Use when a 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 transmission projects does ERCOT plan by 2028?\", \"what new projects appeared since last month?\". COVERS: (1) natural gas pipeline projects US-wide from the EIA natural gas pipeline projects list (public domain) — operator, status (Announced, Pre-applied, Applied, Approved, Construction, On Hold, Completed), states crossed, capacity i"
      },
      {
        "name": "get_power_availability_timeline",
        "description": "Power-availability TIMING for one US state — when power gets EASIER, 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 as dated subtractions; LBNL interconnection-queue depth as congestion context (NO delivery dates — the feed has none and most queued MW never completes). The one derived number, cumulative_firm_signal_mw, counts ONLY under-construction+testing minus retirements — speculative permitting-stage MW is shown but never folded in. Answers \"when is new "
      },
      {
        "name": "get_global_power",
        "description": "Use when a user asks about power plants/units 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 Global Integrated Power Tracker: 182,000+ geolocated units across 170+ countries, each with fuel, capacity (MW), status, start year, operator/owner and lat/lng. Filter by country (e.g. Germany, India, Brazil, Japan), fuel (comma-union: coal, oil/gas, nuclear, solar, wind, hydro), status, pipeline=true (JUST the forward se"
      },
      {
        "name": "get_interconnection_queue",
        "description": "ISO interconnection queue snapshot: total queued GENERATION capacity (queued_load_total_gw, GW) per ISO from each ISO's public queue. For ERCOT it ALSO returns the large-load (data-center-driven) interconnection queue in queued_load_data_center_gw — >225 GW in process / ~9 GW approved-to-energize (ERCOT's published Q1-2026 figure; ERCOT is the only ISO that publishes a comparable large-load feed, so other ISOs' data_center_gw is null), with provenance in top_subregions. Sources: ERCOT GIS + Large Load Integration, PJM/MISO/SPP/CAISO/NYISO/ISO-NE public queues. Pass iso=ERCOT (or any of 7) to d"
      }
    ],
    "profiled_at": "2026-09-24T23:00:49.308Z"
  }
}