A
licenseA
qualityA
maintenanceEnables 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.
7
242
MIT
inbody-api-mcp
by rwestergren
Related Servers
Alternatives to inbody-api-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceRead access to Withings scale data, including weight and body composition metrics, through a local MCP server.-
- AlicenseNot gradedqualityCmaintenanceEnables reading Withings smart-scale data (weight, body composition, etc.) through MCP tools, with OAuth2 authentication and automatic token refresh.MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to access Zepp/Amazfit health and fitness data such as steps, sleep, heart rate, workouts, and user profile information via tools.-
- FlicenseNot gradedqualityCmaintenanceExposes user profile data from the Sapphire Wellness App via MCP tools for health alerts, personalised recommendations, and partner service subscriptions.-
- FlicenseNot gradedqualityBmaintenanceEnables read-only access to Amazfit/Zepp fitness data via the unofficial Zepp cloud API, exposing normalized health and workout metrics to MCP clients.-
TDQS
A4.4/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: get_profile returns user identity and baseline metrics; get_scan returns full metrics for a specific scan; get_scan_count returns the total number of scans; list_scans returns a summary list of scans. No overlap or ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case: get_profile, get_scan, get_scan_count, list_scans. The convention is uniform and predictable.
Tool Count5/5
With 4 tools, the server is well-scoped for an InBody API: it provides profile retrieval, scan listing, scan detail, and scan count. No unnecessary tools, and the count is appropriate for the domain.
Completeness4/5
The tool set covers the essential read operations for InBody scans and user profile. A minor gap is the lack of filtering or searching scans by date range, but the core workflow (list, get detail, count) is fully supported.
Maintenance
ActivityInactive
ResponsivenessNo issues