F
licenseNot graded
qualityD
maintenanceAn MCP server that analyzes patient symptoms using AI, suggests potential diagnoses, and retrieves relevant medical literature from PubMed.
-
DrugWise
Related Servers
Alternatives to DrugWise
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables AI assistants to query U.S. FDA public datasets, including drug adverse events, labeling, recalls, approvals, shortages, NDC directory, and medical device regulatory information.10MIT
- AlicenseBqualityCmaintenanceAn MCP server that connects AI assistants to OpenEMR instances to manage patient records, clinical trends, and medication safety. It provides 17 tools for tasks such as patient search, drug interaction checks, and generating comprehensive health trajectories and visit preparations.17MIT
- AlicenseBqualityCmaintenanceAn MCP server that provides standardized access to biomedical knowledge bases and resources, enabling AI systems to retrieve verified information from sources like bioRxiv, EuropePMC, and various protein/gene databases.5230Apache 2.0
- FlicenseNot gradedqualityCmaintenanceAn educational healthcare assistant MCP server that provides medication information, interaction checks, symptom guidance, and health topic searches using local data and a local LLM.-
- FlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that bridges AI applications with FHIR healthcare data systems, enabling patient data access, clinical data retrieval, and data quality assessment.4-
TDQS
B3.3/5.0
Scored across 5 tools
Disambiguation4/5
Tools have distinct purposes, but there is some overlap: orchestrator_check_drug_interactions already queries ClinicalTrials.gov, overlapping with clinical_trials_search_clinical_trials. Also, polypharmacy_risk_check_polypharmacy_risk duplicates the interaction checking logic for multiple medications. Descriptions help differentiate, but boundaries are not perfectly clear.
Naming Consistency3/5
Naming uses long descriptive underscores, but prefixes are inconsistent: 'orchestrator_', 'drug_info_', 'drug_alternatives_', 'clinical_trials_', 'polypharmacy_risk_'. Also, 'clinical_trials_search_clinical_trials' is redundant. Overall, pattern is present but mixed.
Tool Count4/5
With 5 tools, the server is well-scoped for its purpose. Each tool covers an essential step in the drug interaction workflow. Could potentially be consolidated (e.g., search trials into check interactions), but current count is reasonable.
Completeness4/5
Covers core workflow: get info, check interactions, find alternatives, search trials, polypharmacy check. Missing drug-food interactions and allergy checks, but these are tangential. Minor gaps, but agents can still complete main tasks.
Maintenance
ActivityStale
ResponsivenessNo issues