A
licenseA
qualityD
maintenanceEnables querying FDA drug label information including adverse reactions, warnings, and indications via natural language.
5
10 npm
1
GPL 3.0
DailyMed MCP Server
by RowanErasmus
Related Servers
Alternatives to DailyMed MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables querying FDA drug label information including adverse reactions, warnings, and indications through natural language.511 npmGPL 3.0
- AlicenseNot gradedqualityFmaintenanceProvides comprehensive pharmaceutical intelligence by integrating real-time openFDA data with locally-cached Orange Book and Purple Book databases. It enables users to analyze drug safety, patents, generic equivalents, biosimilars, and regulatory information through natural language queries.3MIT
- AlicenseAqualityDmaintenanceEnables LLMs to search FDA drug labels and adverse event data via the OpenFDA API, supporting natural language queries for drug safety information.2MIT
- AlicenseNot gradedqualityCmaintenanceSearch and retrieve FDA Structured Product Labels from DailyMed via NLM, supporting queries by drug name, NDC, RXCUI, and more.5 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables drug safety, interactions, adverse events, and regulatory data queries using free sources like DrugBank, WHO, FDA FAERS, and more. Provides tools for checking drugs, interactions, adverse events, and searching across pharmaceutical databases.MIT
TDQS
B3.3/5.0
Scored across 28 tools
Disambiguation4/5
Most tools have distinct purposes targeting specific resources like drugs, classes, or codes, with clear boundaries. However, some overlap exists between 'get_all_' and 'search_' tools (e.g., get_all_drug_names vs. search_drug_names), which could cause minor confusion in selection, though descriptions help clarify the pagination differences.
Naming Consistency5/5
Tool names follow a highly consistent verb_noun pattern throughout, using 'get_' for retrieval and 'search_' for queries, with snake_case uniformly applied. This predictability makes it easy for agents to understand and navigate the toolset without ambiguity.
Tool Count3/5
With 28 tools, the count is borderline high for a medical database server, potentially feeling heavy and overwhelming. While the domain is complex, the number might exceed typical well-scoped ranges (3-15 tools), suggesting some consolidation could improve usability without losing functionality.
Completeness5/5
The toolset provides comprehensive coverage for the DailyMed domain, including CRUD-like operations for drugs, classes, and codes (e.g., get details, search, mappings), with no obvious gaps. It supports core workflows like retrieval, search, and mapping across all key resources, ensuring agents can handle most tasks without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues