Apple Health
ReviewAudited by ClawScan on May 1, 2026.
Overview
This skill is coherent and privacy-conscious, but it will run a third-party Apple Health MCP package on your local health export and save local setup/query notes.
Before installing, make sure you trust the third-party Apple Health MCP package and the MCP client you will connect it to. Point HEALTH_DATA_DIR only at the specific export folder you want analyzed, prefer bounded queries, and periodically review or delete the local ~/apple-health/ memory if it contains sensitive summaries.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The npm package will execute locally and is expected to access the Apple Health export directory.
The skill directs users to run a third-party npm MCP server, without a pinned package version, as the main integration mechanism.
"command": "npx", "args": ["@neiltron/apple-health-mcp"]
Install only if you trust the MCP package; consider reviewing its source/provenance and pinning a known-good version where your client supports it.
Health summaries, export paths, and analysis notes may remain on disk and be reused in later sessions.
The skill stores persistent local memory, including query logs and summaries that may contain health-related context.
Memory lives in `~/apple-health/` ... `query-log.md` # Reusable SQL/report prompts and known-good outputs
Keep stored notes minimal, avoid saving raw records, and delete or redact ~/apple-health/ if you no longer want the agent to retain this context.
Sensitive health results may be visible to whichever MCP-compatible client or agent workspace you connect.
Health data is accessed through an MCP client/server flow, so query outputs can enter the connected client or agent conversation context.
Then confirm the MCP client ... Run `health_schema` ... Run one bounded query from `query-recipes.md`
Use only trusted MCP clients and avoid connecting this server in shared or untrusted workspaces unless you are comfortable exposing health summaries there.