Skip to main content
Glama
Sign In
Vaultbeat MCP Server

Vaultbeat MCP Server

by Fino-wind
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Vaultbeat MCP Server

No user-submitted related servers found.

    Related Servers

    • apple-health-shortcuts-mcp

      Chloe622-mail
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to read Apple Health data through three tools: current stats, detailed metrics, and trends. Deployable to Cloudflare with a one-click phone setup, exposing only read-only access.
      MIT

    • marrow-mcp

      MarrowHealth
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read your own Apple Health data through a self-hosted SQLite mirror, allowing them to query health metrics, workouts, meals, and strength logs without sending data to the cloud.
      77 PyPI
      4
      MIT

    • Apple Health Shortcuts MCP

      wei0124ovo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read-only access Apple Health data through three tools: current status and sleep, detailed metrics, and 7/14/30-day trends, deployed via one-click on Cloudflare with private-key authentication.
      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.1/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and the descriptions include explicit 'which tool to use' guidance (e.g. get_sleep_detail vs get_sleep_nights vs get_metric, or get_metric vs get_intraday). However, the deliberate log_X_entry (replace) vs log_X_append (add) pairs, plus the many read tools over overlapping metric data, create genuine adjacency that an agent could misselect without reading the long caveats.

    Naming Consistency5/5

    Names follow a strict verb_noun snake_case convention throughout: get_*, log_*, update_*, delete_*, list_*, compare_*, correlate_*. The replace/append split is expressed consistently across note, strength, and food domains, with vaultbeat_doctor as the only (understandable) outlier.

    Tool Count3/5

    29 tools is heavy and sits at the edge of the 'too many' band for a single server. The health domain is broad enough that each tool is justified (multiple data types, read/append/replace variants), but the surface is large enough that an agent must navigate a lot of near-adjacent options.

    Completeness4/5

    Broad lifecycle coverage: symptoms, state of mind, notes, strength, food, weight, and metrics all have create/read (+update or append/delete) paths, and Apple-Health-sourced kinds are correctly read-only. Gaps are minor — no delete for food/strength/notes (only replace/append) — and are largely explained as intentional given the app as source of truth.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources