med-lit-mcp
Related Servers
Alternatives to med-lit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to search authoritative drug, health statistics, medical literature, clinical guideline, clinical trial, and pediatric sources such as FDA, WHO, PubMed, RxNorm, and Google Scholar, with local privacy and no API keys.101 npmISC
- FlicenseNot gradedqualityCmaintenanceEnables dental research and clinical intelligence by providing tools to search PubMed, systematic reviews, verify citations, and query ClinicalTrials.gov directly from Claude Web and Claude Desktop.-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query authoritative medical sources such as FDA, WHO, PubMed, RxNorm, and ClinicalTrials.gov for drug information, safety data, health statistics, clinical guidelines, pediatric resources, and evidence-graded literature. Runs locally with no API keys or data leaving the machine.101 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to query authoritative medical sources such as FDA, WHO, PubMed, RxNorm, and ClinicalTrials.gov for drug information, medical literature, health statistics, clinical guidelines, and pediatric resources through local MCP tools.101 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query authoritative medical sources such as FDA, WHO, PubMed, RxNorm, and ClinicalTrials.gov for drug information, health statistics, medical literature, clinical guidelines, and pediatric resources. Runs locally with no API keys or cloud dependencies, adding resilience, caching, and evidence grading to every lookup.101 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query authoritative sources like FDA, WHO, PubMed, RxNorm, and Google Scholar for drug information, health statistics, clinical guidelines, trials, and medical literature. It runs locally with no API keys, so data stays private while results come back with evidence grading and resilient fallbacks.101 npmISC
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: drug entries, PubMed searches, abstract retrieval, clinical trial search, guideline discovery, drug search, and shinryo master operations are all clearly separated. Even the two drug-related tools (search_drug and fetch_drug_entry) have a clear search-then-fetch workflow, avoiding overlap.
The naming follows a mostly consistent pattern with verb prefixes (search_, fetch_, import_, find_), though shinryo_master_status deviates by being a noun phrase instead of an action. Minor inconsistency with 'find_guideline' versus 'search_' but overall the pattern is predictable and readable.
With 9 tools, the server is well-scoped for its purpose of medical literature and drug/reimbursement information retrieval. Each tool covers a distinct domain or step in a workflow, and the count feels neither bloated nor insufficient for the stated functionality.
The surface covers the main workflows: drug search/detail, PubMed search/abstract, clinical trial lookup, guideline discovery, and shinryo master management. Minor gaps exist, such as lacking full-text article retrieval beyond abstracts or direct PMDA label fetching, but these are acknowledged as external limitations and agents can work around them.