Skip to main content
Glama

Related Servers

Alternatives to BioMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      This MCP server provides 16 intelligent tools for searching, retrieving, and linking biomedical literature from PubMed and PMC. It enables LLM applications to perform complex queries, batch processing, and cross-database linking.
      16
      8
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that gives AI assistants access to biological and biomedical RDF databases via SPARQL at the RDF Portal, as well as selected REST APIs (NCBI E-utilities, UniProt, ChEMBL, PDB, Reactome, Rhea, MeSH, and more).
      29
      18
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives LLMs live access to clinical trials, FDA drug recalls, adverse-event reports, drug labels, and drug-name normalization via six validated tools.
      6
      MIT
    • 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
      12
      -

    TDQS

    A3.5/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools follow a clear entity/action or entity/relation pattern, so gene_trials, variant_trials, drug_trials, and trial_search are distinguishable by name. A few fuzzy boundaries remain: discover overlaps with the domain searches, gene_get overlaps with ensembl_lookup, and gene_articles could be confused with article_search.

    Naming Consistency4/5

    The dominant convention is consistent: entity_search/entity_get pairs and entity_relation tools like disease_drugs and gene_trials all use snake_case noun-first names. Generic outliers (discover, pdb, batch_get) and source-prefixed tools (ensembl_*, gtex_*) break the pattern slightly.

    Tool Count2/5

    41 tools is a very large surface, exceeding the 25+ threshold for 'too many' regardless of how well-named they are. The broad biomedical scope justifies some size, but many search/get/relation tools could plausibly be consolidated into parameterized endpoints to reduce agent navigation cost.

    Completeness4/5

    The read-only biomedical surface is unusually thorough: all major entities have search/get plus cross-entity links (trials, drugs, diseases, articles, enrichment, expression, homology). Minor gaps remain, such as no direct variant-disease or disease-article endpoint, but they are workaroundable via existing search tools.

    Maintenance

    ActivityActive
    ResponsivenessResponsive