Clinical trials API and MCP server

Three datasets the registry API does not give you

Read what changed in a ClinicalTrials.gov record, field by field, with the value before and after and a link to the source. The same key also returns a source-backed FDA and PDUFA calendar and verified sponsor-to-ticker mappings, as JSON over REST or as tools for an AI assistant. See Pro pricing or how to get a key.

Field-level change history

One record per changed field: primary completion date, enrollment, recruitment status or primary outcome measures. Each has the previous value, the new value, the date the registry posted it and the registry link. The ClinicalTrials.gov API returns only the current version of a study.

FDA calendar events with date precision

PDUFA target dates from company SEC filings, FDA approval decisions, complete response letters and advisory committee notices, as shown on the FDA calendar. Every event carries its source link, the quoted evidence and a precision field, so a date reported as a month or quarter stays a month or quarter.

Sponsor, ticker and CIK mappings

Verified links from a trial’s NCT ID to its sponsor, stock ticker and SEC CIK number, each with the evidence link. Filter trials and changes by ticker.

Example: every recorded change for one company since a date

Send your key in the Authorization header of a GET request.

curl "https://trialredline.com/api/v1/changes?ticker=ABCD&since=2026-09-01" \
  --header "Authorization: Bearer YOUR_API_KEY"

The response is a page of change records. The values below are illustrative, to show the shape:

{
  "data": [
    {
      "id": 1,
      "nct_id": "NCT00000000",
      "field": "primary_completion",
      "before": "2026-03-31",
      "after": "2026-09-30",
      "posted_date": "2026-09-12",
      "kind": "date_slip",
      "review_status": "factual",
      "source_url": "https://clinicaltrials.gov/study/NCT00000000"
    }
  ],
  "page": 1,
  "per_page": 50,
  "has_more": false,
  "attribution": "ClinicalTrials.gov; normalized by TrialRedline. Source dates and coverage are supplied per record."
}

FDA calendar events

GET /api/v1/events returns published events in date order. Read precision before you treat date as a day. Illustrative values:

{
  "data": [
    {
      "id": 1,
      "title": "PDUFA target action date",
      "type": "pdufa",
      "date": "2027-03",
      "precision": "month",
      "indication": "Example condition",
      "source_url": "https://www.sec.gov/Archives/edgar/data/0000000/example.htm",
      "evidence": "The FDA assigned a PDUFA target action date in March 2027.",
      "verified_at": "2026-09-01T00:00:00"
    }
  ],
  "page": 1,
  "per_page": 50,
  "has_more": false,
  "attribution": "FDA, SEC company disclosures and Federal Register; reviewed by TrialRedline. Source evidence and date precision are supplied per record."
}

7 read-only REST endpoints

All paths are relative to https://trialredline.com and return JSON.

GET /api/v1/changes
Recorded field-level changes across covered trials, newest first: the field, the before and after values, the date the registry posted the change and a source link. Optional filters: ticker, since=YYYY-MM-DD.
GET /api/v1/trials/NCT_ID/changes
Recorded changes for one trial.
GET /api/v1/trials/NCT_ID/history
The stored versions of one trial, with a coverage note.
GET /api/v1/trials
Tracked trial records, optionally for one company ticker. Optional filters: ticker.
GET /api/v1/trials/NCT_ID
One trial’s current stored record.
GET /api/v1/events
Published FDA calendar events: PDUFA target dates, approval decisions, complete response letters and advisory committee notices, each with its date precision, a source link and the supporting quote.
GET /api/v1/mappings
Verified links between trials, sponsors, stock tickers and SEC CIK numbers, with the evidence link.

Replace NCT_ID with a ClinicalTrials.gov identifier such as NCT01234567. List endpoints take page and per_page (up to 100 records a page) and return has_more, so you can stop when it is false.

MCP server: the same data as tools for an AI assistant

Point any Model Context Protocol client that can send a request header at https://trialredline.com/mcp. Then ask in plain language, for example which trials from one company moved their primary completion date since September, and the assistant calls the tools and gets the registry links back with each answer.

{
  "mcpServers": {
    "trialredline": {
      "type": "http",
      "url": "https://trialredline.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

In Claude Code you can run this instead:

claude mcp add --transport http trialredline \
  https://trialredline.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Authentication is a Bearer API key only. There is no OAuth sign-in, so the client must let you set the Authorization header, as Claude Code, Cursor and VS Code do.

7 read-only tools

list_trials
List tracked trials. Arguments: ticker.
What the assistant is told

List clinical trials tracked by TrialRedline, ordered by NCT ID, optionally for one sponsor ticker. Each record has title, phase, status, sponsor, verified ticker, conditions, interventions, primary completion date and type, enrollment and type, the ClinicalTrials.gov source_url, source_updated_at, history_complete and coverage_note.

get_trial
Get one trial. Arguments: nct_id (required).
What the assistant is told

Return the current stored record for one trial by NCT ID, with its ClinicalTrials.gov source_url, source_updated_at, history_complete flag and coverage_note.

list_changes
List registry changes. Arguments: ticker, since.
What the assistant is told

List recorded field-level changes to trial registry records across all tracked trials, newest first, optionally for one sponsor ticker and/or posted on or after a date. Each change gives the field, the before and after values, posted_date, kind, review_status and source_url. Changes quarantined as contradictory are excluded.

list_trial_changes
List changes for one trial. Arguments: nct_id (required).
What the assistant is told

List recorded field-level changes for one trial, newest first: field, before and after values, posted_date, kind, review_status and source_url. Changes quarantined as contradictory are excluded.

get_trial_history
Get stored versions of one trial. Arguments: nct_id (required).
What the assistant is told

List the stored registry versions of one trial, newest first. Each version has its number, submitted_date, posted_date, the normalized fields, origin (research import or live snapshot), whether the version is complete, a disputed flag, coverage_note and source_url. Stored history can be incomplete; versions can be large, so prefer a small per_page.

list_sponsor_mappings
List verified trial-sponsor-ticker mappings.
What the assistant is told

List verified links between trials, sponsors, stock tickers and SEC CIK numbers, ordered by NCT ID, with the evidence source_url. Unverified mappings are excluded.

list_regulatory_events
List published FDA regulatory events.
What the assistant is told

List published regulatory calendar events in date order: company-disclosed PDUFA target dates, FDA approvals, complete response letters and advisory committee notices. Each event has title, type, date, precision (the date may be a day, month, quarter or other period; never assume an exact day), indication, source_url, the supporting evidence quote and verified_at. Pending and conflicted candidates are excluded.

Every tool also takes page and per_page where it returns a list.

The server uses the Streamable HTTP transport: send JSON-RPC 2.0 with POST and each request gets one JSON response. It keeps no session. Supported protocol revisions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05.

One Pro key for both, 10,000 requests a month

The API and the MCP server are part of the Pro plan. See what Pro costs and includes. To get a key, create an account, start Pro, then open API access and create a key. The full key is shown once.

  • 10,000 requests each calendar month (UTC), shared by all your keys and by REST and MCP.
  • Every REST request counts as one. Over MCP, each tool call counts as one; connecting and listing tools do not.
  • Everything is read-only. A missing or wrong key returns 401, an account without Pro returns 403, and a used-up month returns 429.
  • Coverage is company-sponsored Phase 2 and Phase 3 drug trials linked to US-listed companies. Each trial’s record says whether its stored history is complete; the methodology page has the detail.

Embed the FDA calendar on your site, free

Writing about an upcoming PDUFA date? Paste this into a blog post or newsletter archive page to show the next published FDA calendar events. It needs no account, key or JavaScript, and each event links to its drug page and its original source.

<iframe src="https://trialredline.com/embed/fda-calendar"
  title="Upcoming FDA calendar events" width="100%" height="520"
  loading="lazy" style="border:0"></iframe>
<p><a href="https://trialredline.com/fda-calendar">
  FDA calendar by TrialRedline</a></p>

Add ?limit=5 to choose how many events to show (1 to 25; 10 if you leave it out) and &type= to show one kind of event:

type=pdufa
Announced review target
type=approval
FDA approval decision
type=crl
Complete response letter
type=advisory_committee
Advisory committee notice

This is the widget with ?limit=5:

To put the dates in your own calendar instead, subscribe to the FDA calendar feed (.ics).

Common questions

Is there an API for changes to clinical trial records?

Yes. GET /api/v1/changes returns one record per changed field with the previous value, the new value, the date ClinicalTrials.gov posted the change and a link to the registry record. The registry’s own API returns only the current version of each study.

Is there an MCP server for ClinicalTrials.gov change history?

Yes. TrialRedline runs a read-only Model Context Protocol server over Streamable HTTP. It offers the same data as the REST API as tools an AI assistant or agent can call.

Does the MCP server support OAuth?

No. Both the REST API and the MCP server authenticate with a Bearer API key and nothing else. Your MCP client has to let you set an Authorization header, as Claude Code, Cursor and VS Code do.

Is there an FDA calendar or PDUFA date API?

Yes. GET /api/v1/events and the list_regulatory_events tool return the published FDA calendar: PDUFA target dates disclosed by companies, FDA approval decisions, complete response letters and advisory committee notices. Each event states whether its date is an exact day, a month, a quarter or another period.

Is the API free?

The API and MCP server are part of the Pro plan. Browsing the site, the FDA calendar, its .ics feed and the embeddable calendar are free and need no account.

Which trials does the API cover?

Company-sponsored Phase 2 and Phase 3 drug trials linked to US-listed companies. Four fields are compared between versions: primary completion date, enrollment, recruitment status and primary outcome measures.

Related

ClinicalTrials.gov API guide

FDA calendar

Where the data comes from