Skip to main content
Glama
ayeyouok

a207-meal-plan-mcp

by ayeyouok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to a207-meal-plan-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

    • a207-nutrition-assessment-mcp

      ayeyouok
      F
      license
      A
      quality
      B
      maintenance
      Enables pediatric CKD nutrition assessment by calculating PRNT energy/protein targets, evaluating dietary intake against those targets, and screening for PEW risk, with support for dialysis, vegetarian diets, and edema corrections.
      5
      -

    • ckd-parent-guide-mcp

      rpint
      A
      license
      A
      quality
      C
      maintenance
      Provides deterministic parental guidance for children with chronic kidney disease, including food safety checks, lab report interpretation, and nutrient-aware food substitutions based on authoritative guidelines and the Chinese Food Composition Table.
      12
      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
      -
    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 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one generates a new meal plan, the other aggregates nutrient data from an existing plan. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: 'generate_meal_plan' and 'get_meal_plan_nutrients'. The naming style is uniform and predictable.

    Tool Count3/5

    With only 2 tools, the server feels minimal. While the narrow scope is defensible, it sits at the borderline where 1-2 tools are typically considered thin for a functional domain.

    Completeness3/5

    The tool surface covers generation and nutrient validation, but lacks update/delete/list operations for meal plans. There are notable gaps in lifecycle management, though the core generation workflow is present.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources