MCP Tools DirectoryAbout this integration
MCP server for InBody body-composition data — scans, body fat, muscle mass, body water
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.0
- Package
- inbody-api-mcp
- Last compatibility test
- Not independently tested
Connect your agent
inbody-api-mcpPublisher documentation and manifest only; no package, personal health account, credential, or API was executed. The documented tool surface is read-only but handles sensitive health data through a reverse-engineered API.
Capabilities: Read account profile and scan count, List body-composition scan history, Retrieve detailed body-composition and impedance measurements
Connected profiles
Additional details
io.github.rwestergren/inbody-api-mcp
Source ↗ · Checked 2026-09-170.1.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17INBODY_LOGIN_ID, INBODY_LOGIN_PW
Source ↗ · Checked 2026-09-17inbody-api-mcp
Source ↗ · Checked 2026-09-190.1.0
Source ↗ · Checked 2026-09-19The Python project exposes a console script, and the documented client configurations spawn it through uvx over stdio.
Source ↗ · Checked 2026-09-19An InBody registration login identifier and password are required, with a country code used for regional routing; this account-login flow is outside the native auth taxonomy.
Source ↗ · Checked 2026-09-19The server discovers and connects to the appropriate regional lookinbody.com mobile REST endpoint.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19