mcp-registry/io.github.pipeworx-io/geoapify/places / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/geoapify/places

The best live alternatives to mcp-registry/io.github.pipeworx-io/geoapify/places right now are mcp-registry/io.github.pipeworx-io/tomtom/search_poi, mcp-registry/io.github.pipeworx-io/foursquare/nearby_places, mcp-registry/io.github.pipeworx-io/google_maps/maps_place_search, mcp-registry/work.latlng.mcp/latlng/find_nearby_places, mcp-registry/io.github.pipeworx-io/foursquare/search_places — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/geoapify/places itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/tomtom/search_poi	io.github.pipeworx-io/tomtom	live status →
mcp-registry/io.github.pipeworx-io/foursquare/nearby_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_place_search	io.github.pipeworx-io/google_maps	live status →
mcp-registry/work.latlng.mcp/latlng/find_nearby_places	work.latlng.mcp/latlng	live status →
mcp-registry/io.github.pipeworx-io/foursquare/search_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/io.github.eugenelabonarsky/votura-tours/search_places	io.github.eugenelabonarsky/votura-tours	live status →
mcp-registry/work.latlng.mcp/latlng/search_places	work.latlng.mcp/latlng	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/geocode_search	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search	io.github.Vee3io/vee3	live status →
mcp-registry/io.github.pipeworx-io/geonames/get_nearby	io.github.pipeworx-io/geonames	live status →
mcp-registry/io.github.pipeworx-io/overpass/pois_near	io.github.pipeworx-io/overpass	live status →
mcp-registry/work.latlng.mcp/latlng/list_place_categories	work.latlng.mcp/latlng	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/geoapify/places?

mcp-registry/io.github.pipeworx-io/tomtom/search_poi is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/foursquare/nearby_places, mcp-registry/io.github.pipeworx-io/google_maps/maps_place_search, mcp-registry/work.latlng.mcp/latlng/find_nearby_places, mcp-registry/io.github.pipeworx-io/foursquare/search_places. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/geoapify/places down right now?

mcp-registry/io.github.pipeworx-io/geoapify/places's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fgeoapify%2Fplaces.

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%2Fgeoapify%2Fplaces or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/geoapify/places's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/geoapify/places.