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

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

The best live alternatives to mcp-registry/io.github.pipeworx-io/openfema/query_dataset right now are mcp-registry/io.github.pipeworx-io/data-nantes/query, mcp-registry/io.github.pipeworx-io/opendatasoft/records, mcp-registry/io.github.pipeworx-io/data-fulton/datasets, mcp-registry/io.github.pipeworx-io/data-fulton/metadata, mcp-registry/io.github.pipeworx-io/opendatasoft/datasets — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/openfema/query_dataset itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/data-nantes/query	io.github.pipeworx-io/data-nantes	live status →
mcp-registry/io.github.pipeworx-io/opendatasoft/records	io.github.pipeworx-io/opendatasoft	live status →
mcp-registry/io.github.pipeworx-io/data-fulton/datasets	io.github.pipeworx-io/data-fulton	live status →
mcp-registry/io.github.pipeworx-io/data-fulton/metadata	io.github.pipeworx-io/data-fulton	live status →
mcp-registry/io.github.pipeworx-io/opendatasoft/datasets	io.github.pipeworx-io/opendatasoft	live status →
mcp-registry/io.github.pipeworx-io/folketinget-dk/query_entity	io.github.pipeworx-io/folketinget-dk	live status →
mcp-registry/io.github.pipeworx-io/data-rennes/query	io.github.pipeworx-io/data-rennes	live status →
mcp-registry/io.github.pipeworx-io/data-paris/query	io.github.pipeworx-io/data-paris	live status →
mcp-registry/io.github.pipeworx-io/data-oregon/datasets	io.github.pipeworx-io/data-oregon	live status →
mcp-registry/io.github.pipeworx-io/cbs-nl/get_data	io.github.pipeworx-io/cbs-nl	live status →
mcp-registry/io.github.pipeworx-io/data-brussels/query	io.github.pipeworx-io/data-brussels	live status →
mcp-registry/io.github.pipeworx-io/data-gr/dataset	io.github.pipeworx-io/data-gr	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/data-nantes/query is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/opendatasoft/records, mcp-registry/io.github.pipeworx-io/data-fulton/datasets, mcp-registry/io.github.pipeworx-io/data-fulton/metadata, mcp-registry/io.github.pipeworx-io/opendatasoft/datasets. Glimind ranks alternatives by semantic similarity and live health.

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

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