Skip to main content
Glama
okizuka-hitts

personal-health-mcp

by okizuka-hitts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to personal-health-mcp

No user-submitted related servers found.

    Related Servers

    • Renpho Health MCP

      aniruddh-jammoria
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query and analyze Renpho smart scale data (weight, body fat, etc.) by syncing it from the Renpho app and exposing it through MCP tools for conversational exploration.
      1
      MIT

    • withings-mcp

      stefanocaronia
      A
      license
      B
      quality
      C
      maintenance
      Enables Claude and other MCP clients to securely read your own body measurements, daily activity, sleep summaries, and paired devices from the official Withings API, with everything running locally.
      5
      1
      MIT

    • Withings MCP Server

      Npab19
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects Claude to Withings health data using OAuth 2.0. Provides 11 read-only tools to access body measurements, activity, sleep, heart rate, and device information from Withings devices.
      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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools are clearly distinct: get_latest_body_composition, get_body_composition, get_measurements_range, get_profile, and list_available_metrics each target different data or metadata. The minor overlap between 'latest' and 'range' variants is manageable due to clear descriptions.

    Naming Consistency4/5

    Tool names predominantly follow a get_<resource> pattern, which is consistent and readable. The exception is list_available_metrics, which uses 'list_' instead of 'get_', a minor deviation that does not impede understanding.

    Tool Count5/5

    Five tools is well within the ideal 3-15 range and appropriately scoped for a personal-health MCP focused on body composition and profile retrieval. No unnecessary tools are present.

    Completeness3/5

    The tool set covers read access to body composition data, profile information, and available metrics, but lacks write operations or management of cached data. Since the domain appears to be read-only retrieval from an external source, the core needs are met, though a few potential gaps exist (e.g., no single-metric query).

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources