mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names

The best live alternatives to mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names right now are mcp-registry/io.github.pipeworx-io/medlineplus/connect, mcp-registry/io.github.pipeworx-io/mesh/search_descriptors, mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes, mcp-registry/io.github.pipeworx-io/mydisease/disease, mcp-registry/com.claidex/failure-intelligence/query_clinicaltrials — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/medlineplus/connect	io.github.pipeworx-io/medlineplus	live status →
mcp-registry/io.github.pipeworx-io/mesh/search_descriptors	io.github.pipeworx-io/mesh	live status →
mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes	io.github.pipeworx-io/hpo-api	live status →
mcp-registry/io.github.pipeworx-io/mydisease/disease	io.github.pipeworx-io/mydisease	live status →
mcp-registry/com.claidex/failure-intelligence/query_clinicaltrials	com.claidex/failure-intelligence	live status →
mcp-registry/io.github.pipeworx-io/clinicaltrials/ct_search	io.github.pipeworx-io/clinicaltrials	live status →
mcp-registry/io.github.pipeworx-io/opentargets/disease	io.github.pipeworx-io/opentargets	live status →
mcp-registry/org.pinnacleblooms/ask/lookup_code	org.pinnacleblooms/ask	live status →
mcp-registry/io.github.hifarrer/cure-cancer-with-ai/search_oncology	io.github.hifarrer/cure-cancer-with-ai	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/data_clinical_trials	io.github.ColinHughes2121/gocreative-agent-api	live status →
mcp-registry/io.github.pipeworx-io/chembl/drug_indications	io.github.pipeworx-io/chembl	live status →
mcp-registry/io.github.pipeworx-io/opentargets/search	io.github.pipeworx-io/opentargets	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names?

mcp-registry/io.github.pipeworx-io/medlineplus/connect is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/mesh/search_descriptors, mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes, mcp-registry/io.github.pipeworx-io/mydisease/disease, mcp-registry/com.claidex/failure-intelligence/query_clinicaltrials. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names down right now?

mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fclinicaltables%2Fdisease_names.

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%2Fclinicaltables%2Fdisease_names or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names.