mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point

The best live alternatives to mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point right now are mcp-registry/io.github.pipeworx-io/postcodes/lookup_postcode, mcp-registry/io.github.pipeworx-io/postcodes/random_postcode, mcp-registry/cloud.dchub/mcp-server/get_grid_scoreboard, mcp-registry/io.github.pipeworx-io/carbon/get_regional_intensity, mcp-registry/cloud.dchub/mcp-server/get_grid_intelligence — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/postcodes/lookup_postcode	io.github.pipeworx-io/postcodes	live status →
mcp-registry/io.github.pipeworx-io/postcodes/random_postcode	io.github.pipeworx-io/postcodes	live status →
mcp-registry/cloud.dchub/mcp-server/get_grid_scoreboard	cloud.dchub/mcp-server	live status →
mcp-registry/io.github.pipeworx-io/carbon/get_regional_intensity	io.github.pipeworx-io/carbon	live status →
mcp-registry/cloud.dchub/mcp-server/get_grid_intelligence	cloud.dchub/mcp-server	live status →
mcp-registry/xyz.lonestaroracle/mcp-server/grid_intelligence	xyz.lonestaroracle/mcp-server	live status →
mcp-registry/cloud.dchub/mcp-server/get_grid_data	cloud.dchub/mcp-server	live status →
mcp-registry/io.github.pipeworx-io/landregistry-uk/lookup_postcode	io.github.pipeworx-io/landregistry-uk	live status →
mcp-registry/io.github.pipeworx-io/postcodes/nearest_postcodes	io.github.pipeworx-io/postcodes	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/grid_carbon	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/dev.infranode/infranode/power_load	dev.infranode/infranode	live status →
mcp-registry/io.github.pipeworx-io/pirate-weather/forecast_grid	io.github.pipeworx-io/pirate-weather	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point?

mcp-registry/io.github.pipeworx-io/postcodes/lookup_postcode is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/postcodes/random_postcode, mcp-registry/cloud.dchub/mcp-server/get_grid_scoreboard, mcp-registry/io.github.pipeworx-io/carbon/get_regional_intensity, mcp-registry/cloud.dchub/mcp-server/get_grid_intelligence. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point down right now?

mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Foctopus-energy%2Fgrid_supply_point.

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%2Fio.github.pipeworx-io%2Foctopus-energy%2Fgrid_supply_point or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point.