mcp-registry/io.github.pipeworx-io/openchargemap/find_stations / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/openchargemap/find_stations

The best live alternatives to mcp-registry/io.github.pipeworx-io/openchargemap/find_stations right now are mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/ev_charging, mcp-registry/com.parkinzi/parkinzi/find_ev_chargers, mcp-registry/dev.infranode/infranode/charging, mcp-registry/app.cardog/mcp/search_electric_stations, mcp-registry/io.github.blackboxfoundry/livedatalink/nrel_alt_fuel_stations — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/openchargemap/find_stations itself is currently "healthy".

alternative	server
mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/ev_charging	io.github.digitalweb33333-creator/x402-endpoints	live status →
mcp-registry/com.parkinzi/parkinzi/find_ev_chargers	com.parkinzi/parkinzi	live status →
mcp-registry/dev.infranode/infranode/charging	dev.infranode/infranode	live status →
mcp-registry/app.cardog/mcp/search_electric_stations	app.cardog/mcp	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/nrel_alt_fuel_stations	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/meteostat/find_stations	io.github.pipeworx-io/meteostat	live status →
mcp-registry/com.parkinzi/parkinzi/search_parking_spots	com.parkinzi/parkinzi	live status →
mcp-registry/work.latlng.mcp/latlng/find_nearby_places	work.latlng.mcp/latlng	live status →
mcp-registry/io.github.pipeworx-io/openaq/find_stations	io.github.pipeworx-io/openaq	live status →
mcp-registry/io.github.pipeworx-io/geonames/get_nearby	io.github.pipeworx-io/geonames	live status →
mcp-registry/dev.infranode/infranode/stations	dev.infranode/infranode	live status →
mcp-registry/io.github.pipeworx-io/transit-land/search_stops	io.github.pipeworx-io/transit-land	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/openchargemap/find_stations?

mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/ev_charging is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.parkinzi/parkinzi/find_ev_chargers, mcp-registry/dev.infranode/infranode/charging, mcp-registry/app.cardog/mcp/search_electric_stations, mcp-registry/io.github.blackboxfoundry/livedatalink/nrel_alt_fuel_stations. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/openchargemap/find_stations down right now?

mcp-registry/io.github.pipeworx-io/openchargemap/find_stations's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fopenchargemap%2Ffind_stations.

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%2Fopenchargemap%2Ffind_stations or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/openchargemap/find_stations's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/openchargemap/find_stations.