mcp-registry/build.exascale/osint/query_power_demand_v1 / alternatives

Live alternatives to mcp-registry/build.exascale/osint/query_power_demand_v1

The best live alternatives to mcp-registry/build.exascale/osint/query_power_demand_v1 right now are mcp-registry/io.github.pipeworx-io/elexon/system_demand, mcp-registry/io.github.pipeworx-io/entso-e/actual_load, mcp-registry/dev.infranode/infranode/power_load, mcp-registry/io.github.pipeworx-io/us-iso-grid/caiso_demand, mcp-registry/ai.dynamicfeed/dynamic-feed/energy_grid — capability-matched and ranked by current reliability. mcp-registry/build.exascale/osint/query_power_demand_v1 itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/elexon/system_demand	io.github.pipeworx-io/elexon	live status →
mcp-registry/io.github.pipeworx-io/entso-e/actual_load	io.github.pipeworx-io/entso-e	live status →
mcp-registry/dev.infranode/infranode/power_load	dev.infranode/infranode	live status →
mcp-registry/io.github.pipeworx-io/us-iso-grid/caiso_demand	io.github.pipeworx-io/us-iso-grid	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/energy_grid	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.deepakumarsubbian/orbiteos/query_energy_totals	io.github.DeepakumarSubbian/orbiteos	live status →
mcp-registry/cloud.dchub/mcp-server/get_grid_intelligence	cloud.dchub/mcp-server	live status →
mcp-registry/io.github.yuzu-hub/wiring-diagram-mcp/calculate_power_budget	io.github.YUZU-Hub/wiring-diagram-mcp	live status →
mcp-registry/cloud.dchub/mcp-server/get_grid_data	cloud.dchub/mcp-server	live status →
mcp-registry/com.adbutler/mcp-server/get_demand_source_report	com.adbutler/mcp-server	live status →
pulsemcp/adbutler/get_demand_source_report	AdButler	live status →
mcp-registry/io.github.pipeworx-io/energy-charts/total_power	io.github.pipeworx-io/energy-charts	live status →

FAQ

What is the best alternative to mcp-registry/build.exascale/osint/query_power_demand_v1?

mcp-registry/io.github.pipeworx-io/elexon/system_demand is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/entso-e/actual_load, mcp-registry/dev.infranode/infranode/power_load, mcp-registry/io.github.pipeworx-io/us-iso-grid/caiso_demand, mcp-registry/ai.dynamicfeed/dynamic-feed/energy_grid. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/build.exascale/osint/query_power_demand_v1 down right now?

mcp-registry/build.exascale/osint/query_power_demand_v1's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fbuild.exascale%2Fosint%2Fquery_power_demand_v1.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fbuild.exascale%2Fosint%2Fquery_power_demand_v1 or MCP find_alternatives. Check mcp-registry/build.exascale/osint/query_power_demand_v1's live status: https://glimind.com/tool/mcp-registry/build.exascale/osint/query_power_demand_v1.