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

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

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

alternative	server
mcp-registry/io.github.pipeworx-io/data-novascotia/metadata	io.github.pipeworx-io/data-novascotia	live status →
mcp-registry/io.github.pipeworx-io/data-novascotia/datasets	io.github.pipeworx-io/data-novascotia	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-norfolk/metadata	io.github.pipeworx-io/data-norfolk	live status →
mcp-registry/io.github.pipeworx-io/data-nantes/dataset_info	io.github.pipeworx-io/data-nantes	live status →
mcp-registry/io.github.pipeworx-io/data-vermont/metadata	io.github.pipeworx-io/data-vermont	live status →
mcp-registry/io.github.pipeworx-io/data-nj/metadata	io.github.pipeworx-io/data-nj	live status →
mcp-registry/io.github.pipeworx-io/data-winnipeg/metadata	io.github.pipeworx-io/data-winnipeg	live status →
mcp-registry/io.github.pipeworx-io/data-oregon/metadata	io.github.pipeworx-io/data-oregon	live status →
mcp-registry/io.github.pipeworx-io/data-mesa/metadata	io.github.pipeworx-io/data-mesa	live status →
mcp-registry/io.github.pipeworx-io/data-delaware/metadata	io.github.pipeworx-io/data-delaware	live status →
mcp-registry/io.github.pipeworx-io/data-connecticut/metadata	io.github.pipeworx-io/data-connecticut	live status →

FAQ

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

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

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

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

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