Health Canada Drug Product Database MCP Server
Related Servers
Alternatives to Health Canada Drug Product Database MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying the Health Canada Drug Product Database for approved drugs, including brand names, DINs, active ingredients, strengths, dosage forms, routes, and market status.87 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables checking drug-drug interactions, resolving drug names or products, and retrieving structured drug monographs (indication, mechanism of action, dosing, adverse effects) via the DrugBank Clinical API.113 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables querying the Swissmedic authorised human medicines register, including search, product details, recent changes, and dataset metadata.64 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables querying openFDA for drug label text, Drugs@FDA application records, and device submission and product-code classification data, including end-to-end validation of device application details. It also supports an experimental sweep of drug labels for real-world-evidence vocabulary.76 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables users to query standardized drug concepts from the National Library of Medicine's RxNorm, including name-based search, drug property retrieval, and related concept exploration via the RxNav REST API.83 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables querying NCATS Inxight Drugs for any substance's indications with the highest development phase reached per condition, approval history, originator, targets, and cross-reference identifiers, plus free-text substance search and reverse lookup of drugs by disease. Supports drilling into clinical-stage programs and resolving condition labels, with graceful handling of unknown drugs or conditions.77 npmMIT
TDQS
Scored across 15 tools
Each tool targets a distinct resource or attribute (e.g., active ingredients, company, dosage form, packaging). Getter and search functions are clearly separated, with no overlapping purposes. The only potential overlap between `get_drug_product` and `get_all_drug_info` is resolved by explicit descriptions of basic vs. comprehensive info.
All tool names follow a consistent snake_case verb_noun pattern: `get_<attribute>` or `search_<entity>`. The getters are uniformly prefixed with `get_`, and the search tools with `search_`. No mixed conventions or vague verbs.
At 15 tools, the set sits at the upper boundary of an appropriately scoped server. Each getter addresses a specific drug product attribute, and `get_all_drug_info` provides a useful aggregate. There is no redundancy or unnecessary expansion.
The server covers all major drug product attributes, including active ingredients, company, dosage form, packaging, pharmaceutical standard, route, schedule, status, therapeutic class, and veterinary species. Searches by DIN and brand name cover primary lookup methods. However, there is no reverse lookup to find drugs by active ingredient or company, which is a notable gap for a drug database.