v1.2.8 is live on the App Store→

Apple Health → MCP → your own agent

Your AI can read
your health.
We never can.

Vaultbeat streams your Apple Health to the AI agent you run yourself — encrypted on your iPhone before it leaves, and synced in the background with no exports to file away.

Free to record on your iPhone. Pairing a machine starts three days of full agent access.

Architecture

Plaintext exists at both ends, and nowhere in between

The app is a bridge, not a vault. It seals each record on your iPhone and keeps the ciphertext moving; the only places it opens again are your own devices and the machines you chose to pair.

On your iPhone

Encrypted before it leaves

Apple Health writes a night's sleep; Vaultbeat seals it on the device. Continuously, in the background — no export, no zip file, no file path to paste.

In the cloud

Ciphertext only

We route it and store it. We hold no key and no way to make one, so what sits on our servers is unreadable to us by design — not by policy.

On a machine you paired

Decrypted where you are

Scan a QR code once from a computer you trust. From then on that machine — and your own devices — can open it. Nothing in the code is a key travelling to it.

Your own agent

Reads it like a file

Claude Code, Hermes, OpenClaw — anything that speaks MCP queries your sleep, cycle, weight and heart history the same way it queries your filesystem.

The same night, twice

One of these is what your agent reads.
The other is what we store.

Encryption happens on your iPhone, before the record leaves it. We route the result and keep it; we hold no key and no way to make one. Whether that is true is not a promise you have to take — it is the difference between these two columns.

On a machine you paired

Decrypted, on your hardware

date2026-09-21
asleep7h 42m
deep1h 18m
rem2h 04m
heart · avg52 bpm
respiratory14.2 / min

Illustrative values, not a real person’s night.

What an MCP client receives after your own machine opens the envelope with the key held in your iCloud Keychain.

On our servers

A row we cannot open

metric_typesleep
envelope_ida3f2…9e41
PFhMQx7kNQm2V0tZaHJmU1pxcm9YS2xEZ3VIMFJ5TndCZTRQcEF6
OWhLdEYyWXNWbjdMd0pjM1F4RzhlUmJUdk04aVVvRDVhSk5mS3cxc0
hZdHA2WjNCbVE5ckxlRjBqVndYUzdnTmlLNGNBUHVaMHlCMnRNSDZS
ZERxbFhXOXZFc0piTjNrVDVhWXBHOG1Rd0YxaHJVYzdMSjRvUzJ4Sz
lCdk5tWTZFZ1QwYVIzUGxIOHdEdUk1ZktjWnROOXFWMXhCb0o3ckd3
UzRhTTBlUDZoWWtDdkwyblQ4ZFJxRjNVSjVCeEkwd05tOWFHb1Y3S3
BlYzRTdEgxUmZNMnlEbkI2WjBqVXhBdzhxTDVrVDNjRzlwVjJOaFJl
NElzWTdCb0Ywd0RhTTFxSjhnVWtQM3ZUNlpjeFJuSDJMNWVCOXRXMF
lhRjdTb2pWNHJNa0kxdUcwUDhOZEIzY1h6UTZUNXdMZUYyaHBZOW1S
YTRLakJ2TjBvVThJc1cxcXhEM2ZHNWVUN2NNMlJoWjlMYUo0eUJ2UD
ZrTjBVd0YxbVNvOGdJN3JYdEUyY0Q1SlFhSDNiWTZ3TjBWOXBMZktU

Ciphertext plus routing metadata. No key is stored beside it, and none exists on our side to fetch.

Your own devices, a machine you explicitly paired, and a partner for the categories they chose can open the left-hand column. That list has never included us.

Designed for privacy

Your health data belongs to you and the people you choose

No cloud accounts. No plain text. A strict boundary between what is shared and what stays on your wrist.

01

Zero-knowledge by design

Curve25519 end-to-end encryption. We route your encrypted metrics and store them; we hold no key and no way to make one. That is a property of the architecture, not a promise in a policy.

02

The intelligence is yours

No model runs in our cloud, and none runs in the app. Your agent does the thinking, on hardware you own, with data it decrypts locally via the Vaultbeat MCP server.

03

Strict boundaries

Sharing is a switch, not a setting. Everything else is personal-only and cannot be shared by anyone.

Never Shared

  • Activity rings
  • Resting heart rate
  • Workouts
  • Mindfulness
  • Wrist temperature
  • VO₂ max

Shareable (Opt-in)

  • Sleep
    duration, stages, and that night’s heart-rate and breathing
  • Cycle
    off by default — the most sensitive switch on the page
  • Water
    daily intake
  • Weight
    trend over time

Connect in seconds

Requires the Vaultbeat iOS app. Pair your machine in its MCP tab → Connect an AI server (app 1.2.8 and earlier: Settings → Data & AI).

Add to Claude Code
claude mcp add vaultbeat-health -- \
  uvx vaultbeat-apple-health@latest serve \
  --transport stdio

Pricing

What does Vaultbeat cost?

Recording your health on your phone is free, forever. A membership keeps your history in the cloud for your own AI. With either of you a member, you and your partner each see the other's data, sleep included. For your AI to read your health data over MCP, you need a membership. Pairing a machine starts three days of full agent access.

Free

$0forever

Everything Apple Health records, kept on your iPhone. Nothing goes to the cloud.

  • Record everything Apple Health gives you
  • Pair with a partner — sharing needs a membership on either side
  • Connect an AI agent — three days of full access
  • End-to-end encrypted, on every plan
For AI agent users

Pro

$9.99/month

or $29.99/year · $74.99 once, forever

Keeps the agent interface going after your three free days — Claude Code, Hermes, OpenClaw.

  • Everything in Free
  • Continued MCP access for your own agent
  • Your full history, not just recent days
  • Trend charts across every metric
  • Lifetime option — no subscription at all
Download Vaultbeat — Health MCP for AI

Requires iOS. With either of you a member, you and your partner see each other's data.

How the Apple Health MCP server works with Claude Code