Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
OwnMetrics 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.
100/100
trust score
7
downloads a day
local
runs on your machine
145
downloads in 30d
What it does
Ask AI apps about your own Garmin data via Garmin's official Personal API. Unofficial.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user ownmetrics-mcp '--' uvx ownmetrics-mcp
# 2 — ask your agent for something these tools do
# get_daily_overview, get_sleep, get_hrv and 11 more
OwnMetrics costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BAAll 1 server
badisbenhamida1 server
1 category
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 OwnMetrics 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 uv (docs.astral.sh/uv): uvx 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 ownmetrics-mcp '--' uvx ownmetrics-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 asks of you
Nothing is required, but it can take GARMIN_PERSONAL_API_KEY (Optional. Your Garmin Personal API key; otherwise run `ownmetrics-mcp auth` once to save it.) if you want to set it.
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
14 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.
T1. One day's overview: steps, distance, floors, resting/min/max heart rate, stress, Body Battery, calories, intensity minutes, sleep hours and sleep score. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | yes | — |
T2. Sleep per night over a date range: hours, deep/light/REM/awake minutes, sleep score, Garmin's feedback, average heart rate, respiration and sleep stress. Each night is labelled woke_up_on, the morning it ended. Results are informational, not medical advice. Fields Garmin did not record say…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | yes | — | |
| end | yes | — |
T3. Heart rate variability (HRV) per night over a date range: last-night average, weekly average, 5-minute high, status and personal baseline, in milliseconds. Each night is labelled woke_up_on, the morning it ended. Results are informational, not medical advice. Fields Garmin did not record say…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | yes | — | |
| end | yes | — |
T4. Per day over a date range: average stress (0-100), minutes in each stress band, and Body Battery high, low, charged and drained. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | yes | — | |
| end | yes | — |
T5. One day's heart rate (resting, min, max, 7-day resting average) and the user's heart rate zones. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | yes | — |
T6. List activities in a date range, newest first, optionally filtered by Garmin activity type key (e.g. running, cycling, indoor_cycling, lap_swimming, strength_training). Returns ids for get_activity. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded';…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | yes | — | |
| end | yes | — | |
| activity_type | string | no | Optional Garmin activity type key, e.g. 'running'. |
| limit | integer | no | Maximum activities, 1-100. |
T7. Details of one activity by id: duration, distance, pace, speed, heart rate, power, cadence, training effect and load, splits and structured workout steps. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | integer | yes | Activity id from list_activities. |
T8. Body metrics over a date range: weigh-ins (kg), BMI, body fat, hydration; plus Pulse Ox (SpO2) and fitness age as of the end date. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them as zero.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | yes | — | |
| end | yes | — |
T9. Check the Garmin connection: whether the key works, granted scopes, a warning if the key expires within a day, which data areas respond, and what Garmin does not provide. Use this first when something fails. Results are informational, not medical advice. Fields Garmin did not record say 'not…
Takes no parameters.
I1. Training totals over up to 366 days, by week or month: sessions, hours, hours per week, evening sessions, average aerobic training effect, and a per-sport breakdown. Use for 'how much did I train' questions. Results are informational, not medical advice. Fields Garmin did not record say 'not…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | yes | — | |
| end | yes | — | |
| group_by | string | no | Group by 'week' or 'month'. |
I2. Compare two periods (each up to 366 days), e.g. this October vs last October: average sleep, HRV, resting heart rate, stress, Body Battery, steps and training per week, with change and % change and how many days of data each side has. Results are informational, not medical advice. Fields…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| a_start | string | yes | Period A first date, YYYY-MM-DD. |
| a_end | string | yes | Period A last date, YYYY-MM-DD. |
| b_start | string | yes | Period B first date, YYYY-MM-DD. |
| b_end | string | yes | Period B last date, YYYY-MM-DD. |
| metrics | array | no | Metrics to compare; leave empty for all. |
I3. Does training go with better or worse sleep and HRV? Over up to 366 days, pairs each day's training with the night after it: correlations with sample size and strength, plus averages for training vs rest days and evening vs earlier sessions. Can focus on one sport. Correlation is not cause;…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | yes | — | |
| end | yes | — | |
| activity_type | string | no | Optional sport to look at on its own, matched by name (e.g. 'tennis', 'running', 'cycling'). Days with only other sports are left out. |
I4. Trend of one metric over up to 366 days, by day, week or month: the series, change per 30 days and whether it is going up, down or flat. Daily grouping adds a 7-day rolling average. Results are informational, not medical advice. Fields Garmin did not record say 'not recorded'; never treat them…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metric | yes | The metric to follow. | |
| start | yes | — | |
| end | yes | — | |
| group_by | string | no | Group by day, week or month. |
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 OwnMetrics 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 100 / 100
Release 0.3.1 · scanned 28 Oct 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 score100
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest54fcca8a9b344c41bf9b57a143e7b9928ed1b479c99cb53c36dd4dcce87b4987
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| 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 (14 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>".
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.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_daily_overview | no tags | |
| get_sleep | no tags | |
| get_hrv | no tags | |
| get_stress_and_body_battery | no tags | |
| get_heart_rate | no tags | |
| list_activities | no tags | |
| get_activity | no tags | |
| get_body_metrics | no tags | |
| get_account_status | no tags | |
| training_summary | no tags | |
| compare_periods | no tags | |
| recovery_correlations | no tags | |
| trend | no tags | |
| weekly_review | 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 digest54fcca8a9b344c41
Scanned2026-10-28
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.3.1. Pin a release below and the command asks for exactly that one.
0.3.1
28 Oct 2026
latestNo release note was published with this version.
0.2.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 OwnMetrics 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.