mcp-registry/com.googleapis.mapstools/mcp/resolve_names / alternatives
mcp-registry/com.googleapis.mapstools/mcp/resolve_namesThe 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".
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.
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.
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.
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.