mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search / alternatives

Live alternatives to mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search

The best live alternatives to mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search right now are mcp-registry/io.github.pipeworx-io/google_maps/maps_place_search, mcp-registry/io.github.pipeworx-io/foursquare/nearby_places, mcp-registry/work.latlng.mcp/latlng/find_nearby_places, mcp-registry/io.github.dynamitecircle/dc/places_search, mcp-registry/io.github.pipeworx-io/geonames/get_nearby — capability-matched and ranked by current reliability. mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/google_maps/maps_place_search	io.github.pipeworx-io/google_maps	live status →
mcp-registry/io.github.pipeworx-io/foursquare/nearby_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/work.latlng.mcp/latlng/find_nearby_places	work.latlng.mcp/latlng	live status →
mcp-registry/io.github.dynamitecircle/dc/places_search	io.github.dynamitecircle/dc	live status →
mcp-registry/io.github.pipeworx-io/geonames/get_nearby	io.github.pipeworx-io/geonames	live status →
mcp-registry/com.eventmatey.mcp/event-discovery/search_events_nearby	com.eventmatey.mcp/event-discovery	live status →
mcp-registry/io.github.pipeworx-io/foursquare/search_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/io.github.pipeworx-io/geoapify/places	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_place_details	io.github.pipeworx-io/google_maps	live status →
mcp-registry/com.pangolinfo/amazon-mcp/search_local_maps	com.pangolinfo/amazon-mcp	live status →
mcp-registry/app.nausika/mcp/nausika_search_places	app.nausika/mcp	live status →
mcp-registry/io.github.pipeworx-io/serper/places	io.github.pipeworx-io/serper	live status →

FAQ

What is the best alternative to mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search?

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

Is mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search down right now?

mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.vee3io%2Fvee3%2Fgoogle-maps.nearby_search.

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.vee3io%2Fvee3%2Fgoogle-maps.nearby_search or MCP find_alternatives. Check mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search's live status: https://glimind.com/tool/mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search.