MCP.Market

Inbody API MCP server

by rwestergren·io.github.rwestergren/inbody-api-mcp·v0.1.0·10 stars
No reviews yet

MCP server for InBody body-composition data — scans, body fat, muscle mass, body water

B72/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B72/100

full report

Adoption
Growing

10 stars132 downloads/wk

Reviews

Write one

Nobody has reviewed Inbody API yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Inbody API tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_profile

    Get the InBody user profile.

  • get_scan

    Get the full metric set for a single InBody scan.

  • get_scan_count

    Get the total number of InBody scans available for the account.

  • list_scans

    List InBody scans with headline metrics, newest first.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 99 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Inbody API compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
72/100
higher than 37% of 48,243 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
10
more than 88% of 28,706 servers
Downloads a week
132
more than 68% of 12,306 servers with a package

What its tools let an agent do: 4 read

Install Inbody API in Claude Code, Cursor or VS Code

claude mcp add inbody-api-mcp -- uvx inbody-api-mcp
Add to Cursor

What the publisher says

From the Inbody API repository's README, as published. We do not edit it. Read it on GitHub

inbody-api-mcp

<!-- mcp-name: io.github.rwestergren/inbody-api-mcp -->

Hosted version for Claude.ai, ChatGPT, and Grok coming soon. Join the waitlist →

An MCP (Model Context Protocol) server for InBody body-composition data, built on the reverse-engineered mobile REST API used by the InBody Android app.

InBody has no public API and no web UI for personal scan data. This server talks to the same JSON REST endpoints the mobile app uses, exposing your body composition history (body fat, muscle mass, body water, segmental impedance) to any MCP client.

Features

normal ranges (MFA), and segmental/multi-frequency impedance (IMP)

  • Profile -- identity and baseline metrics (height, weight, age, gender)
  • Scan history -- chronological summaries (weight, BMI, % body fat, muscle mass)
  • Full scan metrics -- complete body composition (BCA), BMI/%fat/muscle with

your country code

  • Automatic region routing -- resolves the correct regional API host from
  • Automatic re-authentication -- caches the 24h JWT and re-logs in on expiry

Quick Start

1. Install uv

curl -LsSf https://astral.sh/uv/install.sh | sh

2. Set credentials

export INBODY_LOGIN_ID="3026323617"   # registration phone number, digits only
export INBODY_LOGIN_PW="your-password"
export INBODY_COUNTRY_CODE="US"       # ISO country code (default US)

INBODYLOGINID is the phone number used at registration, not your email

-- digits only, no country code or + (e.g. 3026323617). InBody keys login

on the phone number; the email is only returned as profile data. An email

value will fail login with EmptyData.

3. Configure your MCP client

uvx downloads and runs the server on demand -- no separate install step.

OpenCode (opencode.json)

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "inbody": {
      "type": "local",
      "command": ["uvx", "inbody-api-mcp"],
      "environment": {
        "INBODY_LOGIN_ID": "{env:INBODY_LOGIN_ID}",
        "INBODY_LOGIN_PW": "{env:INBODY_LOGIN_PW}",
        "INBODY_COUNTRY_CODE": "US"
      },
      "enabled": true
    }
  }
}

Claude Desktop (claudedesktopconfig.json)

{
  "mcpServers": {
    "inbody": {
      "command": "uvx",
      "args": ["inbody-api-mcp"],
      "env": {
        "INBODY_LOGIN_ID": "3026323617",
        "INBODY_LOGIN_PW": "your-password",
        "INBODY_COUNTRY_CODE": "US"
      }
    }
  }
}

Available Tools

This server is read-only: no write or delete endpoints are exposed.

How It Works

This server communicates with the regional *.lookinbody.com REST API -- the same backend used by the InBody Android app (v2.8.31). The API was reverse-engineered by capturing app traffic with mitmproxy and confirming payload shapes against the live API.

The auth flow:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Inbody API: common questions

Is Inbody API MCP server safe?
Mostly: it is graded B (72/100). Read the Inbody API safety report
How do I install Inbody API?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Inbody API need an API key?
Yes. The registry entry asks for INBODY_LOGIN_PW.
Is Inbody API maintained?
The last commit was 139 days ago (2026-06-19). The latest release is v0.1.0.
How does Inbody API compare with other MCP servers?
safety score 72/100 (higher than 37% of 48,243 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from rwestergren →