Skip to main content
Glama
ayeyouok

a207-followup-mcp

by ayeyouok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to a207-followup-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • 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-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
      -

    • a207-lis-mcp

      ayeyouok
      F
      license
      A
      quality
      B
      maintenance
      MCP server for pediatric CKD lab data, providing lab panel queries, critical value alerts, trend analysis, and write operations with role-based permissions.
      5
      -

    • 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
      -
    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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct function: scheduling, reading records, computing adherence, and retrieving PEW history. There is slight potential confusion between get_followup_records and get_pew_history since both are reads related to the timeline, but the descriptions clarify their specific scopes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (schedule_followup, get_followup_records, get_adherence_score, get_pew_history). The 'get_' prefix is uniformly used for read operations, with no mixed conventions or camelCase deviations.

    Tool Count5/5

    Four tools cover the core follow-up workflow—creating plans, reading records, scoring adherence, and aggregating PEW data. This is well-scoped for the server's purpose and falls within the ideal 3-15 range.

    Completeness3/5

    The server supports creating and reading follow-up plans/records but lacks update/delete operations for plans, which are common lifecycle needs. It also has no tool to record completed follow-ups, leaving notable gaps in the follow-up management cycle.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources