Renpho MCP Server
Related Servers
Alternatives to Renpho MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables access to Renpho smart-scale body-composition data via the Renpho Health cloud API, providing metrics, trends, and diagnostics to Claude.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query and analyze Renpho smart scale data (weight, body fat, etc.) by syncing it from the Renpho app and exposing it through MCP tools for conversational exploration.1MIT
- AlicenseAqualityCmaintenanceEnables AI clients to query Withings health data such as weight, body composition, heart rate, temperature, SpO2, activity, sleep, workouts, and ECG recordings.17MIT
- AlicenseNot 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.2ISC
- AlicenseAqualityBmaintenanceEnables 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.714 npmMIT
- 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-
TDQS
Scored across 9 tools
Most tools target clearly distinct resources or actions: user info, scale-user mappings, latest measurement, body composition, trend, refresh, health, and diagnostics. The main ambiguity comes from missing descriptions on get_measurements, get_weight_trend, and get_sync_diagnostics, plus some potential overlap between get_sync_diagnostics and health_check.
All tools use snake_case, which is consistent and readable. The pattern is mostly get_* for retrieval, but refresh_data and health_check deviate from the verb_noun convention, and health_check uses noun_verb ordering.
Nine tools is well-scoped for a read-only Renpho scale integration. Each tool appears to cover a distinct user need or operational role, with no excessive bundling or unnecessary endpoints.
The surface covers the core read-only lifecycle: current user, linked scale users, latest and historical measurements, body composition, trends, refresh, diagnostics, and health. Minor gaps include missing descriptions for key retrieval tools and no explicit measurement-detail or date-range filtering operation, though get_measurements may cover this.