# exascale.build MCP server

US ISO interconnection queues and cited energy data. 25 free queries, then $49/mo or $490/yr.

## At a glance

exascale.build is an MCP server in the Other category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 60 tools, including list_capabilities_v1, get_source_evidence_v1 and describe_capability_v1. It scores D (33/100) on the MCP Skills Hub health score as of Oct 28, 2026.

## Install

### How to install exascale.build in Claude Code

1. Add the server

```bash
claude mcp add --transport http osint https://api.exascale.build/mcp
```

2. Verify it's connected

```bash
claude mcp list
```

3. Sharing it with your team?

   Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

4. Use it in a session

   Ask Claude to use the tools this server exposes (e.g. list_capabilities_v1, get_source_evidence_v1, describe_capability_v1). It discovers them automatically.

### How to install exascale.build in Claude Desktop

1. Open your MCP config

   macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add this server

```json
{
  "mcpServers": {
    "osint": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.exascale.build/mcp"
      ]
    }
  }
}
```

3. Why the wrapper?

   This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.

4. Restart Claude Desktop

   The tools appear under the 🔌 menu once the app reloads.

### How to install exascale.build in Cursor

1. Create / edit .cursor/mcp.json in your project

```json
{
  "mcpServers": {
    "osint": {
      "url": "https://api.exascale.build/mcp"
    }
  }
}
```

2. Enable it

   Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

### How to install exascale.build in Codex CLI

1. Add to ~/.codex/config.toml

```toml
[mcp_servers.osint]
command = "npx"
args = ["-y", "mcp-remote", "https://api.exascale.build/mcp"]
```

2. Why the wrapper?

   Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.

3. Run Codex

   Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

### How to install exascale.build in Windsurf

1. Edit ~/.codeium/windsurf/mcp_config.json

```json
{
  "mcpServers": {
    "osint": {
      "serverUrl": "https://api.exascale.build/mcp"
    }
  }
}
```

2. Reload

   Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

### How to install exascale.build in Cline

1. Open Cline → MCP Servers → Configure

   Adds to cline_mcp_settings.json.

2. Add the server

```json
{
  "mcpServers": {
    "osint": {
      "type": "streamableHttp",
      "url": "https://api.exascale.build/mcp"
    }
  }
}
```

### How to install exascale.build in VS Code

1. Create .vscode/mcp.json

```json
{
  "servers": {
    "osint": {
      "type": "http",
      "url": "https://api.exascale.build/mcp"
    }
  }
}
```

2. Start it

   VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

## Tools

- `list_capabilities_v1` — List available exascale.build data capabilities for agent discovery before querying. Also call this BEFORE stating that a capability is not available — client tool lists are cached and this surface grows; anything listed here is reachable via query_capability_v1 even if your tool list predates it.
- `get_source_evidence_v1` — Fetch and hash-verify the raw source row behind a returned citation. Pass a citation object inside `params`. Two ready-to-pass shapes come straight from the query tools: each aggregate row's `citations[ref].verify` object, or a detail record's `citation` (from include_records). Either proves the number with no re-query. The tool verifies the raw workbook SHA-256 before returning source-header row 
- `describe_capability_v1` — Describe any served capability by name — the generic twin of the named describe tools. Pass `capability` as either a capability id from list_capabilities_v1 (e.g. "power.capacity") or a query primitive name (e.g. "query_power_capacity_v1"). Returns the same schema payload as the named describe tool: valid filters, groupings, metrics, detail fields, and citation fields. Use the generic pair (this +
- `query_capability_v1` — Query any served capability by name — the generic twin of the named query tools, reaching every capability including ones newer than your client's cached tool list. Pass `capability` as either a capability id from list_capabilities_v1 (e.g. "power.price_ercot") or a query primitive name (e.g. "query_power_price_ercot_v1"), and `params` as the same flat JSON object the named query tool accepts — ca
- `describe_power_capacity_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.capacity.
- `query_power_capacity_v1` — Query verified U.S. generator-level operating, planned, retired, or canceled power capacity from EIA-860M. Use this for capacity questions by state/jurisdiction, county FIPS, source-reported balancing authority code, fuel, prime mover, technology, lifecycle, or year. Pass filters inside the `params` object. The operating/planned/retired/canceled selector is `lifecycle` (e.g. `lifecycle: "operating
- `describe_power_generation_v1` — Describe valid filters, groupings, atoms, metrics, detail fields, and citation fields for power.generation.
- `query_power_generation_v1` — Query verified U.S. monthly net electricity generation (MWh) from EIA-923. Use this for "how much was generated" questions by state, source-reported balancing authority code, fuel, prime mover, sector, plant, or generator, for a given month. For a fuel total or a fuel mix (e.g. "coal generation", "top fuels"), filter or group by `fuel_group` — it sums the several energy_source_code values a fuel s
- `describe_power_asset_ownership_v1` — Describe annual EIA-860 ownership filters, convention, metrics, and exact-cell citations.
- `query_power_asset_ownership_v1` — Query verified annual EIA-860 generator ownership. Returns the Owner schedule's raw owner names and ownership shares for each `eia_plant_id` + `generator_id`. `percent_owned` is the workbook's raw fraction of one (0.6 = 60%), not a whole-number percent. Filter by plant, generator, exact raw owner name, state, owner state, annual vintage, or source-reported balancing authority code; `{"state":"TX",
- `describe_power_fuel_cost_v1` — Describe EIA-923 receipt/cost filters, raw units, missing semantics, and exact-cell citations.
- `query_power_fuel_cost_v1` — Query verified raw EIA-923 fuel receipts and delivered fuel costs. Returns one Page 5 Fuel Receipts and Costs row per published receipt: plant/month, fuel, supplier, purchase type, source physical quantity, and delivered cost in EIA's stated cents/MMBtu. Filter by plant, month/range, exact source strings, state, fuel, cost status, or source-reported balancing authority code; `{"state":"TX","balanc
- `describe_power_plant_costs_v1` — Describe native-XBRL Form 1 plant-cost facts, units, coverage, and exact-fact citations.
- `query_power_plant_costs_v1` — Query accepted native-XBRL FERC Form 1 large-steam plant facts. Returns one separately cited XBRL fact per respondent, report year, raw plant name, and source concept: installed capacity, net generation, plant-cost balance items, fuel expense, and individual operation and maintenance lines. Values and units are as filed; nominal dollars are not adjusted, allocated, divided by generation, or combin
- `describe_natural_gas_prices_v1` — Describe the EIA Henry Hub and state electric-power gas-price atoms, units, aggregate grain, missingness, vintages, and citations.
- `query_natural_gas_prices_v1` — Query verified EIA natural-gas price records from two public series. `atom="henry_hub_daily_spot"` returns one trading-day Henry Hub spot price in EIA's published $/MMBtu unit (series RNGWHHD). `atom="state_electric_power_monthly"` returns one state-month average price paid by electric-power consumers in EIA's published $/Mcf unit; `{"atom":"state_electric_power_monthly","state":"TX"}` is the Texa
- `describe_power_demand_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.demand.
- `query_power_demand_v1` — Query verified U.S. hourly electricity demand (MW) by balancing authority from EIA-930. Use this for "how much load" questions at the hourly balancing-authority grain: filter or group by `balancing_authority_code`, `region`, `data_date` (or the `data_date_from`/`data_date_to` range), `hour_number`, `datetime_utc`, or `is_imputed`. Pass filters inside the `params` object. Returns JSON aggregates wi
- `describe_power_demand_rollup_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.demand_rollup.
- `query_power_demand_rollup_v1` — Query verified U.S. hourly electricity demand (MW) as EIA's own published national and regional totals from the EIA Grid Monitor (region-data). Use this for "how much load for the whole country, or a region" questions. Filter by `respondent` (US48 = the Lower-48 national total, or one of the 13 EIA regions — CAL, CAR, CENT, FLA, MIDA, MIDW, NE, NW, NY, SE, SW, TEN, TEX), `data_date` (one day) or t
- `describe_power_retail_sales_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.retail_sales.
- `query_power_retail_sales_v1` — Query verified U.S. annual retail electricity sales — billed MWh, revenue, and customer counts — by utility, state, and customer sector from EIA-861. Use this for "who sold how much power to whom" questions at the annual utility×state×sector grain: filter or group by `data_year`, `state`, `sector` (residential / commercial / industrial / transportation), `part`, `service_type`, `ownership`, `ba_co
- `describe_power_interconnection_queue_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue.
- `query_power_interconnection_queue_v1` — Query the MISO generator interconnection queue — the public waiting line of projects that have REQUESTED to connect to the MISO grid (the 15-state Midwest/South footprint). Returns cited, project-level records: requested megawatts (net summer / net winter), location (`state`, `county`, derived `county_fips`), fuel and technology as MISO reports them, three independent status dimensions (`applicati
- `describe_power_interconnection_queue_pjm_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_pjm.
- `query_power_interconnection_queue_pjm_v1` — Query the PJM New Services (interconnection) queue — the public waiting line of projects that have REQUESTED to connect to the PJM grid (the mid-Atlantic RTO incl. Northern Virginia, PA, NJ, MD, OH, VA, WV and more). Returns cited, project-level records with PJM's full published structure: requested megawatts (`requested_max_output_mw` = MFO, `requested_summer_mw` = MW Capacity / summer net, `requ
- `describe_power_interconnection_queue_pjm_cycle_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_pjm_cycle.
- `query_power_interconnection_queue_pjm_cycle_v1` — Query PJM's cluster/cycle service-request grid — the cluster view of PJM's interconnection process: the TC1/TC2 transition cycles (re-processing the pre-Order-2023 serial backlog) and the reopened steady-state cycles (C01+, the new intake). A SEPARATE PJM publication from the full New Services queue (query_power_interconnection_queue_pjm_v1) — richer per-project cluster detail; the two share rows 
- `describe_power_interconnection_queue_caiso_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_caiso.
- `query_power_interconnection_queue_caiso_v1` — Query the CAISO generator interconnection queue — California ISO's public Public Queue Report, the waiting line of projects that have REQUESTED to connect to the CAISO grid (California, plus the out-of-state edges it studies: NV, AZ). Returns cited, project-level records with CAISO's full published structure: the net megawatts to grid (`net_mw_to_grid`, CAISO's own headline figure) and the per-com
- `describe_power_interconnection_queue_nyiso_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_nyiso.
- `query_power_interconnection_queue_nyiso_v1` — Query the NYISO generator + load interconnection queue — New York ISO's public waiting line of projects that have REQUESTED to connect to the New York grid. Uniquely among ISOs, NYISO publishes a Load Projects tab — load interconnection requests (large-load demand), served as-reported — and since its 2026-07 edition tags each load request with its own `End-Use` class (`end_use`, e.g. DAT / DAT-AI 
- `describe_power_interconnection_queue_isone_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_isone.
- `query_power_interconnection_queue_isone_v1` — Query the ISO-NE generator interconnection queue — ISO New England's public IRTT "public queue" report, the waiting line of projects that have REQUESTED to connect to the New England grid (CT, MA, ME, NH, RI, VT). Returns cited, project-level records with ISO-NE's full published structure (all 31 columns of the rendered report): the three megawatt readings kept SEPARATE (`net_mw`, `summer_mw` = ma
- `describe_power_interconnection_queue_ercot_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_ercot.
- `query_power_interconnection_queue_ercot_v1` — Query the ERCOT generator interconnection queue — ERCOT's public GIS Report (EMIL PG7-200-ER), the waiting line of generation projects that have REQUESTED to connect to the ERCOT (Texas) grid. Returns cited, project-level records with ERCOT's full published structure across four lifecycle sheets (Large Gen + Small Gen = active; Inactive Projects; Cancellation Update): the requested `capacity_mw` (
- `describe_power_interconnection_queue_spp_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_spp.
- `query_power_interconnection_queue_spp_v1` — Query the SPP generator interconnection queue — Southwest Power Pool's public GI Summary report, the waiting line of generation projects that have REQUESTED to connect to the SPP grid (the ~14-state central-US RTO: OK, KS, TX panhandle, NE, NM, MO, CO, ND, SD, AR, LA and more). Returns cited, project-level records with SPP's full published structure: the requested `capacity_mw` (SPP's headline `Ca
- `describe_power_price_ercot_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for power.price_ercot.
- `query_power_price_ercot_v1` — Query verified ERCOT wholesale electricity prices — ERCOT's Day-Ahead Market Settlement Point Prices ($/MWh, EMIL NP4-190-CD), the price cleared the day before each operating day at every ERCOT (Texas) settlement point, served hourly. Returns cited prices for each (`settlement_point`, `delivery_date`, `hour_ending`): the per-hour `price_usd_per_mwh` in detail records, plus `avg_price_usd_per_mwh`,
- `describe_power_capacity_accreditation_pjm_v1` — Describe PJM ELCC document identities, class dimensions, metrics, and citations.
- `query_power_capacity_accreditation_pjm_v1` — Query cited PJM marginal ELCC class ratings by document kind, auction, delivery year, and resource class. Preliminary, final, and incremental-auction documents remain separate; no value is preferred or reconciled. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the
- `describe_power_capacity_market_pjm_v1` — Describe PJM RPM delivery-year/LDA filters, UCAP metrics, and citations.
- `query_power_capacity_market_pjm_v1` — Query cited PJM Base Residual Auction UCAP clearing prices, RTO cleared MW, reliability requirement, and published administrative price collar by delivery year and LDA. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.
- `describe_power_capacity_accreditation_miso_v1` — Describe MISO accreditation document kinds, resource classes, ratios, suppressions, and citations.
- `query_power_capacity_accreditation_miso_v1` — Query cited MISO Schedule 53 class-average and indicative-DLOL seasonal accreditation ratios, including published unit counts, storage variants, and explicit suppression atoms. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.
- `describe_power_capacity_market_miso_v1` — Describe MISO PRA planning-year, season, zone, parameter, and citation fields.
- `query_power_capacity_market_miso_v1` — Query cited MISO Planning Resource Auction seasonal zonal ACP, verbatim ERZ values, published CONE parameters, and IMM conduct thresholds. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.
- `describe_ai_infrastructure_construction_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.construction.
- `query_ai_infrastructure_construction_v1` — Query verified U.S. private construction spending ($ millions) for data centers and semiconductor/computer-electronics manufacturing plants, from the U.S. Census Bureau's Value of Construction Put in Place (C30). Use this for "how much is being spent BUILDING data centers (or chip fabs) in the US" questions — the construction buildout in dollars, not capacity or investment. Filter by `category` ("
- `describe_ai_infrastructure_trade_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.trade.
- `query_ai_infrastructure_trade_v1` — Query verified U.S. monthly IMPORTS of integrated circuits (HS-8542) — customs value (USD) by country of origin — from the U.S. Census Bureau's International Trade data. Use this for "how much $ of chips did the US import (from Taiwan / South Korea / in total) and how is it trending" questions. HS-8542 is ALL integrated circuits (processors, memory, amplifiers, parts) — NOT AI-accelerator / GPU-sp
- `describe_ai_infrastructure_equipment_trade_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.equipment_trade.
- `query_ai_infrastructure_equipment_trade_v1` — Query verified U.S. monthly IMPORTS of semiconductor-manufacturing EQUIPMENT (HS-8486) — customs value (USD) by country of origin — from the U.S. Census Bureau's International Trade data. Use this for "is the fab buildout actually tooling up, and who supplies the machines" questions — the equipment leg of the fab lifecycle: construction spending (ai_infrastructure.construction) measures the shell,
- `describe_ai_infrastructure_production_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.production.
- `query_ai_infrastructure_production_v1` — Query verified U.S. semiconductor & electronic-component PRODUCTION and CAPACITY UTILIZATION — the Federal Reserve's monthly G.17 industrial-production index (2017=100) and capacity-utilization rate (percent) for NAICS 3344 — from the Board's own release, history to 1972. Use this for "are the domestic fabs actually producing / how hot are they running" questions — the OUTPUT leg of the fab lifecy
- `describe_robotics_trade_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for robotics.trade.
- `query_robotics_trade_v1` — Query verified U.S. monthly IMPORTS of INDUSTRIAL ROBOTS — customs value (USD) AND unit counts (number of robots) — by country of origin, from the U.S. Census Bureau's International Trade data. Use this for "how many robots is the US importing, from whom, and what are they worth" questions — the only high-frequency official U.S. robotics series. Covers the nomenclature's two robot-specific HS-10 c
- `describe_robotics_adoption_v1` — Describe valid filters, groupings, metrics, detail fields, and citation fields for robotics.adoption.
- `query_robotics_adoption_v1` — Query the verified share of US manufacturing plants USING industrial robots — plus workers exposed and robotics capex — from the Census Industrial Robotic Equipment product (the first official federal robotics-adoption statistics). Use this for "are factories actually adopting robots" questions — the INSTALLED-BASE reading the import data cannot see. Serves the percent of plants with robots and th

---

Source: https://mcp-skills-hub.vercel.app/mcps/build-exascale-osint · MCP Skills Hub · data as of 2026-10-28T12:31:05Z