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

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

The best live alternatives to mcp-registry/io.github.pipeworx-io/arcgis-kansas/search_datasets right now are mcp-registry/io.github.pipeworx-io/arcgis-montana/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-sarpycounty/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-stlouiscounty/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-kingston/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-sacramento/search_datasets — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/arcgis-kansas/search_datasets itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/arcgis-montana/search_datasets	io.github.pipeworx-io/arcgis-montana	live status →
mcp-registry/io.github.pipeworx-io/arcgis-sarpycounty/search_datasets	io.github.pipeworx-io/arcgis-sarpycounty	live status →
mcp-registry/io.github.pipeworx-io/arcgis-stlouiscounty/search_datasets	io.github.pipeworx-io/arcgis-stlouiscounty	live status →
mcp-registry/io.github.pipeworx-io/arcgis-kingston/search_datasets	io.github.pipeworx-io/arcgis-kingston	live status →
mcp-registry/io.github.pipeworx-io/arcgis-sacramento/search_datasets	io.github.pipeworx-io/arcgis-sacramento	live status →
mcp-registry/io.github.pipeworx-io/arcgis-lincolnne/search_datasets	io.github.pipeworx-io/arcgis-lincolnne	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-branson/search_datasets	io.github.pipeworx-io/arcgis-branson	live status →
mcp-registry/io.github.pipeworx-io/arcgis-lincolncountync/search_datasets	io.github.pipeworx-io/arcgis-lincolncountync	live status →
mcp-registry/io.github.pipeworx-io/arcgis-phoenix/search_datasets	io.github.pipeworx-io/arcgis-phoenix	live status →
mcp-registry/io.github.pipeworx-io/arcgis-kamloops/search_datasets	io.github.pipeworx-io/arcgis-kamloops	live status →
mcp-registry/io.github.pipeworx-io/arcgis-austin/search_datasets	io.github.pipeworx-io/arcgis-austin	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/arcgis-montana/search_datasets is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/arcgis-sarpycounty/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-stlouiscounty/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-kingston/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-sacramento/search_datasets. Glimind ranks alternatives by semantic similarity and live health.

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

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