Zovo Trial Finder
Server Details
Recruiting trials near you
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools target clearly different entry points: discovery by condition/city versus retrieval of a single study by NCT ID. Descriptions explicitly state when each applies and even list what they do not do, leaving no realistic chance of misselection.
Both names follow the same verb_noun snake_case convention (find_recruiting_trials, get_trial_details). The verbs also match the actions accurately—'find' for search, 'get' for single-record retrieval.
Two tools is on the thin side of the typical 3-15 range, but for a narrowly scoped trial-finder the search/detail split covers the essential interaction pattern without bloat. It could arguably use one more operation, but nothing is redundant.
The core lifecycle (discover trials by condition/location, then drill into a specific NCT record for eligibility, sites, and contacts) is covered end to end, including export formats. Minor gaps exist—no way to list available conditions or compare multiple trials side by side—but agents can work around these via the search tool.
Available Tools
2 toolsfind_recruiting_trialsFind recruiting clinical trialsARead-onlyIdempotentInspect
Use this when someone wants recruiting clinical trials for a condition, optionally near a city, as a shortlist to discuss with a doctor. Returns up to 10 studies from live ClinicalTrials.gov records, sorted by distance to the nearest open site and then by recruiting status, with eligibility at a glance, contacts and a PDF and CSV. Does not give medical advice, judge which trial is better, or check whether a person qualifies. Do not use for drug prices or treatment recommendations.
Inputs: condition (required), age, sex, city, +5 more. Returns: notes, query, shown, source, +7 more
get_trial_detailsGet clinical trial detailsARead-onlyIdempotentInspect
Use this when someone gives a ClinicalTrials.gov ID (NCT number) and wants that study's eligibility criteria, open sites, contacts and status from the live record, with a PDF and a CSV of open sites. Add a city to sort sites by distance. Does not give medical advice or check whether a person qualifies.
Inputs: nct_id (required), city, state, country. Returns: notes, sites, trial, source, +3 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Search recruiting US clinical trials by city, condition, phase and patient eligibility.
Search ClinicalTrials.gov by condition, drug, location and status, with full trial details
Clinical trial search and status from ClinicalTrials.gov
Search and monitor ClinicalTrials.gov and EU trial registry records, with trial change tracking and
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables searching and querying clinical trials from ClinicalTrials.gov with intelligent filtering for recruiting studies, geographic search, and detailed trial information including contacts and eligibility criteria.31 npm6MIT
- AlicenseNot gradedqualityCmaintenanceClinical Trials AI - MCP server providing AI-powered tools and automation by MEOK AI Labs6 npm39 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceEnables searching ClinicalTrials.gov's 600K+ registered studies with full-text and field-specific queries, status/phase/geographic filters, and field discovery. Also retrieves full study records and posted results, and matches patient demographics and conditions to candidate recruiting trials.2,484 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables searching 600K+ ClinicalTrials.gov studies with field-specific, geographic, and advanced filters; fetching full protocol records, posted results, and field definitions. It also matches patient demographics and conditions to candidate recruiting trials via STDIO or Streamable HTTP.2,484 npmApache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.