mcp-registry/io.github.vortx-ai/emem/emem_elevation / alternatives

Live alternatives to mcp-registry/io.github.vortx-ai/emem/emem_elevation

The best live alternatives to mcp-registry/io.github.vortx-ai/emem/emem_elevation right now are mcp-registry/io.github.pipeworx-io/open-elevation/get_elevation, mcp-registry/io.github.pipeworx-io/openrouteservice/elevation_point, mcp-registry/io.github.pipeworx-io/maptiler/elevation, mcp-registry/io.github.pipeworx-io/google_maps/maps_elevation, mcp-registry/io.github.pipeworx-io/opentopography/point_elevation — capability-matched and ranked by current reliability. mcp-registry/io.github.vortx-ai/emem/emem_elevation itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/open-elevation/get_elevation	io.github.pipeworx-io/open-elevation	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/elevation_point	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/io.github.pipeworx-io/maptiler/elevation	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_elevation	io.github.pipeworx-io/google_maps	live status →
mcp-registry/io.github.pipeworx-io/opentopography/point_elevation	io.github.pipeworx-io/opentopography	live status →
mcp-registry/io.github.pipeworx-io/opentopodata/elevation	io.github.pipeworx-io/opentopodata	live status →
mcp-registry/io.github.pipeworx-io/open-elevation/get_elevations	io.github.pipeworx-io/open-elevation	live status →
mcp-registry/io.github.pipeworx-io/openrouteservice/elevation_line	io.github.pipeworx-io/openrouteservice	live status →
mcp-registry/io.github.pipeworx-io/maptiler/elevation_polyline	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.pipeworx-io/opentopography/datasets	io.github.pipeworx-io/opentopography	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/tides	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/app.nausika/mcp/nausika_is_water	app.nausika/mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.vortx-ai/emem/emem_elevation?

mcp-registry/io.github.pipeworx-io/open-elevation/get_elevation is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/openrouteservice/elevation_point, mcp-registry/io.github.pipeworx-io/maptiler/elevation, mcp-registry/io.github.pipeworx-io/google_maps/maps_elevation, mcp-registry/io.github.pipeworx-io/opentopography/point_elevation. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.vortx-ai/emem/emem_elevation down right now?

mcp-registry/io.github.vortx-ai/emem/emem_elevation's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.vortx-ai%2Femem%2Femem_elevation.

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.vortx-ai%2Femem%2Femem_elevation or MCP find_alternatives. Check mcp-registry/io.github.vortx-ai/emem/emem_elevation's live status: https://glimind.com/tool/mcp-registry/io.github.vortx-ai/emem/emem_elevation.