mcp-pharma
Related Servers
Alternatives to mcp-pharma
- AlicenseAqualityBmaintenanceMCP server for verifying Russian counterparties (legal entities and individual entrepreneurs) via public Federal Tax Service data: EGRUL/EGRIP, bankruptcy registry (EFRSB), Transparent Business, bailiff service (FSSP), and arbitration courts (KAD).815MIT
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with comprehensive access to Israel's complete pharmaceutical database from the Ministry of Health, enabling drug information search, therapeutic comparisons, and safety assessments.18-
- AlicenseBqualityDmaintenanceProvides access to the official FDA DailyMed database for comprehensive drug information, including drug labels, NDC codes, RxNorm mappings, pharmacologic classifications, and FDA application numbers through natural language queries.283MIT
- 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
- AlicenseNot gradedqualityBmaintenancePharmaceutical R\&D Pipeline Intelligence for AI Agents — Clinical trials, FDA approvals, drug information & publications in one MCP server.5MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query the official Spanish AEMPS/CIMA registry for real-time pharmaceutical data, including medications, supply problems, and clinical equivalences.1Apache 2.0
TDQS
Scored across 6 tools
Most tools target distinct resources: search, drug details, registration status, pricing, recalls, and instructions. However, check_drug_registration and get_drug_card both surface status and holder information and accept similar query parameters, so their boundaries could be clearer.
All tool names follow a consistent verb_noun pattern using check_, get_, or search_. There is no mixing of naming conventions or vague action-only verbs.
Six tools is well-scoped for a read-only pharmaceutical registry server. Each tool covers a meaningful query type without unnecessary redundancy or bloat.
Core registry lookups are covered: search, drug card, registration status, pricing, and recalls. However, get_instruction is a non-functional stub that always returns ready=false, so instruction retrieval is a notable gap in the surface.