Skip to main content
Glama
Open Drug Data MCP
by knorby

Related Servers

Alternatives to Open Drug Data MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables looking up drug and molecule data — identifiers such as InChIKey, SMILES, CAS, and ChEMBL IDs, plus measured and computed properties and drug information — across PubChem, ChEMBL, and Wikidata. Every returned value carries its cited source, and it covers small molecules, peptides (including modified and cyclic forms), and conjugates such as antibody–drug conjugates.
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Provides access to the official FDA DailyMed database for comprehensive drug information, including drug labels, NDC codes, RxNorm mappings, pharmacologic classifications, and FDA application numbers through natural language queries.
      28
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to search authoritative drug, health statistics, medical literature, clinical guideline, clinical trial, and pediatric sources such as FDA, WHO, PubMed, RxNorm, and Google Scholar, with local privacy and no API keys.
      83 npm
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to resolve genes, diseases, chemicals, variants and species to normalized ids, search ~36M PubMed abstracts and PMC full texts by free text or entity, and retrieve the machine-extracted relations between them with the supporting sentences and PMIDs. Supports auditing individual relations with full evidence passages and pulling per-article entity annotations with character offsets.
      81 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and retrieving NIH Dietary Supplement fact sheets, NCCIH herb summaries, and real supplement product labels from the DSLD, including uses, safety, and medication interaction information.
      94 npm
      MIT

    TDQS

    A4.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    The product vs ingredient tools are clearly separated, and search/get/resolve roles are mostly distinct. There is some overlap around identifiers: an NDC can be used in search_products, get_product, and resolve_identifiers, though the descriptions explain the different purposes. Overall the boundaries are understandable but not perfectly crisp.

    Naming Consistency5/5

    All tools share a consistent `drugdata_` prefix and follow a predictable verb-plus-resource pattern such as search_products, get_product, and resolve_identifiers. `ping` is the only non-resource verb, but it is conventional and does not disrupt the pattern.

    Tool Count5/5

    Seven tools is a well-scoped set for a multi-source drug data server, with separate operations for products, ingredients, identifier resolution, references, and health checking. Each tool has a clear place and no bulk of redundant endpoints.

    Completeness4/5

    The surface covers searching and fetching products and ingredients, cross-source identifier resolution, reference search, and server health. Minor gaps exist in that reference results are link-first rather than retrievable records, and some specialized lookups depend on optional parameters, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues