Skip to content
ToolCargo

A practical MCP workflow

Research registered study records with AI and MCP

Search ClinicalTrials.gov through ToolCargo, inspect selected exact NCT records and prepare a source-linked research list. Keep registry status, posted-results availability and dated milestones separate. Use Europe PMC for a separate publication search, then review original sources before assessing any evidence.

Built for: Research and editorial agents gathering public study-registration metadata.

What to connect

Create a ToolCargo account and use OAuth or an API key with a supported MCP client. Hosted connectors share your plan’s call quota; connect each required MCP endpoint separately. Review provider permissions before starting.

Client setup and test status · Current plans and limits

Run the workflow

  1. 1. Choose a public research topic

    Call clinicaltrials_search_studies with a topic you intend to share with the public registry, a small limit and an optional source status filter. Do not provide personal health details. Results are topic candidates under the registry’s search semantics; matching is not proof of relevance, treatment suitability or individual eligibility.

  2. 2. Inspect an exact NCT record

    Copy a returned NCT identifier into clinicaltrials_study_record. Review the exact canonical record, title, recorded sponsor, conditions and study type or phase. A validated missing ID is source absence at observation time. Errors and redirected aliases do not become missing records.

  3. 3. Separate status, results availability and dates

    Retain overallStatus separately from hasResults: a completed study can have no posted results. Posted results do not establish efficacy, safety, completeness or a positive finding. Preserve month or day precision and ACTUAL or ESTIMATED milestones. Source processing date, record update date and ToolCargo observation time describe different events.

  4. 4. Search publication candidates independently

    Use Europe PMC to find life-sciences publication records on the topic and inspect their source identifiers and publication types. Keep these candidates in a separate list. A similar title, condition or sponsor does not prove that a paper reports the registered study; verify any claimed relationship in the original records.

  5. 5. Return a dated source-linked research list

    Attribute registry data to ClinicalTrials.gov and disclose the ToolCargo projection. Retain the actual source processing timestamp, API version, observation time, modifications and missing or truncated fields. Each operation reads fresh selected metadata and confirms matching source versions before and after the fetch. A detected source update returns an error and requires restarting. Explicit pages can still change, and separate backend requests are not an atomic snapshot. Review the live record again before later use.

A prompt to try

Use ToolCargo to find registered study records on the public topic I provide and inspect selected exact NCT IDs. Preserve source status, hasResults, source processing date, observation time, source links and actual or estimated date fields with their original precision. Attribute the registry data to ClinicalTrials.gov and disclose ToolCargo’s selected-field projection and modifications. Search Europe PMC separately if useful; verify any claimed study-publication link in original records. Do not interpret treatment efficacy, safety, eligibility or outcome findings. Do not send personal health details or fetch participant data, contacts, protocol narratives, eligibility text, outcome tables or files.

What a useful result looks like

Two separate research lists: registry NCT ID → title → recorded study type/phase → overallStatus → posted-results availability → actual/estimated milestones and date precision → source processing date → source link → observation time → missing/truncated fields; publication source ID → citation metadata → independently reviewed relationship, if any.

Know the limits

ClinicalTrials.gov records are supplied by study sponsors and investigators; listing does not establish government review or approval of safety or scientific validity. Registry status is not treatment advice, individual eligibility or proof of efficacy. This connector reads selected public metadata, without outcome interpretation, participant information, contacts, narratives or files. Counts, rankings and pages can change. Source data retain international and possible third-party copyright; ToolCargo grants no reuse sublicense. One successful hosted operation consumes one shared-plan call, even though a source-version check, selected metadata fetch and confirming version check require three requests. No provider account, key or paid provider is needed.

Common questions

Does COMPLETED mean posted results are available?

No. Study status and posted-results availability are independent source fields. Keep them separate, and do not infer that results are positive, complete, peer reviewed or evidence that a treatment works.

Can an estimated completion date be presented as an accomplished milestone?

No. Retain the source’s date type and month or day precision. Estimated dates describe a source-recorded plan, not an observed completion.

Is a publication automatically linked to a matching study?

No. Search the sources independently and verify any relationship in original records. Similar text or a shared topic is insufficient.

Is the source processing timestamp the same as fetchedAt?

No. The processing timestamp comes from the registry’s version endpoint; fetchedAt is ToolCargo’s observation time. ToolCargo checks the source version before and after fetching metadata and fails if it changes. These checks still do not make separate backend requests an atomic source snapshot.

References and tool documentation

Use the provider’s documentation to check the underlying concepts, and ToolCargo’s references for the exact tools, inputs and limits.

Tool references for this workflow

Continue with the tools

Related workflows