mcp-registry/work.latlng.mcp/latlng/find_nearby_places / alternatives

Live alternatives to mcp-registry/work.latlng.mcp/latlng/find_nearby_places

The best live alternatives to mcp-registry/work.latlng.mcp/latlng/find_nearby_places right now are mcp-registry/io.github.pipeworx-io/geonames/get_nearby, mcp-registry/io.github.pipeworx-io/foursquare/nearby_places, mcp-registry/io.github.mcflamingo/local-intel/local_intel_nearby, mcp-registry/io.github.pipeworx-io/geoapify/places, mcp-registry/io.github.pipeworx-io/overpass/pois_near — capability-matched and ranked by current reliability. mcp-registry/work.latlng.mcp/latlng/find_nearby_places itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/geonames/get_nearby	io.github.pipeworx-io/geonames	live status →
mcp-registry/io.github.pipeworx-io/foursquare/nearby_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/io.github.mcflamingo/local-intel/local_intel_nearby	io.github.MCFLAMINGO/local-intel	live status →
mcp-registry/io.github.pipeworx-io/geoapify/places	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.github.pipeworx-io/overpass/pois_near	io.github.pipeworx-io/overpass	live status →
mcp-registry/io.github.tickadoo/tickadoo-mcp/find_nearby_experiences	io.github.tickadoo/tickadoo-mcp	live status →
mcp-registry/io.github.srivastsh/muni-mcp/muni_nearby_stops	io.github.srivastsh/muni-mcp	live status →
mcp-registry/net.smartapis/products-watch/smartagent_places_nearby	net.smartapis/products-watch	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search	io.github.Vee3io/vee3	live status →
mcp-registry/io.github.pipeworx-io/predicthq/nearby_events	io.github.pipeworx-io/predicthq	live status →
mcp-registry/io.github.pipeworx-io/ebird/nearby_observations	io.github.pipeworx-io/ebird	live status →
mcp-registry/io.github.pipeworx-io/foursquare/search_places	io.github.pipeworx-io/foursquare	live status →

FAQ

What is the best alternative to mcp-registry/work.latlng.mcp/latlng/find_nearby_places?

mcp-registry/io.github.pipeworx-io/geonames/get_nearby 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.mcflamingo/local-intel/local_intel_nearby, mcp-registry/io.github.pipeworx-io/geoapify/places, mcp-registry/io.github.pipeworx-io/overpass/pois_near. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/work.latlng.mcp/latlng/find_nearby_places down right now?

mcp-registry/work.latlng.mcp/latlng/find_nearby_places's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fwork.latlng.mcp%2Flatlng%2Ffind_nearby_places.

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%2Fwork.latlng.mcp%2Flatlng%2Ffind_nearby_places or MCP find_alternatives. Check mcp-registry/work.latlng.mcp/latlng/find_nearby_places's live status: https://glimind.com/tool/mcp-registry/work.latlng.mcp/latlng/find_nearby_places.