mcp-registry/io.github.pipeworx-io/datacube-sk/get_data / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/datacube-sk/get_data

The best live alternatives to mcp-registry/io.github.pipeworx-io/datacube-sk/get_data right now are 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/bpstat-pt/get_dataset, mcp-registry/io.github.pipeworx-io/cso-ie/get_dataset, mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/datacube-sk/get_data itself is currently "healthy".

alternative	server
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/bpstat-pt/get_dataset	io.github.pipeworx-io/bpstat-pt	live status →
mcp-registry/io.github.pipeworx-io/cso-ie/get_dataset	io.github.pipeworx-io/cso-ie	live status →
mcp-registry/io.github.pipeworx-io/cso-ie/query_dataset	io.github.pipeworx-io/cso-ie	live status →
mcp-registry/io.github.pipeworx-io/statcan/statcan_cube_metadata	io.github.pipeworx-io/statcan	live status →
mcp-registry/io.github.pipeworx-io/statcan/statcan_list_cubes	io.github.pipeworx-io/statcan	live status →
mcp-registry/io.github.pipeworx-io/statcan/statcan_cube_data	io.github.pipeworx-io/statcan	live status →
mcp-registry/io.github.pipeworx-io/unicef/dataflow_structure	io.github.pipeworx-io/unicef	live status →
mcp-registry/io.github.pipeworx-io/statec-lu/dataflow_structure	io.github.pipeworx-io/statec-lu	live status →
mcp-registry/io.github.pipeworx-io/dst-dk/get_data	io.github.pipeworx-io/dst-dk	live status →
mcp-registry/io.github.pipeworx-io/istat-it/get_data	io.github.pipeworx-io/istat-it	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/datacube-sk/get_data?

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

Is mcp-registry/io.github.pipeworx-io/datacube-sk/get_data down right now?

mcp-registry/io.github.pipeworx-io/datacube-sk/get_data's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fdatacube-sk%2Fget_data.

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%2Fdatacube-sk%2Fget_data or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/datacube-sk/get_data's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/datacube-sk/get_data.