Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Healthfolder is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
13
tools declared
local
runs on your machine
—
downloads a day
What it does
Read a Health Access folder of Apple Watch workouts and vitals; write training plans back as files.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user healthfolder-mcp '--' npx -y @reneturcios/healthfolder mcp
# 2 — ask your agent for something these tools do
# list_workouts, get_workout, get_vitals and 10 more
Healthfolder costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 381 servers
CloudCorpRecords381 servers
28 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Healthfolder as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user healthfolder-mcp '--' npx -y @reneturcios/healthfolder mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List workouts from the Health Access folder, newest first, with a one-line summary each. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum rows to return (default 20) |
| since | string | no | Only workouts starting on or after this date (YYYY-MM-DD) or RFC 3339 timestamp |
| sport | string | no | Activity filter: pool_swim, indoor_row, cycle, walk, run, ... (swim matches both swim kinds) |
Open one workout in full: the workout document plus summary, parts text and cardiac cost. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Workout id: the full HealthKit UUID, its first 8 characters, or the file name |
| include_hr_series | boolean | no | Include the heart-rate series (default false) |
| include_laps | boolean | no | Include laps (default true) |
The seven-metric vitals view (resting HR, HRV, body mass, sleep, steps, VO2max, blood pressure) of the last N days, oldest first, with latest values and averages. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | How many days back to read (default 30) |
Training summary: one entry per ISO week ending in the current week, empty weeks included. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| weeks | integer | no | How many weeks to cover (default 8) |
Store the athlete's own effort rating (1 to 10) and optional feel note in a workout file. Call only with a number the athlete said; an existing Apple rating is refused unless override is true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| effort | number | yes | The effort rating the athlete stated, 1 to 10 |
| feel | string | no | Optional free-text note from the athlete |
| id | string | yes | Workout id: the full HealthKit UUID, its first 8 characters, or the file name |
| override | boolean | no | Replace an existing Apple rating when the athlete asks to change it (default false) |
Validate a healthaccess.plan.v1 training plan and write it into the folder's plans/ directory for the app to put on the Watch. Every validation violation is reported in one message.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | object | yes | The plan object: name, sport, optional warmup/cooldown, and at least one block of steps |
Read a plan's status as the app recorded it: pending, scheduled, failed or cancelled. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The plan id returned by push_plan |
List every plan in the folder's plans/ directory with its state, planned distance and time, newest first. Read-only.
No parameter schema on file.
Read one day file (days/<date>.json) with every Health group it holds. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | The day to read, YYYY-MM-DD |
Read the day files in a date range (at most 366 days), oldest first, optionally reduced to named groups. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | First day of the range, YYYY-MM-DD |
| groups | array | no | Optional list of groups to keep in each day |
| to | string | yes | Last day of the range, YYYY-MM-DD |
Read catalog.json (which Health types have data and where they were exported) plus the export-coverage check. Read-only.
No parameter schema on file.
Read profile.json: age, birth year, sex, blood type and the app's other profile fields. Read-only.
No parameter schema on file.
List every ECG file in the folder's ecg/ directory, newest first. Read-only.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Healthfolder or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.0 · scanned 6 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest6825dd4820267b61b62ba048872e574fb2cf92ce0e4f6ac7685ca0593d6cec31
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
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>".
13 of the 13 recovered tools are registered only when first === "mcp" || argv[argv.length - 1] === "mcp" holds (dist/cli.js:109) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
No tool is registered unconditionally · 13 only when first === "mcp" || argv[argv.length - 1] === "mcp" holds (dist/cli.js:109) — typically when a key or option is configured. All 13 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_workouts conditional | no tags | |
| get_workout conditional | no tags | |
| get_vitals conditional | no tags | |
| training_summary conditional | no tags | |
| rate_workout conditional | no tags | |
| push_plan conditional | no tags | |
| get_plan_status conditional | no tags | |
| list_plans conditional | no tags | |
| get_day conditional | no tags | |
| get_days conditional | no tags | |
| get_catalog conditional | no tags | |
| get_profile conditional | no tags | |
| list_ecgs conditional | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest6825dd4820267b61
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Healthfolder can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.