mcp-registry/io.github.pipeworx-io/nasa-eonet/list_layers / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/nasa-eonet/list_layers

The best live alternatives to mcp-registry/io.github.pipeworx-io/nasa-eonet/list_layers right now are mcp-registry/io.github.pipeworx-io/data-dc/dc_layers, mcp-registry/io.github.pipeworx-io/data-baltimore/baltimore_layers, mcp-registry/io.github.davidmosiah/delx-mcp-a2a/list_ontology_primitives, mcp-registry/io.github.pipeworx-io/arcgis-kinston/layer_info, mcp-registry/io.github.pipeworx-io/arcgis-sanbernardino/layer_info — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/nasa-eonet/list_layers itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/data-dc/dc_layers	io.github.pipeworx-io/data-dc	live status →
mcp-registry/io.github.pipeworx-io/data-baltimore/baltimore_layers	io.github.pipeworx-io/data-baltimore	live status →
mcp-registry/io.github.davidmosiah/delx-mcp-a2a/list_ontology_primitives	io.github.davidmosiah/delx-mcp-a2a	live status →
mcp-registry/io.github.pipeworx-io/arcgis-kinston/layer_info	io.github.pipeworx-io/arcgis-kinston	live status →
mcp-registry/io.github.pipeworx-io/arcgis-sanbernardino/layer_info	io.github.pipeworx-io/arcgis-sanbernardino	live status →
mcp-registry/io.github.pipeworx-io/arcgis-southbend/layer_info	io.github.pipeworx-io/arcgis-southbend	live status →
mcp-registry/io.github.pipeworx-io/arcgis-peoria/layer_info	io.github.pipeworx-io/arcgis-peoria	live status →
mcp-registry/io.github.pipeworx-io/arcgis-pittsburgh/layer_info	io.github.pipeworx-io/arcgis-pittsburgh	live status →
mcp-registry/io.github.pipeworx-io/arcgis-maricopa/layer_info	io.github.pipeworx-io/arcgis-maricopa	live status →
mcp-registry/io.github.pipeworx-io/arcgis-kansas/layer_info	io.github.pipeworx-io/arcgis-kansas	live status →
mcp-registry/io.github.pipeworx-io/arcgis-cumberland/layer_info	io.github.pipeworx-io/arcgis-cumberland	live status →
mcp-registry/io.github.pipeworx-io/arcgis-montana/layer_info	io.github.pipeworx-io/arcgis-montana	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/nasa-eonet/list_layers?

mcp-registry/io.github.pipeworx-io/data-dc/dc_layers is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/data-baltimore/baltimore_layers, mcp-registry/io.github.davidmosiah/delx-mcp-a2a/list_ontology_primitives, mcp-registry/io.github.pipeworx-io/arcgis-kinston/layer_info, mcp-registry/io.github.pipeworx-io/arcgis-sanbernardino/layer_info. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/nasa-eonet/list_layers down right now?

mcp-registry/io.github.pipeworx-io/nasa-eonet/list_layers's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fnasa-eonet%2Flist_layers.

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%2Fnasa-eonet%2Flist_layers or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/nasa-eonet/list_layers's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/nasa-eonet/list_layers.