@pipeworx/dchub

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/dchub’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 5

Data-center site selection, power and grid intelligence from DC Hub: facility registry, per-metro market intelligence, live grid fuel mix and demand, leasable capacity, and a one-call planner for multi-part siting questions.

Tools

• dchub_execute_plan(intent, ...) — answers a multi-part data-center question in one call (e.g. “rank markets for a 200 MW AI campus”, “power headroom in PJM”) and returns the combined result with citations.
• dchub_search_facilities(city, state, country, operator, min_capacity_mw, ...) — which data centers exist and who operates them.
• dchub_get_market_intel(market) — vacancy, pricing, pipeline and operators for one metro, by market slug (e.g. northern-virginia).
• dchub_get_grid_data(iso) — live fuel mix and demand for a grid (PJM, ERCOT, CAISO and others).
• dchub_source_capacity(min_mw, region, ...) — powered land, shells, turnkey capacity and colocation available to buy or lease.

Auth

Keyless. Without a DC Hub key, DC Hub returns a trimmed PREVIEW for some tools (a few rows per list, no MW detail); every response says so in preview / preview_notice. A caller may pass their own DC Hub key as _apiKey for fuller answers. A Pipeworx-wide partner key is not configured yet.

Data sources

• DC Hub (dchub.cloud), data-center intelligence platform: facility registry, Data Center Power Index and market intelligence, grid feeds, capacity listings. Cite as “DC Hub, dchub.cloud”. Live per-request; nothing is stored by Pipeworx.

DC Hub asked that partner traffic be identifiable; every call carries X-DCHub-Via: pipeworx (changes nothing in access). Results are JSON wrapped in {source, preview, result}; result.provenance carries DC Hub’s own completeness and as-of fields, and as_of may be null: do not cite retrieved_at as a data date. dchub_execute_plan responses are large (tens of KB).

Tools

• dchub_execute_plan — Answer a multi-part data-center question in one call (DC Hub): e.g. “rank markets for a 200 MW AI campus” or “power headroom in PJM”. Plans and runs the needed lookups and returns the combined result
• dchub_search_facilities — Find data centers and who operates them (DC Hub facility registry), filtered by city, state, country, operator or MW range. Returns name, operator, location and verification flag; MW detail needs a DC
• dchub_get_market_intel — Data-center market intelligence for one metro (DC Hub): facility count, tracked MW, status mix, top providers, pipeline and lease pricing. Market is a slug such as northern-virginia. Keyless calls ret
• dchub_get_grid_data — Live electricity grid data for one grid (DC Hub): fuel mix and demand for US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE), utility balancing authorities, and international grids.
• dchub_source_capacity — Search data-center capacity available to buy or lease (DC Hub Capacity Source): powered land, powered shells, turnkey capacity and colocation, by size (min_kw / min_mw) and location (region, state, ma