renpho-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENPHO_EMAIL | Yes | Required RENPHO Health account email | |
| RENPHO_PASSWORD | Yes | Required account password | |
| RENPHO_AREA_CODE | No | Two uppercase letters, defaults to US; use your account's country code | US |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_userA | Read the logged-in RENPHO Health account profile. Credentials and tokens are excluded. |
| get_scale_usersA | List linked scale tables and profile IDs. Use a returned userIds value as scaleUserId when selecting a family profile. |
| get_measurementsA | Read body composition history, newest first, with native RENPHO fields and unit codes. Filters ownership before pagination. Check scanComplete before treating results as complete. No health classifications are computed. |
| get_latest_measurementA | Read the latest owned measurement and all available body composition fields. Returns null when none match. Refuses to claim latest if the scan limit is reached. |
| get_weight_trendA | Summarize positive weight readings over the past N days in native kg, lb, or stone. Rejects incomplete scans and inconsistent, missing, or mixed stone/pounds unit codes. This is arithmetic, not medical advice. |
| refresh_sessionA | Discard the in-memory login session. The next data request authenticates again. Does not trigger scale uploads or change RENPHO data. |
| health_checkA | Verify RENPHO login and scale discovery without returning measurements. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.