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

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

The best live alternatives to mcp-registry/io.github.pipeworx-io/opentopography/datasets right now are mcp-registry/io.github.pipeworx-io/opentopodata/datasets, mcp-registry/io.github.vortx-ai/emem/emem_terrain, mcp-registry/io.github.pipeworx-io/nasa-cmr/search_collections, mcp-registry/io.github.pipeworx-io/opendosm-my/opendosm_list_datasets, mcp-registry/io.github.pipeworx-io/maptiler/elevation — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/opentopography/datasets itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/opentopodata/datasets	io.github.pipeworx-io/opentopodata	live status →
mcp-registry/io.github.vortx-ai/emem/emem_terrain	io.github.Vortx-AI/emem	live status →
mcp-registry/io.github.pipeworx-io/nasa-cmr/search_collections	io.github.pipeworx-io/nasa-cmr	live status →
mcp-registry/io.github.pipeworx-io/opendosm-my/opendosm_list_datasets	io.github.pipeworx-io/opendosm-my	live status →
mcp-registry/io.github.pipeworx-io/maptiler/elevation	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.pipeworx-io/bea-gov/dataset_list	io.github.pipeworx-io/bea-gov	live status →
mcp-registry/io.github.vortx-ai/emem/emem_elevation	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/io.github.pipeworx-io/opendosm-my/opendosm_get_dataset	io.github.pipeworx-io/opendosm-my	live status →
mcp-registry/com.gribstream/mcp/gribstream_list_datasets	com.gribstream/mcp	live status →
mcp-registry/io.github.pipeworx-io/huggingface/trending_datasets	io.github.pipeworx-io/huggingface	live status →
mcp-registry/io.github.pipeworx-io/gdacs/events	io.github.pipeworx-io/gdacs	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/opentopodata/datasets is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vortx-ai/emem/emem_terrain, mcp-registry/io.github.pipeworx-io/nasa-cmr/search_collections, mcp-registry/io.github.pipeworx-io/opendosm-my/opendosm_list_datasets, mcp-registry/io.github.pipeworx-io/maptiler/elevation. Glimind ranks alternatives by semantic similarity and live health.

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

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

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