eufylife-scale-mcp
Related Servers
Alternatives to eufylife-scale-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables read-only access to RENPHO Health smart scale measurements through MCP, allowing users to retrieve latest readings, body composition history, and weight trends via an MCP client.711 npmMIT
- FlicenseNot gradedqualityCmaintenanceRead access to Withings scale data, including weight and body composition metrics, through a local MCP server.-
- FlicenseNot gradedqualityDmaintenanceProvides access to body composition data from FeelFit smart scales, including measurements like weight, BMI, and body fat. Supports multi-account management and health goal tracking via the FeelFit Cloud API.2-
- FlicenseNot gradedqualityDmaintenanceEnables retrieval of health data from Withings smart scales including weight measurements and comprehensive body composition metrics like fat mass, muscle mass, and hydration levels. Supports multiple users, unit preferences, and OAuth authentication for secure access to personal health data.2-
- AlicenseNot gradedqualityCmaintenanceEnables reading Withings smart-scale data (weight, body composition, etc.) through MCP tools, with OAuth2 authentication and automatic token refresh.MIT
- AlicenseAqualityCmaintenanceEnables retrieval of InBody body composition data including profile, scan history, and full metrics via MCP tools.49MIT
TDQS
Scored across 3 tools
The three tools target distinct resources: member listing vs. measurement retrieval. However, get_latest_measurement is essentially a special case of get_measurement_history (the newest entry), so an agent could reasonably confuse the two when only the latest reading is needed.
All tools follow a consistent verb_noun snake_case pattern: list_members, get_latest_measurement, get_measurement_history. The verbs are appropriate and predictable for their actions.
Three tools is a small but reasonable surface for a read-only smart-scale integration. Each tool has a clear role, though the set sits at the lower bound and leaves little margin for additional read operations.
The core read paths are covered: enumerate members, fetch the latest body-composition measurement, and retrieve historical weigh-ins. Minor gaps exist (e.g., no tool to fetch a single measurement by ID, no member-specific filter explicitly documented), but nothing that would block typical agent queries.