mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_count_by_condition / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_count_by_condition

The best live alternatives to mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_count_by_condition right now are mcp-registry/org.memoryapi/clinical/get_trial_stats, mcp-registry/ai.dynamicfeed/dynamic-feed/clinical_trials, mcp-registry/org.memoryapi/clinical/search_trials, mcp-registry/ai.signal8/mcp/get_clinical_trials, mcp-registry/io.github.pipeworx-io/pharma-intel/pharma_pipeline_scan — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_count_by_condition itself is currently "healthy".

alternative	server
mcp-registry/org.memoryapi/clinical/get_trial_stats	org.memoryapi/clinical	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/clinical_trials	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/org.memoryapi/clinical/search_trials	org.memoryapi/clinical	live status →
mcp-registry/ai.signal8/mcp/get_clinical_trials	ai.signal8/mcp	live status →
mcp-registry/io.github.pipeworx-io/pharma-intel/pharma_pipeline_scan	io.github.pipeworx-io/pharma-intel	live status →
mcp-registry/io.github.nhoverte/biocosm/find_by_phase	io.github.nhoverte/biocosm	live status →
mcp-registry/io.github.pipeworx-io/idigbio/count_by_field	io.github.pipeworx-io/idigbio	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/trials_details	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.hifarrer/cure-cancer-with-ai/list_clinical_trials	io.github.hifarrer/cure-cancer-with-ai	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/trials_search	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/data_clinical_trials	io.github.ColinHughes2121/gocreative-agent-api	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/clinical-trials	ai.intuitek.the-stall/the-stall	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_count_by_condition?

mcp-registry/org.memoryapi/clinical/get_trial_stats is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.dynamicfeed/dynamic-feed/clinical_trials, mcp-registry/org.memoryapi/clinical/search_trials, mcp-registry/ai.signal8/mcp/get_clinical_trials, mcp-registry/io.github.pipeworx-io/pharma-intel/pharma_pipeline_scan. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_count_by_condition down right now?

mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_count_by_condition's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fclinicaltrials%2Fct_count_by_condition.

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%2Fclinicaltrials%2Fct_count_by_condition or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_count_by_condition's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_count_by_condition.