biomed-clinical-radar-mcp
Related Servers
Alternatives to biomed-clinical-radar-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables AI agents to query free biomedical and pharmaceutical APIs for clinical trials, drug data, molecular structures, adverse events, and research literature.14-
- AlicenseNot gradedqualityDmaintenanceProvides real-time access to medical data including drug interactions, ICD-10 codes, FDA adverse event reports, and clinical guidelines. It enables LLMs to query databases like openFDA, PubMed, and CMS for pharmaceutical and clinical information.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to query and analyze FDA adverse events, drug labels, medical device clearances, and other public health datasets through natural language commands.14-
- AlicenseBqualityDmaintenanceEnables AI assistants to search and retrieve biomedical research articles from PubMed's database of over 35 million citations, including metadata, abstracts, MeSH terms, and full-text PDFs when available.11MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to access FDA and ClinicalTrials.gov data for medical device compliance, adverse event monitoring, and regulatory due diligence.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to retrieve and search authoritative healthcare data, including FDA drug information, PubMed literature, health topics, clinical trials, ICD-10 terminology, medRxiv preprints, NCBI Bookshelf content, BMI calculations, and DICOM metadata.MIT
TDQS
Scored across 1 tool
There is only one tool, so an agent cannot misselect between alternatives. Its purpose (searching PubMed, ClinicalTrials.gov, and OpenFDA by keyword) is stated clearly and unambiguously.
The single name is descriptive snake_case with a leading verb (search_), which is a clean and readable convention. With only one tool there is no cross-tool consistency to evaluate, and the name is somewhat long/vague in its 'intelligence' suffix.
The server bundles three distinct data domains (literature, trials, drug labels) into a single tool. A count of 1 is thin for that scope and forces all queries through one monolithic entry point.
The surface is search-only: no way to fetch a specific paper, trial record, or drug label by ID, and no explicit pagination/date-filtering operations. Core keyword retrieval is covered, but agents will hit dead ends when they need details on a specific result.