leki-mcp
Related Servers
Alternatives to leki-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables querying the Polish National Health Fund (NFZ) public API for medical waiting lists and service dictionary, allowing AI to compare wait times and find providers.33MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query the official Spanish AEMPS/CIMA registry for real-time pharmaceutical data, including medications, supply problems, and clinical equivalences.75 PyPI1Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI assistants to search Türkiye's TİTCK-licensed human drug lists, find generic equivalents, and check licence and e-prescription status, including weekly changes.61MIT
- AlicenseNot 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.19Creative Commons Attribution Non Commercial Share Alike 4.0 International
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query the Australian Pharmaceutical Benefits Scheme (PBS) API for medicine pricing, prescriber information, schedules, and more.MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to search official NFZ waiting lists in Poland for specialists, diagnostic tests, and procedures near a given location, ranked by forecast waiting time or distance. Results include waiting counts, addresses, phone numbers, accessibility details, and pediatric availability, with no API key required.367 npm15MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: drug_price handles reimbursement, co-payment, and price comparisons; drug_info retrieves official registry metadata and leaflet links; data_sources explains provenance. There is no meaningful overlap that would cause an agent to misselect between them.
All tool names use consistent snake_case with descriptive noun phrases (drug_price, drug_info, data_sources). The drug_ prefix groups the two drug lookup tools logically, and data_sources is still stylistically consistent.
Three tools are well-scoped for a focused Polish drug pricing and registry lookup server. Each tool has a clear, non-redundant role, and no obvious operation is missing that would justify adding more tools.
The surface covers the core domain well: pricing/refund data, cheaper equivalents, senior/child/pregnancy exemptions, registry details, pack EANs, leaflets, and data provenance. Minor potential gaps exist around broader discovery or safety/interaction information, but the stated scope is substantially covered.