Skip to main content
Glama
mohammadnajeeb

NCBI Gene MCP Server

Related Servers

Alternatives to NCBI Gene MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for querying gene annotations, full-text gene search, and species taxonomy via MyGene.info. Enables AI agents to access gene data through natural language questions.
      15
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes STRING database functionality, allowing AI agents to resolve protein identifiers, retrieve interaction networks, perform homology lookups, and run functional enrichment analysis.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A high-performance MCP server that gives LLMs access to 25 biomedical tools federated across 50+ upstream APIs for genes, variants, drugs, diseases, literature, clinical trials, and structural biology.
      41
      522
      12
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes the UniProt REST API to LLM clients, enabling search and retrieval of protein data via tools like search_uniprotkb, get_entry, and map_ids.
      7
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Federates 13 gene-related MCP backends (gnomAD, GTEx, etc.) behind a single Streamable HTTP endpoint with collision-free namespacing and search-based tool discovery.
      4
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      MCP server for accessing NCBI PubMed/PMC databases, enabling search, retrieval of summaries and full records, citation export, and ID conversion through various APIs.
      12
      1
      -

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools have some overlap that could cause confusion, particularly between 'search_by_gene_symbol' and 'search_genes' which both search for genes but with different parameters. However, 'fetch_gene_info' and 'fetch_protein_info' are clearly distinct from each other and from the search tools, providing some clarity.

    Naming Consistency4/5

    The naming follows a consistent snake_case pattern with clear verb_noun structure (e.g., fetch_gene_info, search_genes). The only minor deviation is 'search_by_gene_symbol' which includes a preposition, but it still maintains readability and overall consistency with the other tools.

    Tool Count3/5

    With 4 tools, the count is borderline thin for a gene database server, as it might lack operations like updating or deleting data, but it covers basic fetch and search functionalities. It's reasonable for a focused scope but could benefit from more comprehensive coverage.

    Completeness3/5

    The server provides fetch and search operations for genes and proteins, but there are notable gaps such as no update, delete, or creation tools, which might be expected in a full CRUD lifecycle. It covers basic retrieval and search, but agents may hit dead ends for more complex tasks.