exascale.build
MCP server by exascale.build · mcp
Use these tools to discover, query, and verify source-cited OSINT data. Call list_capabilities_v1 before querying an unfamiliar domain, call the schema tool to inspect valid filters, and use get_source_evidence_v1 to prove a cited source row. To verify a number against its source, call get_source_evidence_v1 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 get_source_evidence_v1 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). Bu…
Endpoint: https://api.exascale.build/mcp
Verification: observed. Source: crawl.
Capabilities (66)
- list_capabilities_v1
- get_source_evidence_v1
- describe_capability_v1
- query_capability_v1
- describe_power_capacity_v1
- query_power_capacity_v1
- describe_power_generation_v1
- query_power_generation_v1
- describe_power_asset_ownership_v1
- query_power_asset_ownership_v1
- describe_power_fuel_cost_v1
- query_power_fuel_cost_v1
- describe_power_plant_costs_v1
- query_power_plant_costs_v1
- describe_natural_gas_prices_v1
- query_natural_gas_prices_v1
- describe_power_demand_v1
- query_power_demand_v1
- describe_power_demand_rollup_v1
- query_power_demand_rollup_v1
- describe_power_retail_sales_v1
- query_power_retail_sales_v1
- describe_power_interconnection_queue_v1
- query_power_interconnection_queue_v1
- describe_power_interconnection_queue_pjm_v1