renpho-mcp
Related Servers
Alternatives to renpho-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to read smart-scale weight and body-composition data from the associated cloud account, listing members and retrieving the latest measurement or recent history.3MIT
- FlicenseNot gradedqualityCmaintenanceRead access to Withings scale data, including weight and body composition metrics, through a local MCP server.-
- AlicenseCqualityCmaintenanceProvides access to body composition data from Renpho smart scales, enabling users to query weight, BMI, body fat percentage, muscle mass, and other health metrics with trend analysis over customizable time periods.267MIT
- AlicenseAqualityCmaintenanceEnables retrieval of InBody body composition data including profile, scan history, and full metrics via MCP tools.411MIT
- 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 gradedqualityBmaintenanceEnables access to Renpho smart-scale body-composition data via the Renpho Health cloud API, providing metrics, trends, and diagnostics to Claude.MIT
TDQS
Scored across 7 tools
Tools are mostly distinct: get_measurements vs get_latest_measurement vs get_weight_trend could be confused, but their descriptions clearly differentiate history, latest, and summary. Other tools (user, scale users, session, health) are unambiguous. Minor overlap in measurement-related tools.
Naming is predominantly verb_noun with 'get_' prefix (get_current_user, get_scale_users, get_measurements, etc.), but 'refresh_session' and 'health_check' deviate slightly from the 'get_' pattern while still following verb_noun or noun style. Overall consistent snake_case and readable.
7 tools is well-scoped for a health scale integration, covering authentication, user info, scale discovery, health checks, and measurement retrieval. Each tool serves a clear purpose without redundancy or bloat.
The tool surface covers the core lifecycle for a read-only scale API: session management, user profile, device discovery, measurements history, latest measurement, and trend analysis. No obvious gaps for typical use cases; missing write operations are not expected for this domain.