4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Harvard ClinicalTrials MCP Server

Bring Clinical Trials
to CrewAI

Learn how to connect Harvard ClinicalTrials to CrewAI and start using 16 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Api VersionGet StudyGet Study ResultsGet Study TimelineSearch By ConditionSearch By InterventionSearch By LocationSearch By PhaseSearch By SponsorSearch CompletedSearch Device TrialsSearch Fda RegulatedSearch PediatricSearch Rare DiseasesSearch RecruitingSearch Studies

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Harvard ClinicalTrials

What is the Harvard ClinicalTrials MCP Server?

Connect to the ClinicalTrials.gov API v2 — the largest database of clinical studies worldwide, maintained by the U.S. National Library of Medicine.

What you can do

  • Study Search — Search 400K+ clinical trials from 220+ countries
  • Condition Filter — Find trials for specific diseases (cancer, diabetes, Alzheimer's)
  • Intervention Filter — Search by drug, device, or therapy name
  • Sponsor Search — Find trials by organization (Pfizer, NIH, Roche)
  • Phase Filter — Filter by Phase 1-4 to track drug development stages
  • Recruiting — Find trials currently enrolling participants
  • Location — Search by city or country for accessible trials
  • FDA Regulated — Filter for FDA-regulated drug and device trials
  • Pediatric — Find trials including children
  • Rare Diseases — Discover research for orphan conditions
  • Results — Get outcome data from completed studies

Who is this for?

  • Medical Researchers — systematic reviews and evidence synthesis
  • Clinicians — find trial evidence for treatment decisions
  • Patients — discover trials they may be eligible for
  • Pharma Professionals — competitive landscape and pipeline analysis

Built-in capabilities (16)

get_api_version

gov API version and the timestamp of the most recent data update. Useful for verifying data currency and API availability. Get API version and data timestamp

get_study

g. "NCT04368728"). Returns title, status, phase, enrollment, conditions, interventions, eligibility criteria, sponsor, and study locations. Get clinical trial details by NCT ID

get_study_results

Not all trials report results — this is most useful for completed Phase 2-4 studies. Get primary outcome results for a trial

get_study_timeline

Essential for understanding the progress and currency of a study. Get the complete timeline of a clinical trial

search_by_condition

Examples: "diabetes", "breast cancer", "Alzheimer disease", "COVID-19", "depression", "hypertension". Search trials by medical condition

search_by_intervention

Examples: "pembrolizumab", "metformin", "radiation therapy", "cognitive behavioral therapy". Search trials by drug or treatment

search_by_location

Essential for finding trials accessible to patients in a particular area. Search trials by geographic location

search_by_phase

Phase values: "PHASE1", "PHASE2", "PHASE3", "PHASE4", "EARLY_PHASE1". Phase 3 trials are the largest and most definitive, while Phase 1 trials focus on safety. Search trials by study phase

search_by_sponsor

Examples: "Pfizer", "National Cancer Institute", "Roche", "Novartis", "NIH". Search trials by sponsoring organization

search_completed

Completed trials are more likely to have published results and outcomes data. Search completed clinical trials

search_device_trials

Covers diagnostic devices, surgical tools, implants, and digital health technologies. Search medical device clinical trials

search_fda_regulated

S. Food and Drug Administration. These trials follow the most rigorous regulatory standards. Search FDA-regulated drug trials

search_pediatric

Essential for pediatricians, child health researchers, and parents seeking trials for children. Search pediatric clinical trials

search_rare_diseases

Examples: "cystic fibrosis", "sickle cell disease", "Huntington disease", "amyotrophic lateral sclerosis". Search rare disease clinical trials

search_recruiting

Essential for patients seeking to enroll in trials or researchers tracking active studies. Search for currently recruiting studies

search_studies

gov database of over 400,000 clinical studies from 200+ countries. Returns NCT IDs, titles, status, phases, sponsors, conditions, interventions, and locations. Search 400K+ clinical trials worldwide

Why CrewAI?

When paired with CrewAI, Harvard ClinicalTrials becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Harvard ClinicalTrials tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Harvard ClinicalTrials in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Harvard ClinicalTrials and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Harvard ClinicalTrials to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Harvard ClinicalTrials in CrewAI

The Harvard ClinicalTrials MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 16 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Harvard ClinicalTrials
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Harvard ClinicalTrials for CrewAI

Every tool call from CrewAI to the Harvard ClinicalTrials MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Do I need an API key?

No. ClinicalTrials.gov is completely free and public. No authentication required.

02

What are clinical trial phases?

Phase 1 tests safety in small groups; Phase 2 evaluates efficacy; Phase 3 confirms effectiveness in large populations; Phase 4 monitors post-approval. Each phase provides progressively stronger evidence.

03

Can patients find trials to enroll in?

Yes. Use the recruiting filter to find trials currently accepting participants. You can filter by condition, location, and eligibility criteria to find accessible trials.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →