mcp-registry/space.0/space0/get_cell / alternatives

Live alternatives to mcp-registry/space.0/space0/get_cell

The best live alternatives to mcp-registry/space.0/space0/get_cell right now are mcp-registry/io.github.vortx-ai/emem/emem_grid_info, mcp-registry/io.github.vortx-ai/emem/emem_cell_geojson, mcp-registry/io.github.pipeworx-io/oqmd/get_material, mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point, mcp-registry/io.github.vortx-ai/emem/emem_cell_scene_rgb — capability-matched and ranked by current reliability. mcp-registry/space.0/space0/get_cell itself is currently "healthy".

alternative	server
mcp-registry/io.github.vortx-ai/emem/emem_grid_info	io.github.Vortx-AI/emem	live status →
mcp-registry/io.github.vortx-ai/emem/emem_cell_geojson	io.github.Vortx-AI/emem	live status →
mcp-registry/io.github.pipeworx-io/oqmd/get_material	io.github.pipeworx-io/oqmd	live status →
mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point	io.github.pipeworx-io/octopus-energy	live status →
mcp-registry/io.github.vortx-ai/emem/emem_cell_scene_rgb	io.github.Vortx-AI/emem	live status →
mcp-registry/io.github.vortx-ai/emem/emem_topics	io.github.Vortx-AI/emem	live status →
mcp-registry/io.github.pipeworx-io/opencellid/get_cell	io.github.pipeworx-io/opencellid	live status →
mcp-registry/io.github.vortx-ai/emem/emem_locate	io.github.Vortx-AI/emem	live status →
mcp-registry/io.github.revolist/revogrid-mcp/resolve_feature_matrix	io.github.revolist/revogrid-mcp	live status →
mcp-registry/io.github.revolist/revogrid-mcp-pro/resolve_feature_matrix	io.github.revolist/revogrid-mcp-pro	live status →
mcp-registry/io.github.pipeworx-io/wikidata-sparql/entities_at	io.github.pipeworx-io/wikidata-sparql	live status →
mcp-registry/io.tinyfn/tinyfn/point_in_polygon	io.tinyfn/tinyfn	live status →

FAQ

What is the best alternative to mcp-registry/space.0/space0/get_cell?

mcp-registry/io.github.vortx-ai/emem/emem_grid_info is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vortx-ai/emem/emem_cell_geojson, mcp-registry/io.github.pipeworx-io/oqmd/get_material, mcp-registry/io.github.pipeworx-io/octopus-energy/grid_supply_point, mcp-registry/io.github.vortx-ai/emem/emem_cell_scene_rgb. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/space.0/space0/get_cell down right now?

mcp-registry/space.0/space0/get_cell's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fspace.0%2Fspace0%2Fget_cell.

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%2Fspace.0%2Fspace0%2Fget_cell or MCP find_alternatives. Check mcp-registry/space.0/space0/get_cell's live status: https://glimind.com/tool/mcp-registry/space.0/space0/get_cell.