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

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

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

alternative	server
mcp-registry/io.github.pipeworx-io/data-novascotia/datasets	io.github.pipeworx-io/data-novascotia	live status →
mcp-registry/io.github.pipeworx-io/data-norfolk/datasets	io.github.pipeworx-io/data-norfolk	live status →
mcp-registry/io.github.pipeworx-io/data-novascotia/metadata	io.github.pipeworx-io/data-novascotia	live status →
mcp-registry/io.github.pipeworx-io/data-va/datasets	io.github.pipeworx-io/data-va	live status →
mcp-registry/io.github.pipeworx-io/data-nj/datasets	io.github.pipeworx-io/data-nj	live status →
mcp-registry/io.github.pipeworx-io/data-vermont/datasets	io.github.pipeworx-io/data-vermont	live status →
mcp-registry/io.github.pipeworx-io/data-calgary/calgary_datasets	io.github.pipeworx-io/data-calgary	live status →
mcp-registry/io.github.pipeworx-io/data-cambridge/cambridge_datasets	io.github.pipeworx-io/data-cambridge	live status →
mcp-registry/io.github.pipeworx-io/data-santaclara/datasets	io.github.pipeworx-io/data-santaclara	live status →
mcp-registry/io.github.pipeworx-io/data-sonoma/datasets	io.github.pipeworx-io/data-sonoma	live status →
mcp-registry/io.github.pipeworx-io/data-delaware/datasets	io.github.pipeworx-io/data-delaware	live status →
mcp-registry/io.github.pipeworx-io/data-edmonton/edmonton_datasets	io.github.pipeworx-io/data-edmonton	live status →

FAQ

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

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

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

mcp-registry/io.github.sevask/nova-scotia-data-explorer/search_datasets'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%2Fsearch_datasets.

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%2Fsearch_datasets or MCP find_alternatives. Check mcp-registry/io.github.sevask/nova-scotia-data-explorer/search_datasets's live status: https://glimind.com/tool/mcp-registry/io.github.sevask/nova-scotia-data-explorer/search_datasets.