aria-mcp-server
Related Servers
Alternatives to aria-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for clinical and pharmaceutical data, enabling search of ClinicalTrials.gov, PubMed, FDA, and ICH guidelines without API keys.25 npmMIT
- FlicenseNot gradedqualityDmaintenanceA 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.-
- FlicenseBqualityDmaintenanceProvides access to the ClinicalTrials.gov API, enabling search, analysis, and retrieval of clinical trial data through MCP tools.178-
- FlicenseNot gradedqualityAmaintenanceMCP server for querying PROSPERO registered protocols, enabling search, retrieval, and registration workflow management.-
- AlicenseAqualityDmaintenanceA lightweight MCP server for clinical biomedical literature retrieval, enabling PubMed search, article metadata, full-text access, and evidence summarization through MCP-compatible clients.10MIT
- AlicenseAqualityFmaintenanceEnables 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.53MIT
TDQS
Scored across 3 tools
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.
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.
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.
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.