Health Bridge for AI runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 17 Sep 2026.
Apple Health AI Bridge provides read-only local MCP access for Health Bridge for AI.
We read the source, 22 h ago · rules 3dff92dd89df
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
completed = subprocess.run( # nosec B603 # noqa: S603
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
completed = subprocess.run( # nosec B603 # noqa: S603
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Health Bridge for AI and you get told the day something new turns up.
Read-only MCP access to a local append-only evidence ledger for AI agent sessions.
Read-only MCP server for licensed Healthpoint HL7 FHIR API access.
Read-only MCP access to your own Apple Health data, mirrored from the Marrow iOS app.
Read-only MCP access to the 1F4BC job board for AI agents.
Read-only DWG file access for AI clients through MCP.
Bounded local MCP access to one approved repository for AI read/search and structured handoffs.
Query 190 Apple Health metrics from any MCP agent: zero-dependency, read-only, local-first.
MCP server providing AI assistants with safe, read-only SQL Server access
Answers built from our own checks of this server.