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

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

The best live alternatives to mcp-registry/io.github.pipeworx-io/geonames/search_geonames right now are mcp-registry/io.github.wellknownmcp/ia-asso/search_near_location, mcp-registry/io.github.pipeworx-io/nominatim/search_address, mcp-registry/io.github.pipeworx-io/openrouteservice/geocode_search, mcp-registry/it.cup24/availability/search_suggest_city, mcp-registry/io.github.pipeworx-io/open-meteo/geocode — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/geonames/search_geonames itself is currently "healthy".

alternative	server
mcp-registry/io.github.wellknownmcp/ia-asso/search_near_location	io.github.wellknownmcp/ia-asso	live status →
mcp-registry/io.github.pipeworx-io/nominatim/search_address	io.github.pipeworx-io/nominatim	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/geocode_search	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/it.cup24/availability/search_suggest_city	it.cup24/availability	live status →
mcp-registry/io.github.pipeworx-io/open-meteo/geocode	io.github.pipeworx-io/open-meteo	live status →
mcp-registry/io.github.tickadoo/tickadoo-mcp/search_local_experiences	io.github.tickadoo/tickadoo-mcp	live status →
mcp-registry/io.github.pipeworx-io/ban-fr/reverse_geocode	io.github.pipeworx-io/ban-fr	live status →
mcp-registry/io.github.pipeworx-io/openweather/geocode	io.github.pipeworx-io/openweather	live status →
mcp-registry/io.github.pipeworx-io/foursquare/search_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/io.github.pipeworx-io/photon/search	io.github.pipeworx-io/photon	live status →
mcp-registry/io.github.dynamitecircle/dc/places_search	io.github.dynamitecircle/dc	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search	io.github.Vee3io/vee3	live status →

FAQ

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

mcp-registry/io.github.wellknownmcp/ia-asso/search_near_location is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/nominatim/search_address, mcp-registry/io.github.pipeworx-io/openrouteservice/geocode_search, mcp-registry/it.cup24/availability/search_suggest_city, mcp-registry/io.github.pipeworx-io/open-meteo/geocode. Glimind ranks alternatives by semantic similarity and live health.

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

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

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