Skip to content

Clinical Trials MCP server

org.memoryapi/clinicalmemoryapi.orgstreamable-httpv1.0.0Scanned

Clinical trial search and status from ClinicalTrials.gov

3 tools: 3 only read.

Tools: 0 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Clinical Trials MCP server can do

The Clinical Trials MCP server is published by memoryapi.org, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Only reads 3Show 3 read-only tools
  • get_trial_detailsGet full details of a specific clinical trial by NCT ID.No findings

    Why it is in this group

    • The name "get_trial_details" says "get": a word for reading.
    Description, as the server wrote it
    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_statsGet clinical trial statistics and trends for a condition.No findings

    Why it is in this group

    • The name "get_trial_stats" says "get": a word for reading.
    Description, as the server wrote it
    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?"
  • search_trialsSearch clinical trials on ClinicalTrials.gov by condition, intervention, sponsor, status, or phase.No findings

    Why it is in this group

    • The name "search_trials" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://clinical.memoryapi.org/.well-known/oauth-protected-resource
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http clinical https://clinical.memoryapi.org/mcp
claude mcp add --transport http clinical https://clinical.memoryapi.org/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__clinical__search_trials",
      "mcp__clinical__get_trial_details",
      "mcp__clinical__get_trial_stats"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as clinical. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/org.memoryapi/clinical/verify?hash=e28cc62a1727ffe74c54063371071b13b815b18a55abef71b0a00d260bcc4119" | jq -e '.changed == false'

Pinned hash e28cc62a1727, from Nov 21, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.memoryapi/clinical/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.memoryapi/clinical
[![Anlyon Radar](https://radar.anlyon.com/badge/org.memoryapi/clinical.svg)](https://radar.anlyon.com/servers/org.memoryapi/clinical)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

Clinical Trials MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Clinical Trials MCP server safe?

No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Clinical Trials MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Clinical Trials MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Clinical Trials MCP server have?

3 tools: 3 read. search_trials, get_trial_details and get_trial_stats.

Does the Clinical Trials MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Clinical Trials MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Clinical Trials MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.