Home / MCP registry index / build.exascale/osint
exascale.build
build.exascale/osint in the official MCP registry.
Endpoint https://api.exascale.build/mcp.
The registry describes it as: US ISO interconnection queues and cited energy data. 25 free queries, then $49/mo or $490/yr.
We read its 66 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
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 query_power_interconnection_queue_pjm_v1 describe_power_interconnection_queue_pjm_cycle_v1 query_power_interconnection_queue_pjm_cycle_v1 describe_power_interconnection_queue_caiso_v1 query_power_interconnection_queue_caiso_v1 describe_power_interconnection_queue_nyiso_v1 query_power_interconnection_queue_nyiso_v1 describe_power_interconnection_queue_isone_v1 query_power_interconnection_queue_isone_v1 describe_power_interconnection_queue_ercot_v1 query_power_interconnection_queue_ercot_v1 describe_power_interconnection_queue_spp_v1 query_power_interconnection_queue_spp_v1 describe_power_price_ercot_v1 query_power_price_ercot_v1 describe_power_capacity_accreditation_pjm_v1 query_power_capacity_accreditation_pjm_v1 describe_power_capacity_market_pjm_v1 query_power_capacity_market_pjm_v1 describe_power_capacity_accreditation_miso_v1 query_power_capacity_accreditation_miso_v1 describe_power_capacity_market_miso_v1 query_power_capacity_market_miso_v1 describe_ai_infrastructure_construction_v1 query_ai_infrastructure_construction_v1 describe_ai_infrastructure_trade_v1 query_ai_infrastructure_trade_v1 describe_ai_infrastructure_equipment_trade_v1 query_ai_infrastructure_equipment_trade_v1 describe_ai_infrastructure_production_v1 query_ai_infrastructure_production_v1 describe_robotics_trade_v1 query_robotics_trade_v1 describe_robotics_adoption_v1 query_robotics_adoption_v1 and 6 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/build-exascale-osint)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.