Skip to main content
Glama
ayeyouok

a207-lis-mcp

by ayeyouok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to a207-lis-mcp

No user-submitted related servers found.

    Related Servers

    • nfyy-ckd-risk-warning-mcp

      rpint
      A
      license
      A
      quality
      C
      maintenance
      Mock 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.
      5
      MIT

    • a207-followup-mcp

      ayeyouok
      F
      license
      A
      quality
      B
      maintenance
      MCP 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
      -

    • a207-his-mcp

      ayeyouok
      F
      license
      A
      quality
      B
      maintenance
      Read-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
      -

    • ckd-meal-plan-mcp

      rpint
      A
      license
      A
      quality
      B
      maintenance
      This 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.
      13
      MIT

    • a207-clinical-calc-mcp

      ayeyouok
      F
      license
      A
      quality
      B
      maintenance
      MCP server for pediatric CKD clinical calculations, providing eGFR-Schwartz estimation and KDIGO 2024 CKD staging, restricted to doctors.
      2
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: one write (upsert_lab_result), one patient listing (list_known_patients), and three distinct read views (get_labs for all panels, get_critical_values for urgent flags, get_lab_trend for single-analyte time series). No two tools overlap in purpose; the descriptions clearly separate them.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: upsert_lab_result, list_known_patients, get_labs, get_critical_values, get_lab_trend. The verbs (upsert, list, get) are appropriate for their actions, and the nouns are descriptive and consistent.

    Tool Count5/5

    Five tools is a well-scoped size for a LIS MCP server. It covers the essential operations—write, patient lookup, general read, critical value alert, and trend analysis—without unnecessary redundancy or overwhelming the agent.

    Completeness4/5

    The tool set covers the core LIS lifecycle: inserting/updating results, retrieving patient panels, accessing critical values, and analyzing trends. The only minor gaps are lack of a delete operation and no granular single-result fetch by ID, but these are likely intentional and not critical for typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources