A
licenseNot graded
qualityC
maintenanceEnables querying the Health Canada Drug Product Database for approved drugs, including brand names, DINs, active ingredients, strengths, dosage forms, routes, and market status.
MIT
Health Canada Drug Product Database MCP Server
by wkurzatz
Related Servers
Alternatives to Health Canada Drug Product Database MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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.MIT
- 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.1 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables querying FDA drug approvals, device clearances (510(k)), recalls, and adverse events via the openFDA API, providing tools for clinical and pharmaceutical research.1-
- AlicenseNot gradedqualityCmaintenanceSearch and retrieve FDA Structured Product Labels from DailyMed via NLM, supporting queries by drug name, NDC, RXCUI, and more.2 npmMIT
- AlicenseAqualityDmaintenanceEnables querying FDA drug label information including adverse reactions, warnings, and indications via natural language.56 npm1GPL 3.0
TDQS
A4/5.0
Scored across 15 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues