Skip to main content
Glama
davidmosiah

Delx Living Body

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Delx Living Body

No user-submitted related servers found.

    Related Servers

    • mcp-server-withings

      borgels
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Withings Health API with per-user OAuth2, enabling users to securely access their own health data (measures, activity, sleep, workouts, heart rate, devices, and goals) and optionally add measurements.
      12
      Apache 2.0

    • Garmin MCP

      lokranjanp
      A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes Garmin Connect health and activity data (steps, sleep, stress, activities, etc.) via tools for querying, analysis, and visualization.
      17
      Apache 2.0

    • health-mcp

      jonathan249
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes personal Garmin wellness data through MCP tools for accessing summary, sleep, HRV, heart rate, stress, body battery, and historical data.
      MIT

    • Zepp Cloud MCP

      aryarfani
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Amazfit/Zepp fitness data via the unofficial Zepp cloud API, exposing normalized health and workout metrics to MCP clients.
      -

    • personal-health-mcp

      adamconde
      A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted MCP server that aggregates personal health data from Google Health, Oura, and Withings into a single, provider-attributed interface with configurable source of truth preferences.
      MIT

    • mcp-garmin

      PilarJ
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes Garmin Connect data through MCP, enabling retrieval of activities, health metrics, training status, and workouts, with OAuth authentication and confirmed write operations.
      MIT
    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.5/5.0

    Scored across 9 tools

    Disambiguation2/5

    Three tools—connection_status, status, and health_check—all report connector availability and can be easily confused. Similarly, agent_manifest, data_inventory, and capabilities all serve self-description/onboarding purposes, making the tool boundaries unclear.

    Naming Consistency3/5

    All tools share the living_body_ prefix and snake_case, which is helpful, but the pattern is mostly noun phrases with occasional verb forms like ask and compose_context. The naming is readable but not a consistent verb_noun convention.

    Tool Count4/5

    Nine tools is within the ideal range, but several status and metadata tools overlap significantly, making the set feel slightly padded. The count is not excessive overall.

    Completeness4/5

    The core workflows—discovering connectors, checking health, asking wellness questions, and composing context—are covered. Minor gaps like direct per-connector data access or configuration tools exist, but agents can likely work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources