@pipeworx/anzctr

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/anzctr’s. Install: one-click buttons

Connect to just the @pipeworx/anzctr pack

https://gateway.pipeworx.io/anzctr/mcp — only @pipeworx/anzctr’s own tools, nothing else in the catalog.

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: 1

Australian New Zealand Clinical Trials Registry (ANZCTR, anzctr.org.au): the full registered record for one trial by ACTRN. ANZCTR is the WHO primary registry for Australia and New Zealand, and many of its trials are not on ClinicalTrials.gov.

Tools

  • anzctr_trial({actrn}) — the full record for one trial: titles, status, phase and design, health conditions and condition codes, intervention and comparator, primary and secondary outcomes, eligibility, target sample size, key dates, primary sponsor, funding sources, ethics committees, secondary IDs. An ACTRN with no public record returns found: false. Every response carries data_as_of (the time the registry was read).

Use alongside clinicaltrials (US registry) and isrctn (UK/international).

Search is not shipped yet

ANZCTR’s search (TrialSearch.aspx) is an ASP.NET WebForms postback. A working implementation exists in commit f1c44beb0 (anzctr_search: GET the form for its __VIEWSTATE and session cookie, POST it back with ctl00$body$searchTxtBx, interventionDescriptionTxtBx, healthConditionTxtBx, registryRdBtnLst=ANZCTR and the btnSearch button). On 2026-10-09 it returned 45 psilocybin records from a throwaway Worker on our Cloudflare account, but every call from the live gateway got a Cloudflare Managed Challenge (HTTP 403, “I’m Under Attack Mode - The University of Sydney”) on TrialSearch.aspx, while the record page answered normally. A laptop is challenged on the search page too. The egress relay (supabase/functions/egress-proxy) does not carry cookies, which the postback needs. Fleet #2897 carries the follow-up.

Auth

Keyless.

Data sources

ANZCTR has no JSON API; the record page is HTML with one <span id="ctl00_body_CX…"> per field and ctl00_body_repeater_TX…_ctlNN_CX… spans for repeated rows (conditions, outcomes, funders).

Things the next person would otherwise rediscover:

  • Some ACTRNs carry a trailing letter (ACTRN12626001117303p); the record page takes the 14 digits alone, and so does the tool.
  • The record page is answered from the live gateway and from a laptop; only TrialSearch.aspx is challenged.
  • An unknown ACTRN 302s to /Notification.aspx.
  • Records include contact persons with names, phone numbers and email addresses. The tool does not return them.

Tools

  • anzctr_trial — Full ANZCTR record for one trial by its ACTRN (e.g. “ACTRN12626001215314” or the 14 digits alone): titles, recruitment status, phase, study design, health conditions and condition codes, intervention

Tools

  • anzctr_trial — Full ANZCTR record for one trial by its ACTRN (e.g. ACTRN12626001215314 or the 14 digits alone): titles, recruitment status, phase, study design, health conditions and condition codes, intervention an

Regenerated from source · build October 9, 2026