Doctor Claude
Related Servers
Alternatives to Doctor Claude
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides AI systems with access to peer-reviewed medical information from StatPearls, enabling searches for diseases and medical conditions with comprehensive, reliable content formatted in AI-friendly Markdown.2-
- AlicenseAqualityCmaintenanceEnables searching medical literature, clinical trials, drug information, guidelines, and medical fee schedules directly from Claude, returning only original sources and text without medical judgment.9MIT
- AlicenseNot gradedqualityFmaintenanceProvides comprehensive medical information by querying authoritative sources including FDA drug database, WHO health statistics, PubMed literature, RxNorm nomenclature, Google Scholar, and Australia's PBS API through 22+ specialized tools.82 npm3MIT
- AlicenseNot gradedqualityDmaintenanceA specialized Model Context Protocol server that enhances AI-assisted medical learning by connecting Claude Desktop to PubMed, NCBI Bookshelf, and user documents for searching, retrieving, and analyzing medical education content.7MIT
- 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.82 npmISC
- 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.82 npmISC
TDQS
Scored across 6 tools
Each tool targets a distinct operation: searching for articles, fetching article content, managing patient profile (set/get/delete), and calculating clinical scores. No two tools overlap in purpose.
All tool names follow a consistent `verb_noun` pattern with snake_case (e.g., `fetch_medical_article`, `get_patient_profile`), making the action and resource clear.
With 6 tools, the server is well-scoped: 3 for patient profile management, 2 for medical information retrieval, and 1 for clinical scoring. This covers core functionality without unnecessary bloat.
The tool set covers the full lifecycle: search/fetch medical info, save/retrieve/delete patient context, and calculate relevant clinical scores. No obvious missing operations for the stated purpose.