mcp-registry/io.github.pipeworx-io/soilgrids/soil_classification / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/soilgrids/soil_classification

The best live alternatives to mcp-registry/io.github.pipeworx-io/soilgrids/soil_classification right now are mcp-registry/io.github.vortx-ai/emem/emem_soil, mcp-registry/io.github.pipeworx-io/powo/get_taxon, mcp-registry/io.github.pipeworx-io/powo/search_plants, mcp-registry/com.wingmanprotocol.agent/gateway/raised_bed, mcp-registry/dev.infranode/infranode/tree_cadastre — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/soilgrids/soil_classification itself is currently "healthy".

alternative	server
mcp-registry/io.github.vortx-ai/emem/emem_soil	io.github.Vortx-AI/emem	live status →
mcp-registry/io.github.pipeworx-io/powo/get_taxon	io.github.pipeworx-io/powo	live status →
mcp-registry/io.github.pipeworx-io/powo/search_plants	io.github.pipeworx-io/powo	live status →
mcp-registry/com.wingmanprotocol.agent/gateway/raised_bed	com.wingmanprotocol.agent/gateway	live status →
mcp-registry/dev.infranode/infranode/tree_cadastre	dev.infranode/infranode	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/usgs_water_realtime	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/com.civilquants/civilquants/compute_end_area_earthworks	com.civilquants/civilquants	live status →
mcp-registry/ai.snowsure/snow/get_road_weather	ai.snowsure/snow	live status →
mcp-registry/space.0/space0/find_clear_region	space.0/space0	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.vortx-ai/emem/emem_grid_info	io.github.Vortx-AI/emem	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/soilgrids/soil_classification?

mcp-registry/io.github.vortx-ai/emem/emem_soil is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/powo/get_taxon, mcp-registry/io.github.pipeworx-io/powo/search_plants, mcp-registry/com.wingmanprotocol.agent/gateway/raised_bed, mcp-registry/dev.infranode/infranode/tree_cadastre. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/soilgrids/soil_classification down right now?

mcp-registry/io.github.pipeworx-io/soilgrids/soil_classification's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fsoilgrids%2Fsoil_classification.

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