ClinicalTrials.gov MCP integration for AI agents.
Connect AI agents to ClinicalTrials.gov through 14 structured actions, including get api version, get field value statistics, and get list field size statist…
- ACTION CONTRACTS
- 14
- AUTHENTICATION
- No account authorization
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the ClinicalTrials.gov integration exposes
The ClinicalTrials.gov Agent App exposes 14 provider-backed actions for data work. Its current contract lets an authorized agent get the current clinicaltrials.gov api version and daily data refresh timestamp, get value statistics for selected clinicaltrials.gov leaf fields or field data types, and get observed list-size statistics for selected clinicaltrials.gov array fields. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses No account authorization. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected ClinicalTrials.gov account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ClinicalTrials.gov capabilities.
Showing 12 of 14 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_api_versionREADGet the current ClinicalTrials.gov API version and daily data refresh timestamp.
get_field_value_statisticsREADGet value statistics for selected ClinicalTrials.gov leaf fields or field data types.
INPUTS: types / fields
get_list_field_size_statisticsREADGet observed list-size statistics for selected ClinicalTrials.gov array fields.
INPUTS: fields
get_registry_size_statisticsREADGet ClinicalTrials.gov registry counts and the distribution of study JSON record sizes.
get_studies_by_nct_idsREADGet multiple ClinicalTrials.gov studies by NCT identifier and report identifiers that were not found.
INPUTS: nctIds / fields / markupFormat
get_studyREADGet one ClinicalTrials.gov study by NCT identifier.
INPUTS: nctId / fields / markupFormat
get_study_documentsREADList uploaded study protocols, statistical analysis plans, and informed consent forms with their official metadata.
INPUTS: nctId
get_study_eligibilityREADGet patient-facing eligibility criteria, age and sex requirements, and study population details for one ClinicalTrials.gov study.
INPUTS: nctId / markupFormat
get_study_locationsREADGet study sites, geographic coordinates, central contacts, local contacts, and study officials for one ClinicalTrials.gov study.
INPUTS: nctId
get_study_metadataREADGet the official ClinicalTrials.gov study data model and field definitions.
INPUTS: includeIndexedOnly / includeHistoricOnly
get_study_resultsREADGet posted participant flow, baseline characteristics, outcome measures, adverse events, and result notes for one ClinicalTrials.gov study.
INPUTS: nctId / markupFormat
list_enumsREADList official ClinicalTrials.gov enumeration types, values, legacy values, and field usages.
INPUT CONTRACTS
Know what the action needs before it runs.
get_field_value_statistics
typesOPTIONAL- The field data types to include.
fieldsOPTIONAL- The piece names or full leaf field paths to include.
get_list_field_size_statistics
fieldsOPTIONAL- The piece names or full list field paths to include.
get_studies_by_nct_ids
nctIdsREQUIRED- The NCT identifiers to retrieve.
fieldsOPTIONAL- Additional official fields to return alongside the fields required for the normalized study summary.
markupFormatOPTIONAL- The format used for fields whose official data type is markup.
get_study
nctIdREQUIRED- The ClinicalTrials.gov identifier, such as NCT04280705.
fieldsOPTIONAL- Additional official fields to return alongside the fields required for the normalized study summary.
markupFormatOPTIONAL- The format used for fields whose official data type is markup.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Api Version
Get the current ClinicalTrials.gov API version and daily data refresh timestamp. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_api_versionVerify with Get Field Value Statistics
Get value statistics for selected ClinicalTrials.gov leaf fields or field data types. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_field_value_statisticsSAFETY BOUNDARY
Operate ClinicalTrials.gov with explicit limits
- Authorize ClinicalTrials.gov with No account authorization and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned ClinicalTrials.gov data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in ClinicalTrials.gov rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ClinicalTrials.gov task completed successfully.
CONNECTION MODEL
No account authorization
ClinicalTrials.gov uses No account authorization. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 14
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by ClinicalTrials.gov.