mcp-registry/io.github.pipeworx-io/maptiler/geocode_by_id / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/maptiler/geocode_by_id

The best live alternatives to mcp-registry/io.github.pipeworx-io/maptiler/geocode_by_id right now are mcp-registry/io.github.pipeworx-io/photon/reverse, mcp-registry/io.github.pipeworx-io/mapbox/tilequery, mcp-registry/io.github.pipeworx-io/tomtom/reverse_geocode, mcp-registry/io.github.pipeworx-io/google_maps/maps_reverse_geocode, mcp-registry/io.github.pipeworx-io/geoapify/reverse_geocode — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/maptiler/geocode_by_id itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/photon/reverse	io.github.pipeworx-io/photon	live status →
mcp-registry/io.github.pipeworx-io/mapbox/tilequery	io.github.pipeworx-io/mapbox	live status →
mcp-registry/io.github.pipeworx-io/tomtom/reverse_geocode	io.github.pipeworx-io/tomtom	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_reverse_geocode	io.github.pipeworx-io/google_maps	live status →
mcp-registry/io.github.pipeworx-io/geoapify/reverse_geocode	io.github.pipeworx-io/geoapify	live status →
mcp-registry/org.memoryapi/geo/geocode_address	org.memoryapi/geo	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/geocode	ai.intuitek.the-stall/the-stall	live status →
mcp-registry/dev.torify/japanese-locale-mcp/torify_geo.reverseGeocode	dev.torify/japanese-locale-mcp	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/geocode_search	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/com.daedalmap/reverse-geocoding/resolve_point	com.daedalmap/reverse-geocoding	live status →
mcp-registry/com.daedalmap/geocoding/resolve_point	com.daedalmap/geocoding	live status →
mcp-registry/com.daedalmap/county-map/resolve_point	com.daedalmap/county-map	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/maptiler/geocode_by_id?

mcp-registry/io.github.pipeworx-io/photon/reverse is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/mapbox/tilequery, mcp-registry/io.github.pipeworx-io/tomtom/reverse_geocode, mcp-registry/io.github.pipeworx-io/google_maps/maps_reverse_geocode, mcp-registry/io.github.pipeworx-io/geoapify/reverse_geocode. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/maptiler/geocode_by_id down right now?

mcp-registry/io.github.pipeworx-io/maptiler/geocode_by_id's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fmaptiler%2Fgeocode_by_id.

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