Skip to main content
Glama
berntpopp

hpo-link

by berntpopp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hpo-link

No user-submitted related servers found.

    Related Servers

    • hpo-api

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query Human Phenotype Ontology clinical phenotype terms, navigate term hierarchies, and retrieve gene-disease and disease-phenotype annotations through keyless MCP tools.
      383 npm
      MIT

    • orphanet-link

      berntpopp
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables querying rare-disease data from Orphanet, including disease nomenclature, cross-references, classifications, gene associations, HPO phenotypes, epidemiology, and natural history.
      19
      MIT

    • opentargets-mcp

      nickzren
      A
      license
      B
      quality
      A
      maintenance
      MCP 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.
      68
      71 PyPI
      19
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have crisp boundaries: direct vs transitive hierarchy (parents/ancestors, children/descendants) is explicitly contrasted in descriptions, and the inverse-direction pairs (get_genes_for_disease / get_diseases_for_gene, etc.) are unambiguous. The one soft overlap is resolve_xref vs resolve_term (which also accepts xref CURIEs) and map_cross_ontology, though descriptions disambiguate them adequately.

    Naming Consistency5/5

    Uniform snake_case with a consistent verb_noun convention throughout (get_term, get_term_ancestors, resolve_term, search_terms, map_cross_ontology). The relationship queries all follow the same 'get_X_for_Y' pattern, making the set highly predictable.

    Tool Count5/5

    17 tools is well-matched to a knowledge base spanning ontology navigation plus the gene/phenotype/disease annotation triangle. Each tool covers a distinct axis (resolution, search, hierarchy, cross-refs, annotation cross-products), so none feel redundant.

    Completeness4/5

    Strong coverage of term resolution, hierarchy traversal in both directions (direct and transitive), cross-refs both ways, and all six gene/phenotype/disease annotation directions. Minor gap: no direct record lookup for a disease or gene entity (metadata), and no annotation evidence/detail access, but core workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources