Skip to main content
Glama

Related Servers

Alternatives to gwas-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI-driven pharmacogenomic analysis by querying structured genetic variant, drug response, and disease risk data. Supports natural language questions about medications, traits, and health risks based on user genome data, with privacy-first local execution.
      16
      28 npm
      12
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables unified access to 110 life science APIs and databases, including genomics, proteomics, chemistry, literature, and clinical data. Users can query genes, proteins, compounds, pathways, and more through natural language.
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to query clinical genomics databases, retrieve supporting literature, analyze population genetics, and visualize biological pathways.
      18
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for querying the GWAS Catalog (EBI/NHGRI), a curated catalog of genome-wide association studies. It enables AI agents to search and retrieve study data via natural language or direct tool calls.
      37 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables querying genomics data from the Alliance of Genome Resources across model organisms including human, mouse, rat, zebrafish, fly, worm, yeast, and xenopus. Supports gene searches, disease associations, expression data, orthologs, phenotypes, and molecular interactions through natural language.
      22
      18 npm
      MIT

    TDQS

    C2.9/5.0

    Scored across 44 tools

    Disambiguation2/5

    Many tools have overlapping purposes: multiple search tools for genes/proteins (search_ensembl_gene, search_ncbi_gene, search_uniprot) and multiple protein annotation tools (get_protein_details, get_protein_interactions, get_interaction_network). This creates ambiguity for an agent trying to select the right tool.

    Naming Consistency4/5

    Tool names follow a verb_noun pattern with underscores (e.g., annotate_snps, create_manhattan_plot). However, verbs are mixed (get_, search_, calculate_, create_), which is mostly consistent but not perfectly uniform. Minor deviations like 'calculate_genomic_inflation' vs 'ld_pruning' (no verb) reduce consistency slightly.

    Tool Count2/5

    44 tools is high for a GWAS server. Many tools are for searching external databases (10+ search_* tools) that could be consolidated. The server's scope is broad, but the number seems excessive and could overwhelm agents.

    Completeness3/5

    The server covers core GWAS analysis (run_gwas, clump_snps, create_manhattan_plot) and post-GWAS annotation (annotate_snps, enrichment, protein interactions). However, missing meta-analysis, imputation, and fine-mapping tools. Many search tools duplicate functionality, so coverage is moderate.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive