Anzctr vs Clinicaltrials
A side-by-side look at the Anzctr and Clinicaltrials MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AnzctrBiology, Medicine and Bioinformatics · Local subprocess (stdio)ANZCTR — the Australian New Zealand Clinical Trials Registry40FairAuth: no auth requiredVerdict: choose Anzctr for biology, medicine and bioinformatics work as a local process; choose Clinicaltrials for biology, medicine and bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Anzctr when
- You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Clinicaltrials when
- You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
ct_search, ct_get_study, ct_count_by_condition.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Anzctr | |
|---|---|---|
| Category | Biology, Medicine and Bioinformatics | Biology, Medicine and Bioinformatics |
| Quality signal | 40/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Anzctr tools
No tool names declared yet. Check the project README from the listing page.
Clinicaltrials tools 14
ct_searchSearch ClinicalTrials.gov for clinical trials — find trials and look up a NAMED trial by keyword, condition, drug/therapy, status (e.g. 'Recruiting'), or phase (e.g. 'Phase 2'). Use for "clinical trials for <disease/drug>", or to locate a specific study like "the FLOW trial", "semaglutide kidney outcomes trial" (use ct_get_study for its full design/results). Returns NCT IDs, titles, status, enrollment, and sponsor info.ct_get_studyGet full trial details by NCT ID (e.g., 'NCT04567890'). Returns protocol, eligibility criteria, primary outcomes, sponsor, locations, and results.ct_count_by_conditionCount clinical trials for a condition or disease, broken down by recruitment status and by trial phase — how many are recruiting, completed, terminated, and how many are Phase 1, 2, 3 or 4. Use for landscape questions about how much trial activity a disease has and where it sits in development. Filtering by status or phase returns the filtered total without the breakdown.ct_sponsor_trialsList the trials a company LEADS on ClinicalTrials.gov, by sponsor or organization name. Returns status, phase, and conditions to map a research pipeline. Matches the registered lead-sponsor field, so trials another organisation runs using the company's drug are excluded unless sponsor_match asks for them.ct_compare_sponsorsCompare 2–5 NAMED lead sponsors on ClinicalTrials.gov under identical condition, recruitment-status, and phase filters. Returns full matching counts, a ranked comparison, and a small study sample for each sponsor. Use for questions like "who has more recruiting Phase 3 obesity trials, Novo Nordisk or Eli Lilly?" For an open "who are the TOP sponsors of X trials" question with no names given: the registry API has no group-by, so a true ranking is not computable — NEVER invent a candidate list to fake one; say the registry cannot rank sponsors and offer to compare specific named sponsors. Counts use the registered lead-sponsor field; registry records do not establish asset ownership, pipeline value, or probability of success.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Anzctr
{
"mcpServers": {
"anzctr": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-anzctr"
]
}
}
}
Clinicaltrials
{
"mcpServers": {
"clinicaltrials": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-clinicaltrials"
]
}
}
}
Frequently asked questions
Anzctr is categorized under Biology, Medicine and Bioinformatics and uses a local stdio subprocess. Clinicaltrials belongs to Biology, Medicine and Bioinformatics and uses a local stdio subprocess. Pick Anzctr for biology, medicine and bioinformatics work and Clinicaltrials for biology, medicine and bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Anzctr is listed as free. Auth: no auth required. Clinicaltrials has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add anzctr and clinicaltrials as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Anzctr has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Clinicaltrials has 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars.