mcp-registry/io.github.pipeworx-io/geonames/get_nearby / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/geonames/get_nearby

The best live alternatives to mcp-registry/io.github.pipeworx-io/geonames/get_nearby right now are mcp-registry/work.latlng.mcp/latlng/find_nearby_places, 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/predicthq/nearby_events, mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/geonames/get_nearby itself is currently "healthy".

alternative	server
mcp-registry/work.latlng.mcp/latlng/find_nearby_places	work.latlng.mcp/latlng	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/predicthq/nearby_events	io.github.pipeworx-io/predicthq	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search	io.github.Vee3io/vee3	live status →
mcp-registry/io.github.vbhjckfd/timetable-api-node/get_nearby_vehicles	io.github.vbhjckfd/timetable-api-node	live status →
mcp-registry/com.moltravel/travel/airports_near	com.moltravel/travel	live status →
mcp-registry/io.github.pipeworx-io/entreprises-fr/nearby	io.github.pipeworx-io/entreprises-fr	live status →
mcp-registry/io.github.pipeworx-io/geoapify/places	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.tooloracle/hoteloracle/nearby_attractions	io.tooloracle/hoteloracle	live status →
mcp-registry/io.github.pipeworx-io/foursquare/search_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/io.github.pipeworx-io/gbif/occurrences_near	io.github.pipeworx-io/gbif	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/geonames/get_nearby?

mcp-registry/work.latlng.mcp/latlng/find_nearby_places 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/predicthq/nearby_events, mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/geonames/get_nearby down right now?

mcp-registry/io.github.pipeworx-io/geonames/get_nearby's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fgeonames%2Fget_nearby.

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%2Fgeonames%2Fget_nearby or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/geonames/get_nearby's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/geonames/get_nearby.