Skip to main content
Glama
crixalis17

ultrahuman_mcp

by crixalis17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ultrahuman_mcp

No user-submitted related servers found.

    Related Servers

    • Oura MCP Server

      koji117
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Oura Ring health data, including sleep, activity, readiness, and stress metrics via the Model Context Protocol. It enables users to query their personal biometric information and daily health summaries through natural language in MCP-compatible clients.
      681 npm
      MIT

    • Ultrahuman MCP Server

      Vodolazkyi
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Ultrahuman health and fitness data through standardized MCP tools, enabling AI assistants to retrieve metrics like sleep, movement, heart rate, and glucose.
      1
      MIT

    • oura-mcp-server

      trenerok
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to access Oura Ring health data including sleep, activity, readiness, heart rate, and stress through read-only tools.
      40
      6 npm
      1
      MIT

    • Oura MCP

      davidmosiah
      A
      license
      B
      quality
      A
      maintenance
      Local-first MCP server that connects AI agents to your Oura Ring readiness, sleep, activity, and HRV data. Tokens never leave your machine.
      27
      88 npm
      2
      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 7 tools

    Disambiguation4/5

    Each tool targets a specific health metric (recovery, temperature, heart, sleep, activity), but get_health_summary and get_daily_metrics overlap with the specific tools, though descriptions clarify their distinct purposes as summary and raw access.

    Naming Consistency5/5

    All tools follow a consistent get_<metric> naming pattern, making it easy to predict tool names and purposes.

    Tool Count5/5

    Seven tools is well-scoped for a health data server, covering the major health domains without unnecessary redundancy.

    Completeness4/5

    The tool set covers key health metrics (recovery, temperature, heart, sleep, activity) and provides both summary and raw data access. Minor gaps include lack of historical trend queries beyond recent minutes, but core read-only health tracking is well covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources