@pipeworx/tga-artg

Connect: https://gateway.pipeworx.io/tga-artg/mcp · Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 2

TGA ARTG — the Australian Register of Therapeutic Goods: every medicine, biological and medical device approved for supply in Australia. Search by product, active ingredient, sponsor or manufacturer, or pull the full record for one ARTG entry — sponsor, every ingredient with strength, indications, and links to its Product Information (PI) and Consumer Medicine Information (CMI) documents.

Scope — Australia, and only Australia

For the US use openfda; EU-wide, ema-medicines; UK, mhra-uk; Canada, health-canada-drugs; Spain, aemps-cima. Tools are prefixed artg_ so they never win a generic drug question.

Tools

Auth

Keyless. No registration.

Data source — NOT the documented “ARTG Search” tool

• https://data.tga.gov.au/ARTGSearch/ARTGWebService.svc/JSON/ARTGValueSearch/ — the WCF JSON web service that actually backs the register.

The TGA’s own documented ARTG Search tool — linked from tga.gov.au and, as of 2026, a beta Power Apps/Power BI portal at compliance.health.gov.au/artg — is interactive-only: a rendered visual with no query API behind it. tga.gov.au itself is also unreachable from our egress (its Akamai front end times out on every request, including a bare static PDF — a silent connection hold, not a 403). This pack instead calls the JSON web service that genuinely backs the register, at the separate, reachable host data.tga.gov.au — the same service TGA’s own internal client library (aehrc/tga-feed-client on GitHub) is built against. It is keyless, live, and answers per query — a proxy, not a mirror.

Things the next person would otherwise rediscover

• The path segment must be uppercase JSON. Lowercase json (the form quoted in most third-party documentation, including the aehrc client’s own example config) 404s with a generic WCF “Endpoint not found” HTML page — which is a 200-shaped failure if you don’t check for an HTML body where JSON was expected. This pack throws explicitly if the response starts with <.
• pagestart/pageend are a 1-indexed, INCLUSIVE RECORD RANGE, not a page number. pagestart=3&pageend=5 returns records 3, 4 and 5 (three rows). Omitting both silently returns the entire ARTG register (25,000+ active entries) in ARTG-ID order, ignoring every other filter — every call here sends an explicit pagestart=1/pageend=<limit>.
• ARTGValueSearch filtered by licenceid alone returns the single full record — there is no separate working lookup-by-ID endpoint on this host (ARTGEntryJson 404s), so artg_entry is built on the same search operation with licenceid as the only filter.
• www.tga.gov.au is unreachable from our network — do not build against it. data.tga.gov.au (a distinct host, no Akamai) is what actually answers.

Tools

• artg_search — Search the Australian Register of Therapeutic Goods (ARTG) — every medicine, biological and medical device approved for supply in Australia — by product name, active ingredient, sponsor, or manufactur
• artg_entry — Full Australian Register of Therapeutic Goods (ARTG) record for one entry, by ARTG ID (LicenceId, from artg_search). Returns sponsor, every active/excipient ingredient with strength, dosage form, rout