What can you do with this server?

The ARIA Clinical Research MCP Server provides real-time access to biomedical literature and clinical trial data from public APIs — no API keys required. Core Tools: * Search PubMed (search_pubmed): Query 35M+ peer-reviewed papers via NCBI E-utilities for research on drug mechanisms, clinical outcomes, disease studies, safety/efficacy data, biomarkers, and diagnostics * Search Clinical Trials (search_clinical_trials): Query 400K+ studies on ClinicalTrials.gov by condition, intervention, and status (recruiting, completed, or all) Guided Workflows (Prompts): * Generate a comprehensive evidence + trial brief for a medical condition * Produce a structured adverse event and safety profile for a drug * Assess patient eligibility across currently recruiting trials Reference Resources: * Overview of ARIA's capabilities and data sources * Phase I–IV trial definitions and FDA special designations * Curated high-impact journals organized by medical specialty * FDA databases for drug, safety, and regulatory research Example Use Cases: * Search literature on specific drugs, conditions, or treatment outcomes * Find actively recruiting clinical trials for a given disease * Cross-reference published evidence with active trials for drug discovery * Assess patient eligibility for clinical trials

Which integrations are available for this server?

Enables searching of 35M+ peer-reviewed papers via NCBI E-utilities, allowing comprehensive biomedical literature research through the PubMed database.

de en es ja ko ru zh

aria-mcp-server

by pkotecha-eng

Overview Schema Source Related Servers Score Discussions Admin

Python

Remote

🧬 ARIA Clinical Research MCP Server

A standalone MCP server that gives any Claude agent real-time access to biomedical literature and clinical trials — no API keys required. aria-mcp-server MCP server

Tools

Tool	Description
`search_pubmed`	Search 35M+ peer-reviewed papers via NCBI E-utilities
`search_clinical_trials`	Search 400K+ trials via ClinicalTrials.gov v2 API
`search_isrctn`	Search UK/European trials via ISRCTN registry

Related MCP server: clinicaltrials-mcp

Prompts

Prompt	Description
`clinical-research-brief`	Comprehensive evidence + trial brief for a condition
`adverse-event-analysis`	Structured AE and safety profile for a drug
`trial-eligibility-checker`	Patient eligibility assessment across recruiting trials

Resources

Resource	Description
`info://aria`	Overview of ARIA capabilities and data sources
`reference://trial-phases`	Phase I–IV definitions and FDA special designations
`reference://high-impact-journals`	Curated high-impact journals by specialty
`reference://fda-databases`	FDA databases for drug, safety, and regulatory research

Example queries

Once connected, ask Claude:

"Search PubMed for ketogenic diet pediatric epilepsy outcomes"
"Find recruiting trials for lung cancer immunotherapy"
"What does the literature say about veliparib in ovarian cancer, and are there active trials?"
"Find UK and European trials for pediatric epilepsy via ISRCTN"

Quickstart

pip install aria-mcp-server
aria-mcp-server

Connect to Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "aria-clinical-research": {
      "command": "aria-mcp-server"
    }
  }
}

Restart Claude Desktop. The server will appear under Settings → Developer → Local MCP Servers.

Data sources

PubMed — NCBI E-utilities (public API, no key required)
ClinicalTrials.gov — v2 REST API (public API, no key required)
ISRCTN — UK/European clinical trials registry (public API, no key required)

Tech stack

FastMCP — MCP server framework
Python 3.12+

Use cases

Life sciences researchers needing real-time literature access
Clinical trial coordinators checking eligibility and recruiting status
Drug discovery teams cross-referencing published evidence with active trials
Any Claude agent needing grounded biomedical knowledge

Project Structure

aria-mcp-server/          ← root, where mcp-publisher runs
├── aria_mcp_server/      ← Python package
│   ├── __init__.py
│   ├── server.py
│   └── tools.py
├── server.json           ← MCP registry metadata
├── pyproject.toml
├── README.md
├── LICENSE
└── glama.json

Built by

Pooja Kotecha · dinq.me/pkotecha-eng

Available Tools

3 tools

search_clinical_trialsA

Search ClinicalTrials.gov for clinical studies. Read-only operation. No authentication required. Uses ClinicalTrials.gov v2 public API (no rate limit documented). Returns up to 10 results per call. No pagination. Returns 'No clinical trials found.' if no results match. Use for: active trials, recruiting studies, inclusion/exclusion criteria, phase information, sponsor details, and trial locations.

ParametersJSON Schema

Name	Required	Description	Default
`status`	No	Trial status: RECRUITING, COMPLETED, or ALL	RECRUITING
`condition`	Yes	Disease or condition e.g. 'pediatric epilepsy', 'lung cancer'
`max_results`	No	Number of trials to return, between 1 and 10
`intervention`	No	Optional drug or intervention name to narrow results

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes	Formatted list of trials with NCT ID, title, phase, status, sponsor, conditions, interventions, and eligibility criteria (inclusion and exclusion, listed separately). Returns 'no results' message if nothing found.

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Discloses read-only, no auth required, public API with no documented rate limit, batch size (up to 10), no pagination, fallback message. Sufficient for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences plus a crisp list of use cases. Front-loaded with core purpose. Slightly redundant use-case list could be integrated, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values are covered. Description covers purpose, usage, behavioral details, and limitations. No gaps given the tool's simplicity and existing structured fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions for all 4 parameters. Description adds no additional semantic value beyond what the schema already provides. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it searches ClinicalTrials.gov for clinical studies. Lists specific use cases (active trials, recruiting studies, etc.). Distinguishes from sibling tools (search_isrctn, search_pubmed) by focusing on this specific database.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly lists what to use it for and mentions constraints (max 10 results, no pagination, no auth). Lacks explicit 'when not to use' but context is clear given siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_isrctnA

Search the ISRCTN registry for UK and European clinical trials. Read-only operation. No authentication required. Complements ClinicalTrials.gov by covering trials at UK academic institutions and European research centers not listed on ClinicalTrials.gov. Returns up to 10 results per call, filtered for relevance. Returns 'No ISRCTN trials found.' if no results match. Use for: UK/European trials, academic institution studies, international coverage beyond ClinicalTrials.gov.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Condition or search terms e.g. 'pediatric epilepsy', 'type 2 diabetes'
`max_results`	No	Number of trials to return, between 1 and 10

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes	Formatted list of trials with ISRCTN ID, title, phase, status, sponsor, condition, outcomes, countries, and inclusion/exclusion criteria.

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses read-only operation, no authentication required, result limits (up to 10), relevance filtering, and empty response message. With no annotations provided, description carries full burden and does well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

4 sentences covering purpose, behavior, complementary role, and usage hints. Front-loaded and no unnecessary words, though could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, behavior, and limitations. With an output schema present, return values are presumably documented elsewhere. Sufficient for a moderate-complexity search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% description coverage, so baseline is 3. Description adds minimal extra meaning (e.g., 'filtered for relevance'), but mostly restates schema info like max results limit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool searches the ISRCTN registry for UK and European clinical trials, distinguishing itself from sibling tools like search_clinical_trials by explicitly noting it complements ClinicalTrials.gov coverage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit use cases: UK/European trials, academic studies, international coverage beyond ClinicalTrials.gov. Implicitly suggests alternatives by noting it complements other registries, though does not explicitly state when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_pubmedA

Search PubMed for peer-reviewed biomedical literature. Read-only operation. No authentication required. Uses NCBI E-utilities public API (rate limit: ~3 requests/sec). Returns up to 10 results per call. No pagination. Returns 'No papers found.' if no results match. Use for: research papers, drug mechanisms, clinical outcomes, disease studies, safety/efficacy data, biomarkers, diagnostics, and any scientific question.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Search query e.g. 'velarixin pediatric epilepsy phase 2'
`max_results`	No	Number of papers to return, between 1 and 10

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes	Formatted list of papers with title, authors, journal, year, PMID, and abstract. Returns 'no results' message if nothing found.

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description fully discloses behavioral traits: read-only operation, no authentication, NCBI E-utilities API with rate limit, max 10 results, no pagination, and empty result message. This is thorough and adds significant value beyond structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise paragraph, front-loaded with the purpose, followed by behavioral traits and usage context. Every sentence adds value with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all necessary aspects: purpose, behavioral traits, rate limits, result limits, empty result handling, and usage contexts. With an output schema present, return values are not needed. It is complete for a simple tool with two parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does not add additional meaning beyond what is already in the schema for the two parameters (query and max_results). It restates the max_results limit but provides no new semantic detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches PubMed for peer-reviewed biomedical literature, with a specific verb and resource. It distinguishes from sibling tools (clinical trials, ISRCTN) by listing use cases like research papers and drug mechanisms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a 'Use for' list that implies contexts (research papers, drug mechanisms, clinical outcomes, etc.), but does not explicitly state when not to use or name alternative tools. The sibling context provides implicit guidance, so it is clear but lacks exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updatev0.2.1Jul 13, 2026

Changedsearch_clinical_trials1 field changed

changedOutput schema / properties / result / description

Previous value: -"Formatted list of trials with NCT ID, title, phase, status, sponsor, conditions, interventions, and eligibility criteria. Returns 'no results' message if nothing found."New value: +"Formatted list of trials with NCT ID, title, phase, status, sponsor, conditions, interventions, and eligibility criteria (inclusion and exclusion, listed separately). Returns 'no results' message if nothing found."

3 tool updatesv0.2.0Jul 12, 2026
- Changedsearch_clinical_trials4 fields changed
  - addedInput schema / properties / condition / minLength
```
Added value: +1
```
  - addedInput schema / properties / max_results / maximum
```
Added value: +10
```
  - addedInput schema / properties / max_results / minimum
```
Added value: +1
```
  - addedInput schema / properties / status / enum
```
Added value: +[
+  "RECRUITING",
+  "COMPLETED",
+  "ALL"
+]
```
- Changedsearch_isrctn4 fields changed
  - addedInput schema / properties / max_results / maximum
```
Added value: +10
```
  - addedInput schema / properties / max_results / minimum
```
Added value: +1
```
  - addedInput schema / properties / query / minLength
```
Added value: +1
```
  - changedOutput schema / properties / result / description
```
Previous value: -"Formatted list of trials with ISRCTN ID, title, phase, status, sponsor, condition, outcomes, countries, and eligibility criteria."New value: +"Formatted list of trials with ISRCTN ID, title, phase, status, sponsor, condition, outcomes, countries, and inclusion/exclusion criteria."
```
- Changedsearch_pubmed3 fields changed
  - addedInput schema / properties / max_results / maximum
```
Added value: +10
```
  - addedInput schema / properties / max_results / minimum
```
Added value: +1
```
  - addedInput schema / properties / query / minLength
```
Added value: +1
```
1 tool updatev0.1.8May 3, 2026
- Addedsearch_isrctn

2 tool updatesv0.1.2Apr 28, 2026

Changedsearch_clinical_trials5 fields changed

changedInput schema / properties / condition / description

Previous value: -"Disease or condition (e.g. \"pediatric epilepsy\", \"lung cancer\")"New value: +"Disease or condition e.g. 'pediatric epilepsy', 'lung cancer'"

changedInput schema / properties / max_results / description

Previous value: -"Number of trials to return (1-10, default 5)"New value: +"Number of trials to return, between 1 and 10"

changedInput schema / properties / status / description

Previous value: -"Trial status — RECRUITING, COMPLETED, or ALL (default: RECRUITING)"New value: +"Trial status: RECRUITING, COMPLETED, or ALL"

addedOutput schema / properties / result / description

Added value: +"Formatted list of trials with NCT ID, title, phase, status, sponsor, conditions, interventions, and eligibility criteria. Returns 'no results' message if nothing found."

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

Changedsearch_pubmed4 fields changed

changedInput schema / properties / max_results / description

Previous value: -"Number of papers to return (1-10, default 5)"New value: +"Number of papers to return, between 1 and 10"

changedInput schema / properties / query / description

Previous value: -"Search query (e.g. \"velarixin pediatric epilepsy phase 2\")"New value: +"Search query e.g. 'velarixin pediatric epilepsy phase 2'"

addedOutput schema / properties / result / description

Added value: +"Formatted list of papers with title, authors, journal, year, PMID, and abstract. Returns 'no results' message if nothing found."

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

2 tool updatesApr 14, 2026
- First observedsearch_clinical_trials
- First observedsearch_pubmed

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.4/5.0

Scored 2026-09-09 19:43 across 3 tools

Disambiguation5/5

Each tool targets a distinct data source: PubMed (literature), ClinicalTrials.gov (global trials), and ISRCTN (UK/European trials). The descriptions include specific use cases and overlap is minimal, so an agent can easily select the appropriate tool.

Naming Consistency5/5

All tools follow a clear 'search_<source>' pattern, making the naming perfectly consistent and predictable. The verb 'search' is used uniformly with the database name as the object.

Tool Count5/5

Three tools are appropriate for a search-focused server covering the key biomedical research databases. Each tool provides a distinct and essential capability without unnecessary bloat.

Completeness4/5

The server covers the main sources for biomedical literature and clinical trials, but lacks other registries (e.g., EU-CTR, WHO ICTRP). Minor gaps exist, but the core search workflows are well covered and agents can work around them.

Maintenance

ActivitySlowing

ResponsivenessResponsive

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

Clinicaltrials A
io.github.pipeworx-io
ClinicalTrials MCP — wraps ClinicalTrials.gov API v2 (free, no auth)
Research & Data Government Data Biology & Medicine
452
Biolab MCP Server
io.github.srikarjy
Auditable MCP server for PubMed, Europe PMC, ClinicalTrials.gov, and bioRxiv/medRxiv queries
Biology & Medicine Search Open Data
1
Pubmed A
io.github.pipeworx-io
PubMed MCP — wraps the NCBI E-utilities API (biomedical literature, free, no auth)
Research & Data Biology & Medicine Search
4321
PubMed Clinical ResearchOAuth
io.github.Taru0208
Search 36M+ PubMed biomedical articles and ClinicalTrials.gov studies.
Research & Data Biology & Medicine Search
2

Related MCP Servers

Unofficial Clinical Trials MCP
Biology & Medicine Research & Data Open Data
Augmented-Nature
F
license
B
quality
D
maintenance
Provides access to the ClinicalTrials.gov API, enabling search, analysis, and retrieval of clinical trial data through MCP tools.
Updated 9 months ago (2025-12-21 10:02 UTC)
17
8
-
clinicaltrials-mcp
Biology & Medicine Search
agents100x
A
license
A
quality
F
maintenance
Enables conversational access to 400,000+ clinical trials on ClinicalTrials.gov, allowing users to search, compare, and retrieve trial details using plain English through MCP-compatible clients like Cursor and Claude Desktop.
Updated 4 months ago (2026-05-05 14:55 UTC)
5
3
MIT
ClinicalTrials.gov MCP Server
Biology & Medicine Research & Data
baris-varis
F
license
Not graded
quality
C
maintenance
A production-quality MCP server that wraps the ClinicalTrials.gov v2 API, providing structured, TTL-cached access to trial data worldwide and Turkey via 4 MCP tools.
Updated 3 months ago (2026-06-24 21:14 UTC)
-
pubmed-clinical-mcp
Biology & Medicine Search Research & Data
jxia622
A
license
A
quality
C
maintenance
A lightweight MCP server for clinical biomedical literature retrieval, enabling PubMed search, article metadata, full-text access, and evidence summarization through MCP-compatible clients.
Updated 2 months ago (2026-07-08 19:20 UTC)
10
MIT