mcp-registry/io.github.cturkieh/france-data-mcp/geocode_adresse / alternatives

Live alternatives to mcp-registry/io.github.cturkieh/france-data-mcp/geocode_adresse

The best live alternatives to mcp-registry/io.github.cturkieh/france-data-mcp/geocode_adresse right now are mcp-registry/io.github.pipeworx-io/ban-fr/geocode, mcp-registry/io.github.pipeworx-io/ban-fr/reverse_geocode, mcp-registry/io.github.pipeworx-io/tomtom/geocode, mcp-registry/io.github.foundrynet/foundrynet-geo/geocode, mcp-registry/io.github.pipeworx-io/open-meteo/geocode — capability-matched and ranked by current reliability. mcp-registry/io.github.cturkieh/france-data-mcp/geocode_adresse itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/ban-fr/geocode	io.github.pipeworx-io/ban-fr	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/tomtom/geocode	io.github.pipeworx-io/tomtom	live status →
mcp-registry/io.github.foundrynet/foundrynet-geo/geocode	io.github.FoundryNet/foundrynet-geo	live status →
mcp-registry/io.github.pipeworx-io/open-meteo/geocode	io.github.pipeworx-io/open-meteo	live status →
mcp-registry/io.github.pipeworx-io/openweather/geocode	io.github.pipeworx-io/openweather	live status →
mcp-registry/io.github.xogz3/botoi-mcp/lookup_address_validate	io.github.XogZ3/botoi-mcp	live status →
mcp-registry/io.github.pipeworx-io/maptiler/geocode	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.pipeworx-io/geoapify/geocode	io.github.pipeworx-io/geoapify	live status →
mcp-registry/com.mydriverparis/booking/resolve_location	com.mydriverparis/booking	live status →
mcp-registry/io.github.pipeworx-io/geo/geocode	io.github.pipeworx-io/geo	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_geocode	io.github.pipeworx-io/google_maps	live status →

FAQ

What is the best alternative to mcp-registry/io.github.cturkieh/france-data-mcp/geocode_adresse?

mcp-registry/io.github.pipeworx-io/ban-fr/geocode is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/ban-fr/reverse_geocode, mcp-registry/io.github.pipeworx-io/tomtom/geocode, mcp-registry/io.github.foundrynet/foundrynet-geo/geocode, mcp-registry/io.github.pipeworx-io/open-meteo/geocode. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.cturkieh/france-data-mcp/geocode_adresse down right now?

mcp-registry/io.github.cturkieh/france-data-mcp/geocode_adresse's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.cturkieh%2Ffrance-data-mcp%2Fgeocode_adresse.

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.cturkieh%2Ffrance-data-mcp%2Fgeocode_adresse or MCP find_alternatives. Check mcp-registry/io.github.cturkieh/france-data-mcp/geocode_adresse's live status: https://glimind.com/tool/mcp-registry/io.github.cturkieh/france-data-mcp/geocode_adresse.