mcp-registry/io.github.pipeworx-io/nasa-power/regional_data / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/nasa-power/regional_data

The best live alternatives to mcp-registry/io.github.pipeworx-io/nasa-power/regional_data right now are mcp-registry/io.github.pipeworx-io/airnow/observations_in_bbox, mcp-registry/io.tinyfn/tinyfn/bounding_box, mcp-registry/io.github.pipeworx-io/opencellid/cells_in_area, mcp-registry/com.daedalmap/county-map/get_boundary, mcp-registry/com.daedalmap/geocoding/get_boundary — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/nasa-power/regional_data itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/airnow/observations_in_bbox	io.github.pipeworx-io/airnow	live status →
mcp-registry/io.tinyfn/tinyfn/bounding_box	io.tinyfn/tinyfn	live status →
mcp-registry/io.github.pipeworx-io/opencellid/cells_in_area	io.github.pipeworx-io/opencellid	live status →
mcp-registry/com.daedalmap/county-map/get_boundary	com.daedalmap/county-map	live status →
mcp-registry/com.daedalmap/geocoding/get_boundary	com.daedalmap/geocoding	live status →
mcp-registry/com.daedalmap/boundaries/get_boundary	com.daedalmap/boundaries	live status →
mcp-registry/io.github.pipeworx-io/overpass/places_in_bbox	io.github.pipeworx-io/overpass	live status →
mcp-registry/io.github.pipeworx-io/cdec-ca/hourly_data	io.github.pipeworx-io/cdec-ca	live status →
mcp-registry/io.github.pipeworx-io/opentopography/dem	io.github.pipeworx-io/opentopography	live status →
mcp-registry/io.github.pipeworx-io/geoboundaries/get_boundaries	io.github.pipeworx-io/geoboundaries	live status →
mcp-registry/build.exascale/osint/query_power_demand_rollup_v1	build.exascale/osint	live status →
mcp-registry/space.0/space0/find_clear_region	space.0/space0	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/nasa-power/regional_data?

mcp-registry/io.github.pipeworx-io/airnow/observations_in_bbox is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.tinyfn/tinyfn/bounding_box, mcp-registry/io.github.pipeworx-io/opencellid/cells_in_area, mcp-registry/com.daedalmap/county-map/get_boundary, mcp-registry/com.daedalmap/geocoding/get_boundary. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/nasa-power/regional_data down right now?

mcp-registry/io.github.pipeworx-io/nasa-power/regional_data's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fnasa-power%2Fregional_data.

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%2Fnasa-power%2Fregional_data or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/nasa-power/regional_data's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/nasa-power/regional_data.