vghsdk-mcp
Related Servers
Alternatives to vghsdk-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server with a fictitious clinical database to develop and test agents, providing tools to search patients and retrieve full medical records (inpatient, outpatient, emergency) via HTTP streamable transport.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides healthcare tools for interacting with FHIR data and medical resources on EMRs like Cerner and Epic1MIT
- 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
- FlicenseNot gradedqualityCmaintenanceMCP server for querying student information, validating result data, and analyzing student results from a local database.-
- FlicenseAqualityBmaintenanceRead-only MCP server providing pediatric CKD patient master data with tools for patient profiles, diagnosis, nutrition ceilings, guardian verification, and patient lists, designed for the CKDNutri project.5-
- FlicenseNot gradedqualityDmaintenanceAn MCP server and web application that enables natural language medical queries and patient data analysis powered by Gemini AI. It allows users to track and analyze patient biometrics, including vitals, sleep patterns, and laboratory results, through a comprehensive set of automated medical tools.-
TDQS
Scored across 27 tools
Most tools have clear list/detail pairings (e.g., patient_drug_list vs patient_drug_content), but there is potential confusion between consent_list and consent_search, and between patient_op_schedule and consent_opschedule. patient_opd_list_search also overlaps with patient_opd_list.
Tool names mostly follow a snake_case pattern with domain prefixes (e.g., patient_*, surgery_*, doc_*). Minor deviations like consent_opschedule and ivi_fetch_schedule break the noun_verb pattern, but overall the convention is consistent.
27 tools is heavy, but the server covers multiple hospital subsystems (patient records, surgery, OPD, drugs, consents, schedules). The count feels justified for the broad scope, though some consolidation could reduce redundancy.
The surface covers most hospital workflows: patient demographics, OPD/admission notes, surgery records and schedules, drug lists, consult notes, and consent management. Minor gaps exist (e.g., no lab results or allergy data), but the core needs are well covered.