F
licenseNot graded
qualityC
maintenanceMCP server enabling Claude Desktop to answer questions from local Word and PDF documents by searching a vector index built from their contents.
-
Medical Knowledge MCP Server
Related Servers
Alternatives to Medical Knowledge MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables Claude Desktop to search and read local documents via full-text and fuzzy search, providing direct access to indexed files without chunking.MIT
- AlicenseNot gradedqualityDmaintenanceA specialized MCP server for Claude Desktop that enhances AI-assisted medical learning by fetching and processing educational resources from PubMed, NCBI Bookshelf, and user-provided documents.MIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server for Claude Desktop with persistent task management, file operations, document generation, and PDF indexing.205 npm1MIT
- AlicenseNot gradedqualityFmaintenanceA local MCP server that integrates with Claude Desktop, enabling RAG capabilities to provide Claude with up-to-date private information from custom LlamaCloud indices.225MIT
FHIRfly MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceMCP server for connecting Claude Desktop to FHIRfly healthcare reference data APIs, enabling lookup of drugs, providers, clinical codes, and more.126 npmMIT
TDQS
A3.7/5.0
Scored across 9 tools
Disambiguation3/5
The clinical tools (calculate_health_score, recommend_smart_cards, generate_care_plan) are distinct, but the repository maintenance tools overlap: sync_repositories essentially combines check_git_status and pull_git_updates, and pull_git_updates vs refresh_knowledge_base both have refresh effects. The descriptions help, but an agent could easily select the wrong sync/pull/check tool.
Naming Consistency5/5
All nine tools follow a consistent verb_noun snake_case pattern (calculate, recommend, generate, refresh, check, pull, sync, get, search). This makes the tool set predictable and easy to navigate.
Tool Count5/5
Nine tools is well within the ideal range and each tool serves a clear purpose in either clinical reasoning or knowledge base maintenance. The count feels appropriately scoped for a medical knowledge server.
Completeness4/5
The surface covers core clinical workflows (scoring, interventions, care plans) and knowledge base maintenance (search, read, refresh, git sync). Minor gaps exist, such as no tool to list all available files or directly edit knowledge content, but these can be worked around via git and file operations.
Maintenance
ActivityInactive
ResponsivenessNo issues