Skip to main content
Glama
achillesrasquinha

life-science-mcp

by achillesrasquinha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to life-science-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • NCBI Entrez MCP Server

      QuentinCody
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides access to NCBI's scientific databases including E-utilities, PubChem, and PMC APIs for biomedical literature search, molecular data retrieval, and research through natural language queries.
      3
      -
    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.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: searching for tools, retrieving schema details, and executing tools. There is no overlap between these operations.

    Naming Consistency5/5

    All tool names follow a consistent verb-noun camelCase pattern: searchTools, getToolInfo, callTool. The naming is uniform and predictable.

    Tool Count5/5

    With only 3 tools, the server is minimal yet appropriately scoped for its role as a meta-server. It provides the essential discover, inspect, and execute operations without unnecessary bloat.

    Completeness5/5

    The server covers the full lifecycle for interacting with external life science tools: discover via search, understand via getToolInfo, and run via callTool. No obvious gaps in this proxy-like design.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources