Open Drug Data MCP
Related Servers
Alternatives to Open Drug Data MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and MCP clients to query FDA drug labels, FAERS adverse-event reports, recalls, and label-documented drug interactions, returning structured, cited results.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseBqualityDmaintenanceProvides 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.283MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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 npmMIT
TDQS
Scored across 7 tools
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.
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.
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.
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.