Skip to main content
Glama
openpharma-org

Unofficial HPO MCP Server

by openpharma-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Unofficial HPO MCP Server

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.
      181 npm
      MIT

    • hpo-link

      berntpopp
      A
      license
      A
      quality
      A
      maintenance
      MCP server that provides tools for querying the Human Phenotype Ontology (HPO) including term lookup, hierarchy exploration, cross-ontology mappings, and gene-phenotype-disease associations, all grounded in a local SQLite database for fast offline lookups.
      17
      1
      MIT

    • mcp-ebi-ols

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and browsing ontologies from the EBI Ontology Lookup Service, including searching for terms, retrieving term details, and navigating ontology hierarchies via natural language.
      327 npm
      MIT

    • clingen-link

      berntpopp
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables querying ClinGen curated evidence for gene-disease validity, dosage, actionability, and variant pathogenicity via MCP tools.
      MIT

    • mcp-monarch-initiative

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying of the Monarch Initiative biomedical knowledge graph for genes, diseases, phenotypes, and their associations through natural language or direct tool calls.
      2 npm
      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

    A3.8/5.0

    Scored across 12 tools

    Disambiguation5/5

    All tools have clearly distinct purposes: single/batch retrieval, hierarchy navigation (ancestors, parents, children, descendants, path), comparison, search, validation, and statistics. No meaningful overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern, predominantly using the prefix 'hpo'. Variations like 'batch_get' vs 'get' are logical and maintain clarity.

    Tool Count5/5

    12 tools is an appropriate scope for an HPO term server, covering all essential operations without unnecessary bloat or shortage.

    Completeness5/5

    The server provides comprehensive coverage for a read-only HPO term service: retrieval, hierarchy traversal, comparison, search, validation, and statistics. There are no obvious gaps for its intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources