Renpho MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENPHO_EMAIL | Yes | Your Renpho Health account email address | |
| RENPHO_PASSWORD | Yes | Your Renpho Health account password |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_userB | Get current Renpho user information |
| get_latest_measurementB | Get the most recent body composition measurement from Renpho scale |
| get_body_compositionB | Get detailed body composition analysis with health classifications |
| get_weight_trendD | – |
| get_measurementsD | – |
| health_checkB | Check the health status of the Renpho MCP server and API connection |
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 6 tools
Most tools have distinct purposes: get_body_composition, get_current_user, get_latest_measurement, and health_check are clearly different. However, get_latest_measurement and get_measurements could be ambiguous without descriptions, as they both relate to measurements but differ in scope (latest vs. all).
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_body_composition, get_current_user). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 6 tools, the count is well-scoped for a Renpho health and body composition server. Each tool appears to earn its place by covering user info, measurements, trends, and server health, without being overly sparse or bloated.
The tool set covers core read operations for body composition, measurements, and user info, but lacks obvious write or update capabilities (e.g., no tools for setting user data or logging new measurements). Additionally, get_measurements and get_weight_trend have no descriptions, creating gaps in understanding their full scope and usage.