mcp-registry/io.github.sevask/nova-scotia-data-explorer/query_dataset / alternatives

Live alternatives to mcp-registry/io.github.sevask/nova-scotia-data-explorer/query_dataset

The best live alternatives to mcp-registry/io.github.sevask/nova-scotia-data-explorer/query_dataset right now are mcp-registry/io.github.pipeworx-io/data-novascotia/query, mcp-registry/io.github.pipeworx-io/data-vermont/query, mcp-registry/io.github.pipeworx-io/data-norfolk/query, mcp-registry/io.github.pipeworx-io/data-nj/query, mcp-registry/io.github.pipeworx-io/data-providence/query — capability-matched and ranked by current reliability. mcp-registry/io.github.sevask/nova-scotia-data-explorer/query_dataset itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/data-novascotia/query	io.github.pipeworx-io/data-novascotia	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-norfolk/query	io.github.pipeworx-io/data-norfolk	live status →
mcp-registry/io.github.pipeworx-io/data-nj/query	io.github.pipeworx-io/data-nj	live status →
mcp-registry/io.github.pipeworx-io/data-providence/query	io.github.pipeworx-io/data-providence	live status →
mcp-registry/io.github.pipeworx-io/data-sonoma/query	io.github.pipeworx-io/data-sonoma	live status →
mcp-registry/io.github.pipeworx-io/data-va/query	io.github.pipeworx-io/data-va	live status →
mcp-registry/io.github.pipeworx-io/data-oregon/query	io.github.pipeworx-io/data-oregon	live status →
mcp-registry/io.github.pipeworx-io/data-santaclara/query	io.github.pipeworx-io/data-santaclara	live status →
mcp-registry/io.github.pipeworx-io/bts/query_dataset	io.github.pipeworx-io/bts	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-mo/query	io.github.pipeworx-io/data-mo	live status →

FAQ

What is the best alternative to mcp-registry/io.github.sevask/nova-scotia-data-explorer/query_dataset?

mcp-registry/io.github.pipeworx-io/data-novascotia/query is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/data-vermont/query, mcp-registry/io.github.pipeworx-io/data-norfolk/query, mcp-registry/io.github.pipeworx-io/data-nj/query, mcp-registry/io.github.pipeworx-io/data-providence/query. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.sevask/nova-scotia-data-explorer/query_dataset down right now?

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