mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns

The best live alternatives to mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns right now are mcp-registry/io.github.pipeworx-io/bts/dataset_columns, mcp-registry/io.github.pipeworx-io/bts/query_dataset, mcp-registry/io.github.xaviviro/opendata-cat/list_dataset_fields, mcp-registry/io.github.pipeworx-io/data-gov-sg/get_dataset, mcp-registry/io.github.pipeworx-io/data-reunion/dataset_info — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/bts/dataset_columns	io.github.pipeworx-io/bts	live status →
mcp-registry/io.github.pipeworx-io/bts/query_dataset	io.github.pipeworx-io/bts	live status →
mcp-registry/io.github.xaviviro/opendata-cat/list_dataset_fields	io.github.xaviviro/opendata-cat	live status →
mcp-registry/io.github.pipeworx-io/data-gov-sg/get_dataset	io.github.pipeworx-io/data-gov-sg	live status →
mcp-registry/io.github.pipeworx-io/data-reunion/dataset_info	io.github.pipeworx-io/data-reunion	live status →
mcp-registry/io.github.pipeworx-io/cms/dataset_info	io.github.pipeworx-io/cms	live status →
mcp-registry/io.github.sevask/nova-scotia-data-explorer/get_dataset_metadata	io.github.SevaSk/nova-scotia-data-explorer	live status →
mcp-registry/io.github.pipeworx-io/cdc/get_dataset	io.github.pipeworx-io/cdc	live status →
mcp-registry/io.github.pipeworx-io/data-issy/dataset_info	io.github.pipeworx-io/data-issy	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/dane-gov-pl/dataset_details	io.github.pipeworx-io/dane-gov-pl	live status →
mcp-registry/io.github.pipeworx-io/data-centrevaldeloire/dataset_info	io.github.pipeworx-io/data-centrevaldeloire	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns?

mcp-registry/io.github.pipeworx-io/bts/dataset_columns is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/bts/query_dataset, mcp-registry/io.github.xaviviro/opendata-cat/list_dataset_fields, mcp-registry/io.github.pipeworx-io/data-gov-sg/get_dataset, mcp-registry/io.github.pipeworx-io/data-reunion/dataset_info. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns down right now?

mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fdatos-co%2Fdataset_columns.

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%2Fdatos-co%2Fdataset_columns or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns.