mcp-registry/dev.infranode/infranode/tree_cadastre / alternatives

Live alternatives to mcp-registry/dev.infranode/infranode/tree_cadastre

The best live alternatives to mcp-registry/dev.infranode/infranode/tree_cadastre right now are mcp-registry/io.github.pipeworx-io/trefle/get_plant, mcp-registry/io.github.pipeworx-io/data-toulouse/dataset_info, mcp-registry/io.github.pipeworx-io/data-paris/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-cedarpark/search_datasets, mcp-registry/io.github.pipeworx-io/data-brussels/dataset_info — capability-matched and ranked by current reliability. mcp-registry/dev.infranode/infranode/tree_cadastre itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/trefle/get_plant	io.github.pipeworx-io/trefle	live status →
mcp-registry/io.github.pipeworx-io/data-toulouse/dataset_info	io.github.pipeworx-io/data-toulouse	live status →
mcp-registry/io.github.pipeworx-io/data-paris/search_datasets	io.github.pipeworx-io/data-paris	live status →
mcp-registry/io.github.pipeworx-io/arcgis-cedarpark/search_datasets	io.github.pipeworx-io/arcgis-cedarpark	live status →
mcp-registry/io.github.pipeworx-io/data-brussels/dataset_info	io.github.pipeworx-io/data-brussels	live status →
mcp-registry/io.github.pipeworx-io/arcgis-tampa/search_datasets	io.github.pipeworx-io/arcgis-tampa	live status →
mcp-registry/io.github.pipeworx-io/data-cityofnewyork/metadata	io.github.pipeworx-io/data-cityofnewyork	live status →
mcp-registry/io.github.pipeworx-io/arcgis-detroit/search_datasets	io.github.pipeworx-io/arcgis-detroit	live status →
mcp-registry/io.github.pipeworx-io/data-centrevaldeloire/dataset_info	io.github.pipeworx-io/data-centrevaldeloire	live status →
mcp-registry/io.github.pipeworx-io/arcgis-dublinoh/search_datasets	io.github.pipeworx-io/arcgis-dublinoh	live status →
mcp-registry/io.github.pipeworx-io/data-paris/dataset_info	io.github.pipeworx-io/data-paris	live status →
mcp-registry/io.github.pipeworx-io/data-rennes/dataset_info	io.github.pipeworx-io/data-rennes	live status →

FAQ

What is the best alternative to mcp-registry/dev.infranode/infranode/tree_cadastre?

mcp-registry/io.github.pipeworx-io/trefle/get_plant is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/data-toulouse/dataset_info, mcp-registry/io.github.pipeworx-io/data-paris/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-cedarpark/search_datasets, mcp-registry/io.github.pipeworx-io/data-brussels/dataset_info. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/dev.infranode/infranode/tree_cadastre down right now?

mcp-registry/dev.infranode/infranode/tree_cadastre's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fdev.infranode%2Finfranode%2Ftree_cadastre.

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%2Fdev.infranode%2Finfranode%2Ftree_cadastre or MCP find_alternatives. Check mcp-registry/dev.infranode/infranode/tree_cadastre's live status: https://glimind.com/tool/mcp-registry/dev.infranode/infranode/tree_cadastre.