DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber

{
  "id": "aix_3bc9e19831",
  "name": "DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber",
  "operator": "(unclaimed - source: registry-official · publisher: cloud.dchub)",
  "description": "Live power, energy, grid, gas, fiber & data-center site-selection infrastructure — query and cite.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-10-22",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "api-integration",
    "calendar-sync",
    "citation-check",
    "data-enrichment",
    "dedupe-records",
    "geo-coding",
    "inventory-check",
    "object-storage",
    "pdf-to-json",
    "spreadsheet-ops",
    "summarize-docs"
  ],
  "protocols": {
    "mcp": "https://dchub.cloud/mcp/officialregistry",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 3339,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 41,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-10-22T23:00:42.379Z"
  },
  "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"
    }
  ],
  "profile": {
    "mcp_server": "DC Hub Intelligence",
    "mcp_version": "2.12.43",
    "tool_count": 94,
    "tools": [
      {
        "name": "claim_free_key",
        "description": "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 2 full answers per tool per day. Add an email: 50 calls/day. Ask the user for an email first; pass it only if they typed it (makes the key recoverable). Save and reuse the key (lost one: recover_my_key); don't re-mint. Then ask the real question (execute_plan for multi-step). If a call was answered with a sign-in chall"
      },
      {
        "name": "search",
        "description": "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 page. For structured queries (by MW, operator, status, market) use search_facilities directly."
      },
      {
        "name": "fetch",
        "description": "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 (capacity MW, coordinates) use get_facility or open the url."
      },
      {
        "name": "execute_plan",
        "description": "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 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. Recommended entry for a question that spans more than one of those. Pass the user's question as"
      },
      {
        "name": "search_facilities",
        "description": "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_directory_listing. Free: names and locations; MW and specs need a paid key. Ex: \"Equinix sites in Virginia over 10 MW.\" Start here for a facility slug. No match = empty data, not an error: broaden filters. limit 1-500 (free tier 25); page with offset."
      },
      {
        "name": "get_facility",
        "description": "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 \"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). Needs a slug or id from search_faciliti"
      },
      {
        "name": "get_market_intel",
        "description": "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, recent_facilities, market_pricing (quote its basis). Verdict: use get_market_dcpi_rank. Keyless: a trimmed preview; a free key gets more. Ex: \"1 MW colo price in Los Angeles?\" Get the market slug from rank_markets or get_market_dcpi_rank; 404 = unrecognised market, use one of those slugs."
      },
      {
        "name": "get_market_dcpi_rank",
        "description": "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 one 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 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 struct"
      },
      {
        "name": "predict_market_trajectory",
        "description": "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 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 "
      },
      {
        "name": "get_gas_index",
        "description": "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/methodology under `corrections`. A state that cannot be priced comes back verdict UNSCORED with dcgi null and an `unscored_reason`, never a placeholder score, so treat UNSCORED as absence and not as a low score. `gas_price_series` names which EIA series answered each state. Gas-fired $/MWh figures, withdrawn the same day"
      },
      {
        "name": "get_gas_economics",
        "description": "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\", \"dallas\", \"phoenix\"). AZ, GA, FL), never a substitute price; if the backend switch is ever turned off again, `gas_to_grid_status` carries that reason. ★ DO NOT COMPARE a $/MWh published before 2026-09-27 with one published now — each surface then picked the price its own way, up to 5.5x apart. Do not derive a $/MWh your"
      },
      {
        "name": "get_grid_scoreboard",
        "description": "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, 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) + B"
      },
      {
        "name": "compare_isos",
        "description": "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 vs CAISO on gas share, renewable share, and queue depth right now.\" — compare_isos isos=\"PJM,ERCOT,CAISO\"; \"ERCOT vs AESO vs EU_DE_LU\" also works. Params: isos is a comma-separated list (2-4 max): any of the 7 US ISOs (\"PJM\" | \"ERCOT\" | \"CAISO\" | \"MISO\" | \"SPP\" | \"NYISO\" | \"ISO-NE\"), TVA, BPA, a US utility BA, or a no"
      },
      {
        "name": "get_intelligence_index",
        "description": "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/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 m"
      },
      {
        "name": "list_transactions",
        "description": "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 (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 dat"
      },
      {
        "name": "get_news",
        "description": "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 Centre, Fierce Telecom, etc.) refreshed every 30 min. Returns title, summary, source, published_at, and the market/operator entities mentioned. Filter by category (deals/permits/outages/policy/AI). Answers \"what is happening in the data center industry this week\", \"any news on AI capacity\". Try: get_news category=AI limi"
      },
      {
        "name": "semantic_search",
        "description": "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, permitting intel, construction permits, tax incentives and the capacity pipeline, 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 "
      },
      {
        "name": "search_intelligence",
        "description": "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 capacity pipeline — 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 short corpus names (news | deals | facilities | market_narratives | press | announcements | pe"
      },
      {
        "name": "get_market_context",
        "description": "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 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: market (re"
      },
      {
        "name": "get_iso_context",
        "description": "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 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_tokens budge"
      },
      {
        "name": "get_pipeline",
        "description": "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 `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 filter hyperscale); expected_c"
      },
      {
        "name": "get_power_pipeline",
        "description": "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, 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 (p"
      },
      {
        "name": "get_infra_projects",
        "description": "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 transmission projects are planned in PJM by 2030?\", \"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, "
      },
      {
        "name": "get_power_availability_timeline",
        "description": "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 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 fold"
      },
      {
        "name": "get_global_power",
        "description": "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 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 s"
      }
    ],
    "profiled_at": "2026-10-22T23:00:42.379Z"
  },
  "unreachable": false,
  "payment_method": "open"
}