ClinicalTrials.govBLOCK
Search ClinicalTrials.gov trials, retrieve study details and results, and match patients to eligible trials via MCP. STDIO or Streamable HTTP.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
clinicaltrialsgov-mcp-server Search ClinicalTrials.gov trials, retrieve study details and results, and match patients to eligible trials via MCP. STDIO or Streamable HTTP. 7 Tools • 1 Resource • 1 Prompt
[](./CHANGELOG.md) [](./LICENSE) [](https://github.com/users/cyanheads/packages/container/package/clinicaltrialsgov-mcp-server) [](https://modelcontextprotocol.io/) [](https://www.npmjs.com/package/clinicaltrialsgov-mcp-server) [](https://www.typescriptlang.org/) [](https://bun.sh/)
[](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/releases/latest/download/clinicaltrialsgov-mcp-server.mcpb) [](https://cursor.com/en/install-mcp?name=clinicaltrialsgov-mcp-server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImNsaW5pY2FsdHJpYWxzZ292LW1jcC1zZXJ2ZXIiXX0=) [](https://vscode.dev/redirect?url=vscode:mcp/install?%7B%22name%22%3A%22clinicaltrialsgov-mcp-server%22%2C%2
400832bec776OBSERVED · 2026-10-07Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add clinicaltrialsgov-mcp-server -- npx -y [email protected]
claude mcp add clinicaltrialsgov-mcp-server -- npx -y [email protected]
Exposed tools (2)
2 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
Aspirin | read | Low dose aspirin |
conditionMesh | read | Field-level MeSH term for the condition. |
Trust audit
BLOCKgrade F · trust 46/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (5 observation(s))
- Network
- declared (2 observation(s))
- Shell
- declared (8 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (20)
**Seed orientation context when the next moves are predictable.** Piggybacking a compact snapshot alongside the primary result — recent activity, tracked state, a few reference items — does two things
const tsc = await exec([join(ROOT_DIR, 'node_modules', '.bin', 'tsc'), '-p', project], 'tsc');
const alias = await exec(
exec(cmd: string[], options: { cwd: string }): Promise<ShellResult> {':(glob)**/.netrc',
| **Server credential** | The server's own upstream key is missing, or the upstream rejects it (401/403) | `ConfigurationError` — translated in the service, since the automatic status mapping yields `
Prereq: a GitHub PAT with `read:org` + `read:user` scopes stored in Keychain under the service name `mcp-publisher-github-pat`:
2. **No `git stash`, no `git reset --hard`, no `git restore .`, no `git clean -f`, no `git checkout -- .`.** These bypass safety and risk silent data loss. Read-only git (`status`, `diff`, `log`, `sho
.mcpbignore
import { nctIdSchema } from '../../tools/utils/_schemas.js';import { RECOVERY_HINTS } from '../../tools/utils/recovery-hints.js';import { applyFilters, summarizeResults } from '../../tools/utils/study-filters.js';import { loadStudyFixture } from '../../../helpers/format-parity.js';import { missingLeaves } from '../../../helpers/format-parity.js';'anormaltext',
@cyanheads/mcp-ts-core, pino-pretty, zod, @biomejs/biome, @socketsecurity/bun-security-scanner, @types/bun, @vitest/coverage-istanbul, depcheck
- [ ] `.codex-plugin/mcp.json` updated — server name key is the unscoped repo name; every user-supplied variable (API key, contact email, instance URL) is listed in `env_vars` so Codex forwards it fro
- [ ] `.codex-plugin/mcp.json` updated — server name key is the unscoped repo name; every user-supplied variable (API key, contact email, instance URL) is listed in `env_vars` so Codex forwards it fro
Maintenance release. Framework catch-up across two minor versions, with the headline change being a new server-level `instructions` block sent on every `initialize` so spec-compliant clients can forwa
- **`clinicaltrials_get_field_values`** — colloquial labels `RecruitmentStatus` and `RecruitingStatus` now auto-correct to the canonical `OverallStatus` (mirroring the existing case/whitespace normali
Gates applied: critical_finding, instruction_override, no_behavioural_pass, undeclared_transfer.
400832bec776full audit observations/trust-audit/mcp-server/cyanheads__clinicaltrials-gov.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 400832bec776 | BLOCK | F | 46 | first audit |
Questions
What is the ClinicalTrials.gov MCP server?
Search ClinicalTrials.gov trials, retrieve study details and results, and match patients to eligible trials via MCP. STDIO or Streamable HTTP.
What tools does ClinicalTrials.gov expose?
2 in total: 2 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is ClinicalTrials.gov safe to connect to an agent?
No — not without reading the findings first. The audit graded it F (46/100) and found 8 critical or high issues in the source. Each one is listed on this page with the file and line it is on.
What credentials does ClinicalTrials.gov need?
No credential environment variables were found in its source, so it appears to need none.
How does ClinicalTrials.gov run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as clinicaltrialsgov-mcp-server at 2.9.11.
How current is this page?
The grade is for one exact copy of the source (400832bec776), read on 2026-10-07. The repository is watched and re-audited when it changes.