mcp-registry/io.github.pipeworx-io/arcgis-grandchute/search_datasets / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/arcgis-grandchute/search_datasets

The best live alternatives to mcp-registry/io.github.pipeworx-io/arcgis-grandchute/search_datasets right now are mcp-registry/io.github.pipeworx-io/arcgis-chapelhill/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-chatham/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-greenwood/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-durham/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-peoria/search_datasets — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/arcgis-grandchute/search_datasets itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/arcgis-chapelhill/search_datasets	io.github.pipeworx-io/arcgis-chapelhill	live status →
mcp-registry/io.github.pipeworx-io/arcgis-chatham/search_datasets	io.github.pipeworx-io/arcgis-chatham	live status →
mcp-registry/io.github.pipeworx-io/arcgis-greenwood/search_datasets	io.github.pipeworx-io/arcgis-greenwood	live status →
mcp-registry/io.github.pipeworx-io/arcgis-durham/search_datasets	io.github.pipeworx-io/arcgis-durham	live status →
mcp-registry/io.github.pipeworx-io/arcgis-peoria/search_datasets	io.github.pipeworx-io/arcgis-peoria	live status →
mcp-registry/io.github.pipeworx-io/arcgis-charlotte/search_datasets	io.github.pipeworx-io/arcgis-charlotte	live status →
mcp-registry/io.github.pipeworx-io/arcgis-cary/search_datasets	io.github.pipeworx-io/arcgis-cary	live status →
mcp-registry/io.github.pipeworx-io/arcgis-lakecountyil/search_datasets	io.github.pipeworx-io/arcgis-lakecountyil	live status →
mcp-registry/io.github.pipeworx-io/arcgis-seattle/search_datasets	io.github.pipeworx-io/arcgis-seattle	live status →
mcp-registry/io.github.pipeworx-io/arcgis-kansas/search_datasets	io.github.pipeworx-io/arcgis-kansas	live status →
mcp-registry/io.github.pipeworx-io/arcgis-toledo/search_datasets	io.github.pipeworx-io/arcgis-toledo	live status →
mcp-registry/io.github.pipeworx-io/arcgis-kingston/search_datasets	io.github.pipeworx-io/arcgis-kingston	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/arcgis-grandchute/search_datasets?

mcp-registry/io.github.pipeworx-io/arcgis-chapelhill/search_datasets is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/arcgis-chatham/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-greenwood/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-durham/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-peoria/search_datasets. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/arcgis-grandchute/search_datasets down right now?

mcp-registry/io.github.pipeworx-io/arcgis-grandchute/search_datasets's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Farcgis-grandchute%2Fsearch_datasets.

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%2Farcgis-grandchute%2Fsearch_datasets or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/arcgis-grandchute/search_datasets's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/arcgis-grandchute/search_datasets.