mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes

The best live alternatives to mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes right now are mcp-registry/io.github.rarasai/raras/get_disease_detail, mcp-registry/io.github.rarasai/raras/find_diseases_by_phenotypes, mcp-registry/io.github.rarasai/raras/find_phenotypically_similar, mcp-registry/io.github.pipeworx-io/opentargets/disease, mcp-registry/io.github.pipeworx-io/mydisease/disease — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes itself is currently "healthy".

alternative	server
mcp-registry/io.github.rarasai/raras/get_disease_detail	io.github.rarasAI/raras	live status →
mcp-registry/io.github.rarasai/raras/find_diseases_by_phenotypes	io.github.rarasAI/raras	live status →
mcp-registry/io.github.rarasai/raras/find_phenotypically_similar	io.github.rarasAI/raras	live status →
mcp-registry/io.github.pipeworx-io/opentargets/disease	io.github.pipeworx-io/opentargets	live status →
mcp-registry/io.github.pipeworx-io/mydisease/disease	io.github.pipeworx-io/mydisease	live status →
mcp-registry/io.github.pipeworx-io/monarch-initiative/phenotype_to_gene	io.github.pipeworx-io/monarch-initiative	live status →
mcp-registry/io.github.rarasai/raras/search_phenotypes	io.github.rarasAI/raras	live status →
mcp-registry/io.github.pipeworx-io/clinicaltables/disease_names	io.github.pipeworx-io/clinicaltables	live status →
mcp-registry/io.github.pipeworx-io/clinicaltables/conditions	io.github.pipeworx-io/clinicaltables	live status →
mcp-registry/io.github.pipeworx-io/monarch-initiative/gene_to_disease	io.github.pipeworx-io/monarch-initiative	live status →
mcp-registry/io.github.pipeworx-io/opentargets/disease_associations	io.github.pipeworx-io/opentargets	live status →
mcp-registry/io.github.pipeworx-io/mydisease/metadata	io.github.pipeworx-io/mydisease	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes?

mcp-registry/io.github.rarasai/raras/get_disease_detail is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.rarasai/raras/find_diseases_by_phenotypes, mcp-registry/io.github.rarasai/raras/find_phenotypically_similar, mcp-registry/io.github.pipeworx-io/opentargets/disease, mcp-registry/io.github.pipeworx-io/mydisease/disease. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes down right now?

mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fhpo-api%2Fdisease_phenotypes.

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%2Fhpo-api%2Fdisease_phenotypes or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/hpo-api/disease_phenotypes.