mcp-registry/io.github.pipeworx-io/opentopography/dem / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/opentopography/dem

The best live alternatives to mcp-registry/io.github.pipeworx-io/opentopography/dem right now are mcp-registry/io.github.pipeworx-io/opentopodata/datasets, mcp-registry/com.daedalmap/county-map/get_boundary, mcp-registry/com.daedalmap/geocoding/get_boundary, mcp-registry/com.daedalmap/boundaries/get_boundary, mcp-registry/io.github.vortx-ai/emem/emem_terrain — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/opentopography/dem itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/opentopodata/datasets	io.github.pipeworx-io/opentopodata	live status →
mcp-registry/com.daedalmap/county-map/get_boundary	com.daedalmap/county-map	live status →
mcp-registry/com.daedalmap/geocoding/get_boundary	com.daedalmap/geocoding	live status →
mcp-registry/com.daedalmap/boundaries/get_boundary	com.daedalmap/boundaries	live status →
mcp-registry/io.github.vortx-ai/emem/emem_terrain	io.github.Vortx-AI/emem	live status →
mcp-registry/io.github.pipeworx-io/geoboundaries/get_boundaries	io.github.pipeworx-io/geoboundaries	live status →
mcp-registry/dev.infranode/infranode/geo	dev.infranode/infranode	live status →
mcp-registry/io.github.pipeworx-io/nasa-power/regional_data	io.github.pipeworx-io/nasa-power	live status →
mcp-registry/io.github.pipeworx-io/maptiler/tiles_json	io.github.pipeworx-io/maptiler	live status →
mcp-registry/com.daedalmap/county-map/loc_id_info	com.daedalmap/county-map	live status →
mcp-registry/com.daedalmap/boundaries/loc_id_info	com.daedalmap/boundaries	live status →
mcp-registry/com.daedalmap/geocoding/loc_id_info	com.daedalmap/geocoding	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/opentopography/dem?

mcp-registry/io.github.pipeworx-io/opentopodata/datasets is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.daedalmap/county-map/get_boundary, mcp-registry/com.daedalmap/geocoding/get_boundary, mcp-registry/com.daedalmap/boundaries/get_boundary, mcp-registry/io.github.vortx-ai/emem/emem_terrain. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/opentopography/dem down right now?

mcp-registry/io.github.pipeworx-io/opentopography/dem's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fopentopography%2Fdem.

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%2Fopentopography%2Fdem or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/opentopography/dem's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/opentopography/dem.