hpo-link
Related Servers
Alternatives to hpo-link
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceProvides access to the Human Phenotype Ontology (HPO) API with tools for searching, browsing hierarchy, and analyzing phenotypic terms used in genetic research.12-
- AlicenseAqualityAmaintenanceAn MCP server that enables querying rare-disease data from Orphanet, including disease nomenclature, cross-references, classifications, gene associations, HPO phenotypes, epidemiology, and natural history.19MIT
- FlicenseBqualityDmaintenanceA production-ready Model Context Protocol (MCP) server that provides comprehensive access to the BioOntology API for searching, annotating, and exploring over 1,200 biological ontologies.109-
- AlicenseAqualityAmaintenanceMCP server that provides tools to query harmonized gene-disease validity data from the Gene Curation Coalition, supporting consensus and conflict detection for gene-disease assertions.12MIT
- AlicenseBqualityDmaintenanceMCP server that exposes the Open Targets Platform GraphQL API as a set of tools for querying biomedical data such as targets, diseases, drugs, and genetic evidence.6819MIT
- AlicenseNot gradedqualityDmaintenanceMCP servers for querying Brick and 223P ontologies, enabling abbreviation expansion, term/property lookup, and definition retrieval.5BSD 3-Clause
TDQS
Scored across 17 tools
Each tool has a clearly distinct purpose: diagnostics, term traversal, association queries, resolution, cross-reference mapping, and search. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., get_diseases_for_gene, get_term_ancestors, resolve_term). No mixing of conventions.
17 tools provide comprehensive coverage for an HPO linking service, covering term navigation, associations, resolution, search, and diagnostics without being excessive.
The tool surface covers term retrieval, hierarchical traversal, disease-gene-phenotype associations, cross-references, resolution, search, and server diagnostics. No obvious gaps for the intended read-only use case.