Skip to main content
Glama

Related Servers

Alternatives to MedBridge

No user-submitted related servers found.

    Related Servers

    • 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.
      41
      692 npm
      12
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that lets an LLM answer a pharmacist's question about drug shortages by normalizing drug names, finding pharmacologic alternatives, and checking their shortage status using public FDA and NLM data.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server with 60 tools connecting AI assistants to Czech healthcare databases (SUKL, MKN-10, NRPZS) and global biomedical sources (PubMed, ClinicalTrials.gov, OpenFDA).
      1
      MIT
    • 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

    TDQS

    A4.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct data type and action: trials are split between search (list) and get (detail), while drug tools cleanly separate recalls, adverse-event reports, labels, and name normalization. The descriptions reinforce the boundaries and cross-reference each other, so an agent should rarely misselect.

    Naming Consistency5/5

    All tools use an imperative verb + object pattern in snake_case: get_trial, search_trials, search_drug_recalls, get_adverse_events, get_drug_label, normalize_drug_name. The only variation is singular versus plural object forms, which aligns with whether a tool returns one record or many.

    Tool Count5/5

    Six tools is a focused, appropriate size for a medical-information server that spans clinical trials and FDA drug data. No tool feels redundant, and the set is small enough to avoid agent decision overhead.

    Completeness5/5

    The trial workflow is complete: search results point to a full-record getter with eligibility criteria and locations. The drug side covers name resolution, recalls, adverse-event summaries, and labels, with no obvious dead ends for a read-only informational server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues