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

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

The best live alternatives to mcp-registry/io.github.vortx-ai/emem/emem_cell_geojson right now are mcp-registry/io.github.pipeworx-io/opencellid/get_cell, mcp-registry/io.github.pipeworx-io/nasa-eonet/geojson, mcp-registry/space.0/space0/get_cell, mcp-registry/io.github.pipeworx-io/opencellid/cells_in_area, mcp-registry/io.github.pipeworx-io/gdacs/geojson — capability-matched and ranked by current reliability. mcp-registry/io.github.vortx-ai/emem/emem_cell_geojson itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/opencellid/get_cell	io.github.pipeworx-io/opencellid	live status →
mcp-registry/io.github.pipeworx-io/nasa-eonet/geojson	io.github.pipeworx-io/nasa-eonet	live status →
mcp-registry/space.0/space0/get_cell	space.0/space0	live status →
mcp-registry/io.github.pipeworx-io/opencellid/cells_in_area	io.github.pipeworx-io/opencellid	live status →
mcp-registry/io.github.pipeworx-io/gdacs/geojson	io.github.pipeworx-io/gdacs	live status →
mcp-registry/io.github.pipeworx-io/maptiler/tiles_json	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.pipeworx-io/geoboundaries/get_geometry	io.github.pipeworx-io/geoboundaries	live status →
mcp-registry/space.0/space0/inspect_region	space.0/space0	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.digitalweb33333-creator/x402-endpoints/osm_building_footprint	io.github.digitalweb33333-creator/x402-endpoints	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/opencellid/get_cell is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/nasa-eonet/geojson, mcp-registry/space.0/space0/get_cell, mcp-registry/io.github.pipeworx-io/opencellid/cells_in_area, mcp-registry/io.github.pipeworx-io/gdacs/geojson. Glimind ranks alternatives by semantic similarity and live health.

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

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

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