Skip to main content
Glama
axle962

bioretrieval-mcp

by axle962
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to bioretrieval-mcp

No user-submitted related servers found.

    Related Servers

    • BioMCP

      yeyuan98
      A
      license
      A
      quality
      A
      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.
      42
      352 npm
      12
      Apache 2.0

    • BioMCP

      qgeng1465
      F
      license
      B
      quality
      A
      maintenance
      BioMCP is an open-source MCP server that connects any AI assistant to 15 open bioinformatics databases with zero configuration. It provides 23 tools for literature, sequences, BLAST, structures, enrichment, annotations, genomes, interactions, variants, domains, compounds, and single-cell data.
      73
      24 PyPI
      14
      -

    • SciAgentKit

      ehsansyh
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP-native scientific skills for reproducible computational biology and AI-driven drug-discovery workflows. It combines deterministic scientific tools with an MCP server to give AI agents real computational capabilities.
      Apache 2.0

    • pubmed-mcp-server

      phamdunn2767
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching PubMed and Europe PMC, fetching article metadata and full text from PMC, Europe PMC, or Unpaywall, resolving citations and identifiers, exploring related articles, and grounding queries in MeSH vocabulary. Runs over stdio, local Streamable HTTP, or a hosted endpoint, exposing 11 tools, a database-info resource, and a research-plan prompt.
      9 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

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly different resource and action: EMDB search, UniProt entry retrieval, and GEO methylation series search. There is no realistic overlap in selection, even though EMDB results may contain UniProt cross-references.

    Naming Consistency5/5

    All tools use consistent snake_case verb_noun naming: search_emdb, get_uniprot, search_geo_methylation. The mix of search and get reflects the intended action rather than inconsistent conventions.

    Tool Count5/5

    Three tools is well within a focused retrieval server’s scope, and each covers a distinct biological data source. None appears redundant or gratuitous.

    Completeness3/5

    Coverage is uneven: UniProt has fetch but no search, while EMDB and GEO methylation have search but no dedicated full-entry retrieval beyond returned metadata. These are notable gaps for common retrieval workflows, though partial workarounds exist via cross-references and search metadata.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources