Apple Health (rinoshiyo) MCP Server
apple-health-mcp-server
PyPI
v0.6.1
Published by rinoshiyo — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Make Claude your personal health AI — locally.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Shell/command execution in packaging/dev tooling (tests/unit/server/test_server.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/server/test_server.py:168`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import sys proc = subprocess.run( [ sys.executable, "-c", "import sys,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/unit/server/test_server.py
Tools 13
Each tool and what it can reach — statically extracted from the published source.
get_activity_summariesno sensitive capabilityget_heart_rate_samplesno sensitive capabilityget_record_statisticsno sensitive capabilityget_server_infono sensitive capabilityget_workout_routeno sensitive capabilitylist_correlationsno sensitive capabilitylist_data_sourcesno sensitive capabilitylist_ecg_readingsno sensitive capabilitylist_record_typesno sensitive capabilitylist_state_of_mindno sensitive capability
Show 3 more tools ↓
list_workoutsno sensitive capabilityquery_recordsno sensitive capabilityrun_custom_queryno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (13 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.6.1 latest |
A 99/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan apple-health-mcp-server --online --registry pypiOther implementations of Apple Health 3
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
Apple Health MCP server — reads Health Auto Export CSVs
MCP server that lets LLMs query your Apple Health export via SQL
MCP server for querying Apple Health data with DuckDB
More in Lifestyle & Local
MCP server for Australian address search and validation via Addressr
Admissions data & match scores for law, medical, dental, MBA, pharmacy, vet, optometry schools
Live AI data for agents: model releases, regulations (EU AI Act), GenAI glossary, daily news.
AirTreks MCP Server — complex flight routing intelligence for AI agents. Plan multi-city trips, validate alliance routings, get carrier recommendations, and create trip ideas.
Physician-reviewed medical opinions and prescriptions for AI agents.
Thin MCP server + CLI that proxy the atrium /api/v1 observability surface using an oc_live_ Bearer key. Talks HTTP only — no Convex imports.