mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_compounds / alternatives

Live alternatives to mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_compounds

The best live alternatives to mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_compounds right now are mcp-registry/ai.nullary/nullary/search_inactive_compounds, mcp-registry/io.github.pipeworx-io/mychem/query, mcp-registry/io.github.nhoverte/biocosm/find_by_target, mcp-registry/ai.nullary/nullary/get_compound, mcp-registry/io.github.a0985344368-glitch/tsung-ai/compound_search — capability-matched and ranked by current reliability. mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_compounds itself is currently "healthy".

alternative	server
mcp-registry/ai.nullary/nullary/search_inactive_compounds	ai.nullary/nullary	live status →
mcp-registry/io.github.pipeworx-io/mychem/query	io.github.pipeworx-io/mychem	live status →
mcp-registry/io.github.nhoverte/biocosm/find_by_target	io.github.nhoverte/biocosm	live status →
mcp-registry/ai.nullary/nullary/get_compound	ai.nullary/nullary	live status →
mcp-registry/io.github.a0985344368-glitch/tsung-ai/compound_search	io.github.a0985344368-glitch/tsung-ai	live status →
mcp-registry/com.claidex/failure-intelligence/query_chembl	com.claidex/failure-intelligence	live status →
mcp-registry/io.github.pipeworx-io/chembl/search	io.github.pipeworx-io/chembl	live status →
mcp-registry/io.github.pipeworx-io/dailymed/search_drugs	io.github.pipeworx-io/dailymed	live status →
mcp-registry/org.memoryapi/bio/get_compound_data	org.memoryapi/bio	live status →
mcp-registry/io.github.rootsbymenda/pharma-regulatory/search_pharma	io.github.rootsbymenda/pharma-regulatory	live status →
mcp-registry/io.github.pipeworx-io/clinicaltables/drugs	io.github.pipeworx-io/clinicaltables	live status →
mcp-registry/ai.nullary/nullary/search_failed_selectivity	ai.nullary/nullary	live status →

FAQ

What is the best alternative to mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_compounds?

mcp-registry/ai.nullary/nullary/search_inactive_compounds is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/mychem/query, mcp-registry/io.github.nhoverte/biocosm/find_by_target, mcp-registry/ai.nullary/nullary/get_compound, mcp-registry/io.github.a0985344368-glitch/tsung-ai/compound_search. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_compounds down right now?

mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_compounds's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.hifarrer%2Fcure-cancer-with-ai%2Fsearch_compounds.

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.hifarrer%2Fcure-cancer-with-ai%2Fsearch_compounds or MCP find_alternatives. Check mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_compounds's live status: https://glimind.com/tool/mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_compounds.