mcp-registry/com.googleapis.mapstools/mcp/resolve_names / alternatives

Live alternatives to mcp-registry/com.googleapis.mapstools/mcp/resolve_names

The best live alternatives to mcp-registry/com.googleapis.mapstools/mcp/resolve_names right now are mcp-registry/com.mydriverparis/booking/resolve_location, mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search, mcp-registry/io.github.pipeworx-io/openweather/geocode, mcp-registry/io.github.vee3io/vee3/google-maps.search, mcp-registry/me.foodnear/foodnear-me/search_restaurants — capability-matched and ranked by current reliability. mcp-registry/com.googleapis.mapstools/mcp/resolve_names itself is currently "healthy".

alternativeserver
mcp-registry/com.mydriverparis/booking/resolve_locationcom.mydriverparis/bookinglive status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_searchio.github.Vee3io/vee3live status →
mcp-registry/io.github.pipeworx-io/openweather/geocodeio.github.pipeworx-io/openweatherlive status →
mcp-registry/io.github.vee3io/vee3/google-maps.searchio.github.Vee3io/vee3live status →
mcp-registry/me.foodnear/foodnear-me/search_restaurantsme.foodnear/foodnear-melive status →
mcp-registry/io.github.pipeworx-io/photon/searchio.github.pipeworx-io/photonlive status →
mcp-registry/com.thenextgennexus/enterprise-mcp-gateway/google-maps__search_local_businessescom.thenextgennexus/enterprise-mcp-gatewaylive status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_place_searchio.github.pipeworx-io/google_mapslive status →
mcp-registry/io.github.vee3io/vee3/google-maps.place_detailsio.github.Vee3io/vee3live status →
mcp-registry/com.pangolinfo/amazon-mcp/search_local_mapscom.pangolinfo/amazon-mcplive status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_place_detailsio.github.pipeworx-io/google_mapslive status →
mcp-registry/io.github.dynamitecircle/dc/places_searchio.github.dynamitecircle/dclive status →

FAQ

What is the best alternative to mcp-registry/com.googleapis.mapstools/mcp/resolve_names?

mcp-registry/com.mydriverparis/booking/resolve_location is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search, mcp-registry/io.github.pipeworx-io/openweather/geocode, mcp-registry/io.github.vee3io/vee3/google-maps.search, mcp-registry/me.foodnear/foodnear-me/search_restaurants. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.googleapis.mapstools/mcp/resolve_names down right now?

mcp-registry/com.googleapis.mapstools/mcp/resolve_names's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.googleapis.mapstools%2Fmcp%2Fresolve_names.

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.googleapis.mapstools%2Fmcp%2Fresolve_names or MCP find_alternatives. Check mcp-registry/com.googleapis.mapstools/mcp/resolve_names's live status: https://glimind.com/tool/mcp-registry/com.googleapis.mapstools/mcp/resolve_names.