Skip to main content
Glama
CORE-Lab-Research

biocontext

by CORE-Lab-Research
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to biocontext

No user-submitted related servers found.

    Related Servers

    • MyGene MCP Server

      nickzren
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to query gene annotations, expression, pathways, variants, and more via the MyGene.info API, supporting batch operations and multiple biological data sources.
      26
      MIT

    • GenomeMCP

      Eldergenix
      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

    • life-science-mcp

      achillesrasquinha
      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

    • BioBTree

      tamerh
      A
      license
      Not graded
      quality
      A
      maintenance
      A unified biomedical graph database that integrates 50+ primary data sources — genes, proteins, compounds, diseases, pathways, and clinical data — into a single queryable graph with billions of cross-reference edges. Its native MCP server gives LLMs direct access to structured, authoritative biomedical data, complementing their reasoning with reliable identifiers and up-to-date database content.
      20
      AGPL 3.0

    • gwas-mcp

      muslus
      A
      license
      C
      quality
      F
      maintenance
      Provides AI-powered access to major biological databases for GWAS and bioinformatics research. Enables natural language queries for protein, gene, variant, pathway, and drug discovery analysis.
      44
      1
      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 3 tools

    Disambiguation4/5

    Tools are largely distinct: get_protein_info fetches protein details by accession, while resolve_gene and batch_resolve_genes both handle gene resolution. The overlap between single and batch resolution is clear from descriptions, so an agent can choose appropriately without much confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: get_protein_info, batch_resolve_genes, resolve_gene. Even the batch_ prefix maintains a clear convention, making the naming uniform and predictable.

    Tool Count4/5

    With only 3 tools, the server is minimal but well-scoped for the domain of gene and protein resolution. While it's on the lower end of typical counts, the tools cover core operations for this focused purpose, so the count feels appropriate rather than thin.

    Completeness3/5

    The server covers single and batch gene resolution plus protein lookup by accession, but lacks operations like batch protein retrieval or direct gene-to-protein mapping. Agents may need to chain resolve_gene and get_protein_info manually, representing a notable gap in seamless workflow completion.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources