Skip to main content
Glama
rwestergren

inbody-api-mcp

by rwestergren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to inbody-api-mcp

No user-submitted related servers found.

    Related Servers

    • renpho-mcp

      jegork
      A
      license
      A
      quality
      A
      maintenance
      Enables 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
      17 npm
      MIT

    • zepp-mcp

      Adisudirta
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to access Zepp/Amazfit health and fitness data such as steps, sleep, heart rate, workouts, and user profile information via tools.
      -

    • whoop-mcp-resilient

      dssolutions-mx
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to WHOOP health data through MCP clients, including recovery, HRV, sleep, strain, workouts, cycles, trends, and period comparisons, with resilient handling of outages, token refresh, and natural-language dates.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources