Hospital Data MCP Server
Related Servers
Alternatives to Hospital Data MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables LLMs to securely query synthetic clinical data through validated, scoped tools (patient summaries, conditions, medications, lab trends, encounters) while maintaining audit logs and access controls.-
- FlicenseNot gradedqualityCmaintenanceA healthcare MCP demo server exposing clinical resources, tools, and prompts over SSE with authentication, integrated with Pydantic AI and Gemini for natural language patient record updates.-
- AlicenseAqualityBmaintenanceA Claude-compatible MCP server that exposes health-domain tools over 100% synthetic data, built with security and compliance in mind.4MIT
- FlicenseNot gradedqualityBmaintenanceEnables access to patient records, symptom triage, appointment scheduling, and hospital data lookup through a JSON-RPC MCP interface with HTTP and stdio transports.-
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables secure, read-only access to synthetic preventive-care patient records and bounded IRIS namespace health metrics through a small set of allowlisted, parameterized tools.MIT
- AlicenseAqualityCmaintenanceMCP server for FHIR interoperability, enabling natural language querying and manipulation of clinical data with full CRUD operations, semantic search, and RAG capabilities.13MIT
TDQS
Scored across 8 tools
Most tools target distinct data types (drug info, vital signs, patient info, medical info). The only overlap is wxoGetPatient360, which explicitly aggregates the individual patient-related getters, but its purpose as a composite view is clear from the description.
All tools follow the exact same 'wxoGet' + PascalCase noun pattern, creating a predictable and uniform naming convention. The minor typo in 'DrugInterations' does not affect the consistent structure.
With 8 tools, the server is well-scoped for a hospital data access API. The number is within the ideal 3-15 range and each tool serves a clear query purpose.
The tool set covers core patient, medical, vital signs, and drug-related queries, but lacks search/list operations (e.g., find patients, search drugs) and any write capabilities. While likely read-only, the absence of basic lookup endpoints creates notable gaps for general hospital data exploration.