mcpField
E
Exascale.build

Exascale.build

リモート
exascale.build開発ツール03 週間前に更新
リポジトリ公式サイト

Exascale.build について

Exascale.build は、米国の電力、送電網、関連産業のデータを MCP と REST で提供します。キューや市場を調べる分析者向けで、出典の提示と元ファイルのセル単位での検証に対応しています。

主な機能

  1. 01ISO 接続キューの検索
  2. 02電力・天然ガスデータの検索
  3. 03AI インフラ・ロボットデータの検索
  4. 04FCC の衛星申請・通知の取得
  5. 05引用と元データセルの照合

活用シーン

  1. 01ISO キュー間のプロジェクト状況の比較
  2. 02ERCOT 前日価格の推移分析
  3. 03州・燃料別の計画発電容量の絞り込み

MCP 対応

Streamable HTTP の MCP サーバーを提供し、クライアントはデータセットの一覧、クエリ条件の確認、データの絞り込み・集計、引用元ファイルとの照合を行えます。

設定

リモートサーバーはインストール不要です。クライアントを選んで設定をコピーするか、ワンクリックで導入できます。

エンドポイントhttps://api.exascale.build/mcp
インストールコマンドをコピー
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

コマンドはターミナルで実行し、JSON は各クライアントの MCP 設定に貼り付けて再起動します。認可が必要なサーバーは初回接続時にログインを求めます。

ツール

66

このツールにパラメーターはありません。

README(原文)English

プロジェクトの README より

この README の日本語訳はまだありません。以下は英語の原文です。日本語の紹介はページ上部をご覧ください。

exascale.build

MCP endpoint: https://api.exascale.build/mcp (streamable HTTP) · Discovery: /.well-known/agent.json · Website: exascale.build · Docs: exascale.build/docs · Pricing: exascale.build/pro

US ISO interconnection queues and cited energy data, over MCP or REST. Also served: EIA power data, ERCOT day-ahead prices, natural gas prices, fuel receipts and plant costs, generator ownership, AI-infrastructure construction, production, and trade, robotics adoption and trade, and FCC satellite filings and notices. Every value returns its source, as_of, and source_url.

Access

25 free queries, no key required. The free queries are one-time, not a daily refill, and cover the latest snapshot of the open data points. After that, a key is $49/mo or $490/yr, with a 7-day full refund.

Send a paid key as Authorization: Bearer <key>, or connect with the personal MCP URL from the welcome email. Querying a past as_of vintage needs a key. These four data points need a key on every query and are not part of the 25 free queries: power.capacity_accreditation_pjm, power.capacity_market_pjm, power.capacity_accreditation_miso, power.capacity_market_miso.

initialize and tools/list do not need a key. Fair-use rate limits still apply.

Connect

Claude Code

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

JSON config

{
  "mcpServers": {
    "exascale": {
      "type": "http",
      "url": "https://api.exascale.build/mcp"
    }
  }
}

For a paid key, add "headers": { "Authorization": "Bearer <key>" }. A personal MCP URL from the welcome email replaces the URL above.

Claude.ai — Settings → Connectors → Add custom connector → https://api.exascale.build/mcp. Set Authentication to None for the free queries. Paid users paste the personal MCP link from the welcome email.

Claude Desktop — Settings → Connectors → Add custom connector → https://api.exascale.build/mcp. Set Authentication to None for the free queries. Paid users paste the personal MCP link from the welcome email. The JSON config above is the same server.

Cursor — Settings → MCP → New MCP server, or ~/.cursor/mcp.json:

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

Paid key:

{
  "mcpServers": {
    "exascale": {
      "url": "https://api.exascale.build/mcp",
      "headers": {
        "Authorization": "Bearer <key>"
      }
    }
  }
}

Cline — MCP Servers → Configure → Remote Servers → transport Streamable HTTP → https://api.exascale.build/mcp. In the MCP settings JSON, set "type": "streamableHttp" (a missing type is treated as legacy SSE):

{
  "mcpServers": {
    "exascale": {
      "type": "streamableHttp",
      "url": "https://api.exascale.build/mcp",
      "disabled": false
    }
  }
}

Add "headers": { "Authorization": "Bearer <key>" } for a paid key.

REST

curl https://api.exascale.build/v1/capabilities
curl -X POST https://api.exascale.build/v1/power/capacity/query \
  -H 'content-type: application/json' \
  -d '{"group_by":["state"],"order_by":"nameplate_mw","top_n":5}'

A paid key is the same Authorization: Bearer <key> header.

Capabilities

Data pointWhat it answersSource
power.capacityOperating, planned, and retired generator capacity (MW)EIA-860M
power.generationNet generation (MWh) by plant, fuel, state, and balancing authorityEIA-923
power.demandHourly electricity demand (MW) by balancing authorityEIA-930
power.demand_rollupPublished US48 and 13-region hourly demand totalsEIA-930
power.retail_salesAnnual retail sales, revenue, and customers by utility, state, and sectorEIA-861
power.capacity_factorGeneration ÷ (operating nameplate × hours)EIA-860M + EIA-923
power.asset_ownershipAnnual owner names and ownership shares by plant and generatorEIA-860
power.fuel_costReceipt-level delivered fuel cost (cents/MMBtu) and quantityEIA-923
power.plant_costsAs-filed large-steam plant capacity, generation, balances, fuel expense, and O&M linesFERC Form 1
natural_gas.pricesDaily Henry Hub spot ($/MMBtu) and monthly state electric-power prices ($/Mcf)EIA
power.interconnection_queueMISO queue — requested MW and statusMISO GI queue
power.interconnection_queue_pjmPJM queue — requested MW and statusPJM New Services queue
power.interconnection_queue_pjm_cyclePJM cluster/cycle grid — cycle phase MWPJM cycle grid
power.interconnection_queue_caisoCAISO queue — requested MW and statusCAISO Public Queue Report
power.interconnection_queue_nyisoNYISO queue — requested MW and statusNYISO queue
power.interconnection_queue_isoneISO-NE queue — requested MW and statusISO-NE IRTT
power.interconnection_queue_ercotERCOT queue — requested MW and statusERCOT GIS report
power.interconnection_queue_sppSPP queue — requested MW and statusSPP GI summary
power.price_ercotERCOT day-ahead settlement-point prices ($/MWh), including hubs such as HB_NORTHERCOT DAM (NP4-190-CD)
power.capacity_accreditation_pjmPJM marginal ELCC class ratings (paid key on every query)PJM
power.capacity_market_pjmPJM RPM clearing prices and cleared UCAP (paid key on every query)PJM
power.capacity_accreditation_misoMISO seasonal class accreditation ratios (paid key on every query)MISO
power.capacity_market_misoMISO PRA seasonal zonal clearing prices (paid key on every query)MISO
ai_infrastructure.constructionPrivate data-center and semiconductor-fab construction spending ($M/month)Census C30
ai_infrastructure.tradeMonthly US chip-import value (HS-8542) by country of originCensus International Trade
ai_infrastructure.equipment_tradeMonthly US chip-making-equipment import value (HS-8486) by country of originCensus International Trade
ai_infrastructure.productionSemiconductor and electronic-component production index and capacity utilization (NAICS 3344)Fed G.17
robotics.tradeMonthly US industrial-robot imports — customs value and robot counts — by country of originCensus International Trade
robotics.adoptionShare of plants using robots, workers exposed, and robotics capex, by industry, state, and plant sizeCensus Industrial Robotic Equipment
space.satellite_filingsFCC space-station filings back to the 1960s (applicant, type, status, lifecycle dates). New-filing intake ends at the ICFS cutover (~mid-2025).FCC IBFS
space.satellite_noticesFCC weekly satellite public notices since the ICFS cutover: applications accepted for filing and actions takenFCC Space Bureau

Queue MW is requested capacity, not built capacity. The seven ISO queues are separate data points; methodologies differ, and they are not a national total.

66 read-only tools: list_capabilities_v1, a describe_* / query_* pair for each data point, describe_capability_v1 / query_capability_v1 (any capability by id, including ones added after a client cached its tool list), and get_source_evidence_v1. get_source_evidence_v1 re-opens the raw government file, re-checks its SHA-256, and returns the exact cell.

Where the source provides them, rows share anchors such as state, county_fips, and eia_plant_id. Field reference: exascale.build/docs.

Agent flow

discover → describe → query → verify

  1. discover — list_capabilities_v1 lists the data points.
  2. describe — the matching describe_* tool returns filters, groupings, measures, and what that data point does not answer.
  3. query — filters plus group_by, order_by, and top_n. Every value includes source, as_of, and source_url.
  4. verify — pass the citation to get_source_evidence_v1. It re-opens the raw file, re-checks the SHA-256, and returns the exact cell.

Example questions

  1. How much of PJM's interconnection queue has withdrawn vs reached service?
  2. How did ERCOT HB_NORTH day-ahead prices compare with the same week last year?
  3. What are the top 5 states for planned capacity by fuel?

Each figure comes back with its source, as_of, and source_url. Pass that citation to get_source_evidence_v1 to read the exact source cell.

Links

Website exascale.build · Docs /docs · Pricing /pro · Privacy /privacy · Terms /terms · Official MCP Registry: build.exascale/osint · Contact: [email protected]

コメント

MCP は初めてですか?

プロトコルの概要から最初のサーバーの導入まで、よくある疑問にまとめて答えます。

AI アプリケーションが外部のツールやデータソースに統一的な方法で接続するためのオープンなプロトコルです。クライアントはモデルとの対話を担い、MCP サーバーはツール・リソース・プロンプトテンプレートを提供します。標準メッセージでやり取りするため、1 つのサーバーを複数のクライアントで再利用できます。