Skip to main content
Glama
Cole-Will-I-Am

HealthLedger MCP

by Cole-Will-I-Am
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to HealthLedger MCP

No user-submitted related servers found.

    Related Servers

    • Google Health MCP

      davidmosiah
      A
      license
      B
      quality
      A
      maintenance
      A local-first MCP server that enables AI agents to read user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners via OAuth, with tokens never leaving the machine.
      26
      493 npm
      62
      MIT

    • personal-health-mcp

      adamconde
      A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted MCP server that aggregates personal health data from Google Health, Oura, and Withings into a single, provider-attributed interface with configurable source of truth preferences.
      MIT

    • Apple Health AI Bridge MCP

      roian6
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server that exposes Apple Health data (steps, workouts, sleep, etc.) from a local SQLite store, allowing AI agents to query health metrics without sending data to hosted services.
      7
      Apache 2.0

    • indaga-agent

      birinets
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server for querying multi-omic personal health data (genome, labs, wearables) with an honesty contract and progressive disclosure skills.
      1
      AGPL 3.0
    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

    C2.9/5.0

    Scored across 79 tools

    Disambiguation3/5

    Most tools are scoped to distinct domains, but there is meaningful overlap among the many trend-analysis tools (analyze_trend, analyze_metric, analyze_lab_trend, analyze_wearable_trend, etc.) and between generic catch-all records and domain-specific records. The detailed descriptions help, but with 79 tools the risk of misselection is elevated.

    Naming Consistency4/5

    The overwhelming majority of tools follow a clear verb_noun pattern like list_medications, add_condition, and delete_record. Minor deviations exist with noun-phrase names such as health_agenda, data_coverage, and semantic_search, and the mix of get_ vs list_ for retrieval actions creates slight inconsistency without breaking the overall pattern.

    Tool Count1/5

    79 tools is far beyond the practical range for an MCP server and will heavily burden tool selection and context windows. The count is driven by repetitive add/list pairs across many domains plus multiple overlapping analysis tools, making the surface feel bloated rather than curated.

    Completeness4/5

    The server covers an impressively broad health-record surface: profiles, metrics, events, notes, medications, labs, imaging, genomics, procedures, care tasks, documents, family history, and more. The main gap is the lack of a generic update/edit path beyond delete-plus-re-add, though delete_record and set_profile partially mitigate this for corrections.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources