Clinical trials across multiple registries with identifiers and source links.
Scored across 2 tools
The two tools have clearly distinct purposes: trials_get retrieves a single trial by ID, while trials_search performs field-based discovery. An agent can easily determine when to use each.
Both tools follow the same trials_verb convention with concise, predictable names. There is no mixing of naming styles.
Two tools are quite thin for a database server, even a read-only one. The surface may be sufficient for simple lookup and search, but it feels minimal.
The server covers retrieval and search, which are core read operations, but lacks obvious supporting operations such as listing, counts, field metadata, or any write/update lifecycle. If the domain is strictly read-only reference data this may be acceptable, but the surface has notable gaps.
Fetch one canonical trial by id, with every registry's provenance + cross-registry IDs.
Inputs: id (required).
Search trials by condition, intervention, sponsor, phase, status, country, or free text.
Inputs: q, limit, phase, cursor, +7 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
WHO ICTRP — the International Clinical Trials Registry Platform search portal…
Search and monitor ClinicalTrials.gov and EU trial registry records, with trial change tracking and
Clinical trial search and status from ClinicalTrials.gov
Clinical trials, RxNorm drug lookups, FDA drug and device data, PubMed and NHS organisations.
Add one secure layer between your agents and this server.