exascale.build
MCP server · api.exascale.build · found in a public registry · checked since 2026-10-17
Live, handshake completed · latest check
GET https://api.exascale.build/mcpThe name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
3 passed, 0 failed, 27 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-19 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-19 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-19 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
describe_ai_infrastructure_construction_v1describe_ai_infrastructure_equipment_trade_v1describe_ai_infrastructure_production_v1describe_ai_infrastructure_trade_v1describe_capability_v1describe_capacity_factor_v1describe_natural_gas_prices_v1describe_power_asset_ownership_v1describe_power_capacity_accreditation_miso_v1describe_power_capacity_accreditation_pjm_v1describe_power_capacity_market_miso_v1describe_power_capacity_market_pjm_v1describe_power_capacity_v1describe_power_demand_rollup_v1describe_power_demand_v1describe_power_fuel_cost_v1describe_power_generation_v1describe_power_interconnection_queue_caiso_v1describe_power_interconnection_queue_ercot_v1describe_power_interconnection_queue_isone_v1describe_power_interconnection_queue_nyiso_v1describe_power_interconnection_queue_pjm_cycle_v1describe_power_interconnection_queue_pjm_v1describe_power_interconnection_queue_spp_v1describe_power_interconnection_queue_v1describe_power_plant_costs_v1describe_power_price_ercot_v1describe_power_retail_sales_v1describe_robotics_adoption_v1describe_robotics_trade_v1describe_space_satellite_filings_v1describe_space_satellite_notices_v1get_source_evidence_v1list_capabilities_v1query_ai_infrastructure_construction_v1query_ai_infrastructure_equipment_trade_v1query_ai_infrastructure_production_v1query_ai_infrastructure_trade_v1query_capability_v1query_capacity_factor_v1+26
- Tools
- 66
- This list since
- 2026-10-19
- First listed to us
- 2026-10-19
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/1); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Maps, places and weather / Energy and fuel data (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/5): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Live, MCP endpoint answered HTTP 200 | 359 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 406 | 236 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 406 | 233 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/1) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
- Limited evidence: monitored for 3 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_a0ab4af7691f0f99