mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset

The best live alternatives to mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset right now are mcp-registry/io.github.pipeworx-io/datacube-sk/get_data, mcp-registry/io.github.pipeworx-io/estat-japan/get_data, mcp-registry/io.github.pipeworx-io/czso-cz/get_data, mcp-registry/io.github.pipeworx-io/datacube-sk/list_datasets, mcp-registry/io.github.pipeworx-io/cms/get_dataset — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/datacube-sk/get_data	io.github.pipeworx-io/datacube-sk	live status →
mcp-registry/io.github.pipeworx-io/estat-japan/get_data	io.github.pipeworx-io/estat-japan	live status →
mcp-registry/io.github.pipeworx-io/czso-cz/get_data	io.github.pipeworx-io/czso-cz	live status →
mcp-registry/io.github.pipeworx-io/datacube-sk/list_datasets	io.github.pipeworx-io/datacube-sk	live status →
mcp-registry/io.github.pipeworx-io/cms/get_dataset	io.github.pipeworx-io/cms	live status →
mcp-registry/io.github.pipeworx-io/bpstat-pt/get_dataset	io.github.pipeworx-io/bpstat-pt	live status →
mcp-registry/io.github.pipeworx-io/datacube-sk/dataset_dimensions	io.github.pipeworx-io/datacube-sk	live status →
mcp-registry/io.github.pipeworx-io/data-gov-sg/query_dataset	io.github.pipeworx-io/data-gov-sg	live status →
mcp-registry/io.github.pipeworx-io/cms/dataset_info	io.github.pipeworx-io/cms	live status →
mcp-registry/io.github.pipeworx-io/czso-cz/dataset_detail	io.github.pipeworx-io/czso-cz	live status →
mcp-registry/io.github.pipeworx-io/cdc/get_dataset	io.github.pipeworx-io/cdc	live status →
mcp-registry/io.github.pipeworx-io/nsi-bg/get_dataset	io.github.pipeworx-io/nsi-bg	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset?

mcp-registry/io.github.pipeworx-io/datacube-sk/get_data is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/estat-japan/get_data, mcp-registry/io.github.pipeworx-io/czso-cz/get_data, mcp-registry/io.github.pipeworx-io/datacube-sk/list_datasets, mcp-registry/io.github.pipeworx-io/cms/get_dataset. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset down right now?

mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fcso-ie%2Fquery_dataset.

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%2Fcso-ie%2Fquery_dataset or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset.