Health Canada Drug Product Database (fleet #522).
MCPpedia last refreshed this data
io.github.pipeworx-io/health-canada-drugs is an MCP server that health Canada Drug Product Database (fleet #522). Its tool list has not been published yet over http, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"health-canada-drugs": {
"url": "https://gateway.pipeworx.io/health-canada-drugs/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Health Canada Drug Product Database (fleet #522).
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @pipeworx/mcp-health-canada-drugs against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in data
Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
Manage Supabase projects — databases, auth, storage, and edge functions
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/health-canada-drugs and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Every drug authorised for sale in Canada: DIN, brand name, active ingredients with strengths, dosage form, route, market status and the company behind it.
Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
This is Canadian marketing authorisation. US approvals and labels are openfda and dailymed; the two are separate regulatory acts and a drug can be authorised in one and not the other. Tools are prefixed health_canada_* so they never win a generic drug question.
| Tool | Answers |
|---|---|
health_canada_search_drugs | Is Tylenol approved in Canada? — brand-name search, returns DINs |
health_canada_drug_detail | What is DIN 01933655? — ingredients, strengths, form, route, status |
health_canada_drugs_by_ingredient | Which Canadian drugs contain acetaminophen? |
Keyless. No registration.
brandname; the JSON field is brand_name. Measured: ?brandname=ACTIFED → 3,576 bytes; ?brand_name=ACTIFED → 15,040,036 bytes; ?search=ACTIFED → 15,040,036 bytes. Matching the response field name is the natural guess and it is the wrong one. This pack whitelists the working parameters and throws rather than send an unknown one.id= means different things on different endpoints. On /drugproduct/, /activeingredient/, /status/, /form/ and /route/ it is the drug code. On /company/ it is the company code. Drug 11685 is ACTIFED PLUS CAPLET (Glaxo Wellcome); company 11685 is DERMAL DEFENSE, INC. of Michigan. Passing a drug code to /company/ returns a real record for an unrelated firm with nothing to signal the switch — so the company is read from the drug's own record and /company/ is never called with a drug code here.01933655 is not 1933655.companyname and company_name return the full 1.4 MB company list, so company search is deliberately not offered rather than shipped as a 1.4 MB-per-call tool.Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"health-canada-drugs": {
"url": "https://gateway.pipeworx.io/health-canada-drugs/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/health-canada-drugs/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas