EMA MCP Server
Related Servers
Alternatives to EMA MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides access to the European Medicines Agency's public medicines register and related datasets, enabling search and monitoring of approved medicines, herbal substances, shortages, safety communications, referrals, and post-authorisation procedures.36 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables searching EMA Article 57 product data across all EEA countries, including marketing-authorisation holders and pharmacovigilance locations, with filtered search, product lookup, dataset info, and change detection between snapshots.19 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving data from the Spanish official register of authorised medicines, including medicine details, structured SmPC and patient leaflet text, supply shortages, and regulatory changes over time.17 npmMIT

@pipeworx/eu-ctisofficial
AlicenseNot gradedqualityBmaintenanceEnables searching and retrieving EU/EEA clinical trial records from the Clinical Trials Information System, including trial status, sponsors, medicines, conditions, and authorisations.38 npmMIT- AlicenseNot gradedqualityBmaintenancePharmaceutical R\&D Pipeline Intelligence for AI Agents — Clinical trials, FDA approvals, drug information & publications in one MCP server.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying the UK MHRA medicines register to search by product, brand, or active substance, retrieve all documents for a licence, and monitor recent changes to published medicines documents.49 npmMIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'ema_info' has a clearly defined and distinct purpose for EMA drug information lookup.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'ema_info' follows a clear and appropriate pattern for its function.
A single tool is too few for the broad scope implied by the description, which covers multiple aspects like drug approvals, EPARs, orphan designations, supply shortages, and regulatory information. This thin surface likely requires agents to handle complex queries within one tool, which is suboptimal for typical MCP server design.
The tool set is severely incomplete for the EMA domain. While 'ema_info' provides a unified lookup, there are obvious gaps such as separate tools for different resource types (e.g., approvals vs. shortages) or operations (e.g., search vs. get details), which could lead to agent confusion or inefficiency in handling specific queries.