mcp-registry/io.github.pipeworx-io/bts/query_dataset / alternatives

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

The best live alternatives to mcp-registry/io.github.pipeworx-io/bts/query_dataset right now are mcp-registry/io.github.pipeworx-io/datos-co/query_dataset, mcp-registry/io.github.blackboxfoundry/livedatalink/cdc_dataset_query, mcp-registry/io.github.pipeworx-io/data-texas/query, mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns, mcp-registry/io.github.pipeworx-io/data-connecticut/query — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/bts/query_dataset itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/datos-co/query_dataset	io.github.pipeworx-io/datos-co	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/cdc_dataset_query	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/data-texas/query	io.github.pipeworx-io/data-texas	live status →
mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns	io.github.pipeworx-io/datos-co	live status →
mcp-registry/io.github.pipeworx-io/data-connecticut/query	io.github.pipeworx-io/data-connecticut	live status →
mcp-registry/io.github.pipeworx-io/data-batonrouge/query	io.github.pipeworx-io/data-batonrouge	live status →
mcp-registry/io.github.pipeworx-io/data-vermont/query	io.github.pipeworx-io/data-vermont	live status →
mcp-registry/io.github.pipeworx-io/data-utah/query	io.github.pipeworx-io/data-utah	live status →
mcp-registry/io.github.pipeworx-io/data-cityofnewyork/query	io.github.pipeworx-io/data-cityofnewyork	live status →
mcp-registry/io.github.pipeworx-io/data-fortworth/query	io.github.pipeworx-io/data-fortworth	live status →
mcp-registry/io.github.pipeworx-io/data-fulton/query	io.github.pipeworx-io/data-fulton	live status →
mcp-registry/io.github.pipeworx-io/data-va/query	io.github.pipeworx-io/data-va	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/datos-co/query_dataset is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.blackboxfoundry/livedatalink/cdc_dataset_query, mcp-registry/io.github.pipeworx-io/data-texas/query, mcp-registry/io.github.pipeworx-io/datos-co/dataset_columns, mcp-registry/io.github.pipeworx-io/data-connecticut/query. Glimind ranks alternatives by semantic similarity and live health.

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

mcp-registry/io.github.pipeworx-io/bts/query_dataset's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fbts%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%2Fbts%2Fquery_dataset or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/bts/query_dataset's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/bts/query_dataset.