mcp-registry/io.github.foundrynet/foundrynet-geo/geocode / alternatives

Live alternatives to mcp-registry/io.github.foundrynet/foundrynet-geo/geocode

The best live alternatives to mcp-registry/io.github.foundrynet/foundrynet-geo/geocode right now are mcp-registry/org.memoryapi/geo/geocode_address, mcp-registry/work.latlng.mcp/latlng/geocode_address, mcp-registry/ai.intuitek.the-stall/the-stall/geocode, mcp-registry/io.github.pipeworx-io/geo/geocode, mcp-registry/com.dfetcher/vitamin-d/geocode — capability-matched and ranked by current reliability. mcp-registry/io.github.foundrynet/foundrynet-geo/geocode itself is currently "healthy".

alternative	server
mcp-registry/org.memoryapi/geo/geocode_address	org.memoryapi/geo	live status →
mcp-registry/work.latlng.mcp/latlng/geocode_address	work.latlng.mcp/latlng	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/geocode	ai.intuitek.the-stall/the-stall	live status →
mcp-registry/io.github.pipeworx-io/geo/geocode	io.github.pipeworx-io/geo	live status →
mcp-registry/com.dfetcher/vitamin-d/geocode	com.dfetcher/vitamin-d	live status →
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/open-meteo/geocode	io.github.pipeworx-io/open-meteo	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 →
mcp-registry/io.github.pipeworx-io/google_maps/maps_geocode	io.github.pipeworx-io/google_maps	live status →
mcp-registry/io.github.pipeworx-io/geoapify/geocode	io.github.pipeworx-io/geoapify	live status →

FAQ

What is the best alternative to mcp-registry/io.github.foundrynet/foundrynet-geo/geocode?

mcp-registry/org.memoryapi/geo/geocode_address is the top capability-matched alternative that's live right now. Other options: mcp-registry/work.latlng.mcp/latlng/geocode_address, mcp-registry/ai.intuitek.the-stall/the-stall/geocode, mcp-registry/io.github.pipeworx-io/geo/geocode, mcp-registry/com.dfetcher/vitamin-d/geocode. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.foundrynet/foundrynet-geo/geocode down right now?

mcp-registry/io.github.foundrynet/foundrynet-geo/geocode's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.foundrynet%2Ffoundrynet-geo%2Fgeocode.

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.foundrynet%2Ffoundrynet-geo%2Fgeocode or MCP find_alternatives. Check mcp-registry/io.github.foundrynet/foundrynet-geo/geocode's live status: https://glimind.com/tool/mcp-registry/io.github.foundrynet/foundrynet-geo/geocode.