a207-his-mcp
Related Servers
Alternatives to a207-his-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceMCP server for pediatric CKD nutrition and food calculations, enabling energy/protein targets, food nutrient lookup, substitutions, meal summaries, and drug-nutrient interaction checks.8-
- FlicenseAqualityBmaintenanceMCP server for pediatric CKD follow-up management, providing tools to schedule follow-ups based on KDIGO 2024 guidelines, retrieve follow-up records, compute adherence scores, and access PEW history.4-
- AlicenseAqualityBmaintenanceThis MCP server generates individualized meal plans for children with chronic kidney disease (CKD) based on KDIGO 2024/PRNT 2020/KRCP 2025 guidelines, incorporating patient age, CKD stage, allergies, dietary culture, and diet diary analysis. It provides deterministic nutrient computations and tools for meal plan generation, food database lookup, and risk analysis.13MIT
- FlicenseAqualityBmaintenanceMCP server for pediatric CKD lab data, providing lab panel queries, critical value alerts, trend analysis, and write operations with role-based permissions.5-
- FlicenseAqualityBmaintenanceMCP server for pediatric CKD clinical calculations, providing eGFR-Schwartz estimation and KDIGO 2024 CKD staging, restricted to doctors.2-
- AlicenseAqualityCmaintenanceMock MCP server for pediatric CKD risk warning, enabling patient biochemical trend retrieval, deterministic risk rule evaluation, structured alert triggering, and clinical SOP lookup using simulated data.5MIT
TDQS
Scored across 5 tools
Tools have distinct names and purposes, but get_patient_profile overlaps with get_diagnosis and get_nutrition_ceiling by including diagnosis and nutrition limits in its data. While role-based views and descriptions help clarify intended usage, an agent could be uncertain whether to call the specialized getter or the full profile.
All tools follow a consistent verb_noun pattern with snake_case (get_patient_profile, get_diagnosis, verify_guardian_binding, list_patients, get_nutrition_ceiling). The verbs are predictable (get/list/verify) and resources are clearly named.
Five tools is well-scoped for a patient-data access server focused on read operations and authorization. Each tool serves a distinct function in the workflow, with no redundant or trivial tools.
The server covers core read workflows: patient lookup, detailed profile access, diagnosis verification, nutrition limits, and guardian authorization. Minor gaps exist, such as lacking a separate tool for labs or diet diary, but they are embedded in the profile, so agents can achieve their goals without dead ends.