mcp-registry/io.github.pipeworx-io/cms/search_datasets / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/cms/search_datasets

The best live alternatives to mcp-registry/io.github.pipeworx-io/cms/search_datasets right now are mcp-registry/io.github.pipeworx-io/data-montgomery/montgomery_datasets, mcp-registry/io.github.pipeworx-io/healthdata/search_datasets, mcp-registry/io.github.pipeworx-io/data-cambridge/cambridge_datasets, mcp-registry/io.github.pipeworx-io/data-colorado/datasets, mcp-registry/io.github.pipeworx-io/data-maryland/datasets — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/cms/search_datasets itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/data-montgomery/montgomery_datasets	io.github.pipeworx-io/data-montgomery	live status →
mcp-registry/io.github.pipeworx-io/healthdata/search_datasets	io.github.pipeworx-io/healthdata	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-colorado/datasets	io.github.pipeworx-io/data-colorado	live status →
mcp-registry/io.github.pipeworx-io/data-maryland/datasets	io.github.pipeworx-io/data-maryland	live status →
mcp-registry/io.github.pipeworx-io/data-connecticut/datasets	io.github.pipeworx-io/data-connecticut	live status →
mcp-registry/io.github.pipeworx-io/data-fcc/datasets	io.github.pipeworx-io/data-fcc	live status →
mcp-registry/io.github.pipeworx-io/data-mesa/datasets	io.github.pipeworx-io/data-mesa	live status →
mcp-registry/io.github.pipeworx-io/cdc/search_datasets	io.github.pipeworx-io/cdc	live status →
mcp-registry/io.github.pipeworx-io/data-michigan/datasets	io.github.pipeworx-io/data-michigan	live status →
mcp-registry/io.github.pipeworx-io/data-mo/datasets	io.github.pipeworx-io/data-mo	live status →
mcp-registry/io.github.pipeworx-io/data-cookcounty/datasets	io.github.pipeworx-io/data-cookcounty	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/cms/search_datasets?

mcp-registry/io.github.pipeworx-io/data-montgomery/montgomery_datasets is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/healthdata/search_datasets, mcp-registry/io.github.pipeworx-io/data-cambridge/cambridge_datasets, mcp-registry/io.github.pipeworx-io/data-colorado/datasets, mcp-registry/io.github.pipeworx-io/data-maryland/datasets. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/cms/search_datasets down right now?

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