exascale.build

Source-cited US power data, built for agents

Agent-first, source-cited data layer for the US power system. Query operating, planned, and retired generation capacity (EIA-860M), net generation (EIA-923), and capacity factor — over MCP or REST.

MCP connector

Server URL: https://api.exascale.build/mcp
Login: None
Protocol: MCP 2026-07-28
Instructions: Use these tools to discover, query, and verify source-cited OSINT data. Call before querying an unfamiliar domain, call the schema tool to inspect valid filters, and use to prove a cited source row. To verify a number against its source, call with the citation — it re-opens the raw government file server-side, re-checks its SHA-256, and returns the exact raw cell. Do NOT download the source files yourself: several publishers bot-wall their files (WAF / CDN challenges) so a direct fetch fails, and it is unnecessary — the citation already round-trips to the raw cell. Only report a hash match that actually returned (hash_verified: true); never claim a SHA-256 you did not obtain from it. When a question names neither MW nor MWh and no verb picks one — e.g. "how much gas power does Texas have?" — surface both readings, named: installed capacity (MW, a stock) and electricity generated (MWh, a flow). But when the wording already picks one (installed/capacity/can-produce means MW; generated/produced/supplied means MWh), answer that reading alone — do not query the other. Ground every quantitative or comparative claim in a query result — rankings and shares are one cheap call away (group_by + order_by, top_n). If you add context these tools did not return, say so explicitly. NEVER state that this server lacks a capability based on your tool list or prior knowledge of exascale.build — tool lists are cached by clients and this surface grows (power, AI infrastructure, robotics, and space are all served today). Before saying a capability is not available, call and check; if it names a capability with no matching tool in your tool list, the capability is still fully reachable: call then with the capability id. Deny only what itself does not name. Access is 25 free queries, then $49/mo or $490/yr (https://exascale.build/pro). The first 10 need no key; the next 15 come with a free key sent to an email entered at https://exascale.build/free. The live core is US ISO interconnection queues and cited energy data.

Tools

Reads data66

Skills

None in the store listings or on the server

MCP connector

Server URL

https://api.exascale.build/mcp

None

Protocol

MCP 2026-07-28

Instructions

Use these tools to discover, query, and verify source-cited OSINT data. Call before querying an unfamiliar domain, call the schema tool to inspect valid filters, and use to prove a cited source row. To verify a number against its source, call with the citation — it re-opens the raw government file server-side, re-checks its SHA-256, and returns the exact raw cell. Do NOT download the source files yourself: several publishers bot-wall their files (WAF / CDN challenges) so a direct fetch fails, and it is unnecessary — the citation already round-trips to the raw cell. Only report a hash match that actually returned (hash_verified: true); never claim a SHA-256 you did not obtain from it. When a question names neither MW nor MWh and no verb picks one — e.g. "how much gas power does Texas have?" — surface both readings, named: installed capacity (MW, a stock) and electricity generated (MWh, a flow). But when the wording already picks one (installed/capacity/can-produce means MW; generated/produced/supplied means MWh), answer that reading alone — do not query the other. Ground every quantitative or comparative claim in a query result — rankings and shares are one cheap call away (group_by + order_by, top_n). If you add context these tools did not return, say so explicitly. NEVER state that this server lacks a capability based on your tool list or prior knowledge of exascale.build — tool lists are cached by clients and this surface grows (power, AI infrastructure, robotics, and space are all served today). Before saying a capability is not available, call and check; if it names a capability with no matching tool in your tool list, the capability is still fully reachable: call then with the capability id. Deny only what itself does not name. Access is 25 free queries, then $49/mo or $490/yr (https://exascale.build/pro). The first 10 need no key; the next 15 come with a free key sent to an email entered at https://exascale.build/free. The live core is US ISO interconnection queues and cited energy data.

Tools