mcp-registry/com.crashstory/crashstory/query_research_dataset / alternatives

Live alternatives to mcp-registry/com.crashstory/crashstory/query_research_dataset

The best live alternatives to mcp-registry/com.crashstory/crashstory/query_research_dataset right now are mcp-registry/io.github.xaviviro/opendata-cat/query_dataset, mcp-registry/io.github.pipeworx-io/bts/query_dataset, mcp-registry/co.sofya/sofya/research, mcp-registry/io.github.rubix1138/askew-x402/askew_research_query, mcp-registry/io.github.valuein/mcp-sec-edgar/search_reports — capability-matched and ranked by current reliability. mcp-registry/com.crashstory/crashstory/query_research_dataset itself is currently "healthy".

alternativeserver
mcp-registry/io.github.xaviviro/opendata-cat/query_datasetio.github.xaviviro/opendata-catlive status →
mcp-registry/io.github.pipeworx-io/bts/query_datasetio.github.pipeworx-io/btslive status →
mcp-registry/co.sofya/sofya/researchco.sofya/sofyalive status →
mcp-registry/io.github.rubix1138/askew-x402/askew_research_queryio.github.rubix1138/askew-x402live status →
mcp-registry/io.github.valuein/mcp-sec-edgar/search_reportsio.github.valuein/mcp-sec-edgarlive status →
mcp-registry/com.selloracle/etsy-data/search_keywordscom.selloracle/etsy-datalive status →
mcp-registry/com.dropwatchhq/research-intel/search_recordscom.dropwatchhq/research-intellive status →
mcp-registry/io.github.pipeworx-io/estat-japan/search_statsio.github.pipeworx-io/estat-japanlive status →
mcp-registry/io.github.pipeworx-io/eurostat/search_datasetsio.github.pipeworx-io/eurostatlive status →
mcp-registry/io.github.pipeworx-io/datos-co/query_datasetio.github.pipeworx-io/datos-colive status →
mcp-registry/com.daedalmap/wildfires/query_datasetcom.daedalmap/wildfireslive status →
mcp-registry/com.daedalmap/hurricanes/query_datasetcom.daedalmap/hurricaneslive status →

FAQ

What is the best alternative to mcp-registry/com.crashstory/crashstory/query_research_dataset?

mcp-registry/io.github.xaviviro/opendata-cat/query_dataset is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/bts/query_dataset, mcp-registry/co.sofya/sofya/research, mcp-registry/io.github.rubix1138/askew-x402/askew_research_query, mcp-registry/io.github.valuein/mcp-sec-edgar/search_reports. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.crashstory/crashstory/query_research_dataset down right now?

mcp-registry/com.crashstory/crashstory/query_research_dataset's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.crashstory%2Fcrashstory%2Fquery_research_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%2Fcom.crashstory%2Fcrashstory%2Fquery_research_dataset or MCP find_alternatives. Check mcp-registry/com.crashstory/crashstory/query_research_dataset's live status: https://glimind.com/tool/mcp-registry/com.crashstory/crashstory/query_research_dataset.