A
licenseNot graded
qualityC
maintenanceProvides AI with read-only access to Apple Health data via three tools (health_now, health_detail, health_trends). Deployable on Cloudflare with a one-click mobile setup.
MIT
Vaultbeat MCP Server
by Fino-wind
Related Servers
Alternatives to Vaultbeat MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceEnables 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.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables AI to read-only access Apple Health data (current status, sleep, trends) via a Cloudflare-deployed MCP server, using iPhone shortcuts to sync data.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI to read-only access Apple Health data (current stats, sleep details, and trends) via a Cloudflare-deployed MCP server, using iPhone shortcuts to sync data securely.MIT
TDQS
A4.1/5.0
Scored across 33 tools
Disambiguation4/5
The read tools are cleanly separated by metric, and the write tools are deliberately split into replace/append pairs with emphatic warnings, so an agent can usually select correctly. The main residual ambiguities are the entry/append pairs and vaultbeat_sync_sleep vs get_sleep_detail, whose names don't fully telegraph their different purposes.
Naming Consistency4/5
Reads follow get_<metric>, writes follow log_<domain>_<mode>, analytics share the metric_* pattern, and server operations use the vaultbeat_* prefix. Minor deviations — vaultbeat_sync_sleep is a read under a different prefix, log_note lacks the _entry suffix, and vaultbeat_status/doctor are noun-like — are noticeable but don't undermine predictability.
Tool Count2/5
At 33 tools this is a heavy surface for an agent to navigate, well past the 25+ threshold. Many get_* tools repeat identical owner-filtering and coverage semantics and could be consolidated, even though each metric has some unique fields.
Completeness4/5
The server covers an unusually broad set of health metrics, provides read, append, replace, and deliberate delete paths for the writable domains, and includes diagnostics plus a binding lifecycle. Minor gaps remain — no water-logging write, no dedicated symptom-logging tool (worked around via log_note_append) — but agents can generally proceed without dead ends.
Maintenance
ActivityActive
ResponsivenessNo issues