mcp-registry/com.mydriverparis/booking/resolve_location / alternatives

Live alternatives to mcp-registry/com.mydriverparis/booking/resolve_location

The best live alternatives to mcp-registry/com.mydriverparis/booking/resolve_location right now are mcp-registry/io.github.pipeworx-io/openweather/geocode, mcp-registry/io.github.pipeworx-io/maptiler/geocode, mcp-registry/io.github.pipeworx-io/openrouteservice/geocode_search, mcp-registry/io.github.pipeworx-io/open-meteo/geocode, mcp-registry/io.github.pipeworx-io/photon/search — capability-matched and ranked by current reliability. mcp-registry/com.mydriverparis/booking/resolve_location itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/openweather/geocode	io.github.pipeworx-io/openweather	live status →
mcp-registry/io.github.pipeworx-io/maptiler/geocode	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/geocode_search	io.github.pipeworx-io/openrouteservice	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/photon/search	io.github.pipeworx-io/photon	live status →
mcp-registry/io.github.pipeworx-io/geoapify/geocode	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.github.pipeworx-io/tomtom/reverse_geocode	io.github.pipeworx-io/tomtom	live status →
mcp-registry/io.github.pipeworx-io/nominatim/search_address	io.github.pipeworx-io/nominatim	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/geoapify/reverse_geocode	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.github.pipeworx-io/tomtom/geocode	io.github.pipeworx-io/tomtom	live status →
mcp-registry/work.latlng.mcp/latlng/reverse_geocode	work.latlng.mcp/latlng	live status →

FAQ

What is the best alternative to mcp-registry/com.mydriverparis/booking/resolve_location?

mcp-registry/io.github.pipeworx-io/openweather/geocode is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/maptiler/geocode, mcp-registry/io.github.pipeworx-io/openrouteservice/geocode_search, mcp-registry/io.github.pipeworx-io/open-meteo/geocode, mcp-registry/io.github.pipeworx-io/photon/search. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.mydriverparis/booking/resolve_location down right now?

mcp-registry/com.mydriverparis/booking/resolve_location's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.mydriverparis%2Fbooking%2Fresolve_location.

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%2Fcom.mydriverparis%2Fbooking%2Fresolve_location or MCP find_alternatives. Check mcp-registry/com.mydriverparis/booking/resolve_location's live status: https://glimind.com/tool/mcp-registry/com.mydriverparis/booking/resolve_location.