mcpbeat

Clinical Trials MCP Server

org.memoryapi/clinical
answering

Clinical Trials is answering right now. Last checked 15 min ago. It exposes 3 tools.

Clinical trial search and status from ClinicalTrials.gov

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
431 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add clinical --transport http https://clinical.memoryapi.org/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "clinical": {
      "url": "https://clinical.memoryapi.org/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.clinical]
url = "https://clinical.memoryapi.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "clinical": {
      "url": "https://clinical.memoryapi.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "clinical": {
      "url": "https://clinical.memoryapi.org/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

trial
get_trial_details
Get full details of a specific clinical trial by NCT ID. Returns title, summary, description, eligibility criteria, primary/secondary outcomes, sponsor, collaborators, locations, and results summary if available.
get_trial_stats
Get clinical trial statistics and trends for a condition. Returns counts by status (recruiting, completed, etc.), by phase, and top sponsors. Useful for: "How many Alzheimer's trials are recruiting right now?"
trials
search_trials
Search clinical trials on ClinicalTrials.gov by condition, intervention, sponsor, status, or phase. Returns trial IDs, titles, status, phases, conditions, interventions, enrollment, and locations count.

Endpoints

URLTransportStateLatencyChecked
https://clinical.memoryapi.org/mcp streamable-http answering 407 ms 15 min ago

Clinical Trials — questions

Answers built from our own checks of this server.

What can Clinical Trials do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_trial_details, get_trial_stats, search_trials. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Clinical Trials working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 431 ms. The bar chart above shows every period we have measured.
How do I connect Clinical Trials?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Clinical Trials need an API key?
No. Clinical Trials completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Clinical Trials?
It answers our handshake in 431 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.