ClinicalTracker MCP

This server connects to ClinicalTrials.gov and openFDA to observe changes in medical research records. It enables AI assistants to detect shifts in trial statuses, identify new recruiting locations, and note modifications to FDA labels. Notifications can be sent via email or directly to the assistant.

The server is suitable for tracking FDA approval or recall events, watching for status changes in specific studies, searching ClinicalTrials.gov through an AI interface, and locating new recruitment sites for particular health conditions. It offers functions to compare trials, retrieve intelligence briefs, and query EU trials or FDA updates.

Access requires creating a REST API key and signing in to clinicaltracker.org initially. Users must also sign in when requested. Although connecting and listing tools does not require authentication, individual tools may require a vendor account, credentials, or specific permissions.

• Monitor clinical trial status changes
• Track new recruiting sites for specific conditions
• Alert on FDA approval or recall updates
• Search ClinicalTrials.gov via AI assistant

No tool definitions available.

• Oct 31, 2026, 7:43 PM UTC · registry · passed · metadata changed · Source metadata updated
• Oct 31, 2026, 7:42 PM UTC · registry · passed · metadata changed · Source metadata updated
• Oct 31, 2026, 7:42 PM UTC · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

claude mcp add --transport http clinicaltracker-mcp https://clinicaltracker.org/mcp/public

codex mcp add clinicaltracker-mcp --url https://clinicaltracker.org/mcp/public

{
  "mcpServers": {
    "clinicaltracker-mcp": {
      "url": "https://clinicaltracker.org/mcp/public"
    }
  }
}

{
  "mcpServers": {
    "clinicaltracker-mcp": {
      "type": "streamableHttp",
      "url": "https://clinicaltracker.org/mcp/public",
      "disabled": false
    }
  }
}

{
  "servers": {
    "clinicaltracker-mcp": {
      "type": "http",
      "url": "https://clinicaltracker.org/mcp/public"
    }
  }
}

gemini mcp add --transport http clinicaltracker-mcp https://clinicaltracker.org/mcp/public

{
  "mcpServers": {
    "clinicaltracker-mcp": {
      "url": "https://clinicaltracker.org/mcp/public"
    }
  }
}

{
  "mcpServers": {
    "clinicaltracker-mcp": {
      "serverUrl": "https://clinicaltracker.org/mcp/public"
    }
  }
}

• The Aggregate MCPBy The Aggregate · No sign-in
• Zestio MCPBy Zestio · API key
• ContextDB MCPBy ContextDB · OAuth sign-in
• APICK Vision MCPBy APICK · No sign-in
• Seonix MCPBy Seonix · No sign-in
• DarkSearch.xyz MCPBy DarkSearch.xyz · No sign-in

Is authentication required for all operations?

Connecting and listing tools does not require sign-in. However, individual tools may still need a vendor account, credentials, or permissions. Check the documented prerequisites for specific tool usage.

What specific monitoring tasks are supported?

The server supports alerting on FDA approval or recall updates, monitoring clinical trial status changes, searching ClinicalTrials.gov via an AI assistant, and tracking new recruiting sites for specific conditions.

What are the initial setup steps?

You must create a REST API key and sign in to clinicaltracker.org the first time. You must also sign in when prompted by the server during operation.