Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Runspector 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.
90/100
trust score
3
downloads a day
local
runs on your machine
216
downloads in 30d
What it does
Local-first AI running coach for Garmin: readiness, VO2max, 80/20, workouts on your watch
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user runspector-mcp '--' uvx runspector mcp
# 2 — ask your agent for something these tools do
# get_athlete_profile, get_coaching_reference, get_training_readiness and 15 more
Runspector costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
EDAll 1 server
edxleon1 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 Runspector 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 runspector-mcp '--' uvx runspector 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
18 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.
What the app has learned about THIS athlete from their own data, each with its evidence: how many days they run and on which weekdays, their long-run day, a weekly other sport, how consistent they are, their intensity pattern over 28 days, the VO2max trend and whether a measurement is due,…
Takes no parameters.
The coach's full rule set: how to read the data, today's decision, the planning rules, zones and intensity distribution, the energy boundary and the sources behind each threshold - the same text the app's own coach works from. Call it ONCE per conversation, before the first training advice, and…
Takes no parameters.
Today's readiness verdict GO / EASY / REST with the signals behind it (HRV status, sleep score, Body Battery, resting HR vs 27-day baseline, ACWR, days since the last hard workout). Rule-based and conservative. START HERE for "should I train today?". Carries the app's own decision for today and,…
Takes no parameters.
Averages of sleep, HRV, resting HR, stress, Body Battery and steps over the last N days plus a snapshot of the latest day. Use for "how has my recovery been?". Aggregates only — never a day-by-day list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period_days | integer | no | Window length in days. |
Every recorded recovery value for ONE day (default: latest day with data).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| day | no | — |
Weekly averages of ONE recovery metric over the last N days — for "is my HRV / resting HR / sleep trending up or down?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metric | yes | — | |
| period_days | integer | no | Window length in days. |
Training-load picture: ACWR with its SOURCE (Garmin's EWMA ratio, or a self-computed fallback that is less reliable), Garmin training status, VO2max with change, and weekly load buckets. VO2max change is only reported when the value actually varied (Garmin carries the last value forward).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period_days | integer | no | Window length in days. |
Workout digest: totals per sport plus the latest workouts, each run classified Quality / Long Run / Easy (from training effect and duration). Use to see what was actually trained before recommending the next session.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period_days | integer | no | Window length in days. |
Time in heart-rate zones across all runs (easy Z1-2 / moderate Z3 / hard Z4-5 / Z5) with percentages — the basis for the 80/20 polarisation question.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period_days | integer | no | Window length in days. |
Deep dive into ONE run: time in each HR zone, interval structure (rep count, rep length, work vs recovery HR), weather, performance condition, plus rule-based notes. Default: the latest run with detail. The interval structure is Garmin's auto-detection — if the athlete states a different…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| day | no | — | |
| activity_id | integer | no | Garmin activity id; wins over day. |
VO2max over the last 8 weeks as STEPS (only the days the value really changed — Garmin carries it forward in between) plus a descriptive comparison of the last 28 days with the 28 before (distance, Z5 minutes, easy share, temperature). Use for "why is my VO2max moving?". Descriptive, not causal.
Takes no parameters.
Pull the latest days and workouts from Garmin Connect NOW. Call this first when today's run or last night's sleep is missing. Takes 10-40 s. Read-only towards Garmin; writes only to the local database.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | How many days back to re-fetch. |
Build a structured session for the athlete's route or time budget and file it as a PROPOSAL - warm-up, work reps with targets, recovery jogs, cool-down - sized so the whole thing adds up to the route. Targets come from the athlete's own Garmin zones; anything not measured is listed as an assumption.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | yes | — | |
| distance_km | number | no | Route length in km, e.g. 10 for a fixed 10 km loop. Give this OR duration_min. |
| duration_min | integer | no | Session length in minutes. Give this OR distance_km. |
| day | no | — | |
| name | string | no | Workout name on the watch. Default: kind and structure, e.g. 'VO2max 4x4 min'. |
| replaces_schedule_id | integer | no | A calendar entry this session REPLACES (the number after 'schedule' in get_training_readiness). Applying unschedules it first; the workout stays in the library. Use for the readiness swap: an easy run |
Build a polarised training week and file it as ONE proposal: a VO2max session and a threshold session 48 h apart, the long run on its weekday, easy runs between, nothing hard the day before or after the long run, at least one rest day. The sessions go on the days the athlete usually runs, and the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_day | string | no | First day of the week to plan, YYYY-MM-DD, today or up to 8 days ahead. Default: the coming Monday (today, if today is Monday). |
| days_per_week | integer | no | Running days. Default: the athlete's profile, else their history (the days they usually run), else 4 - the last two listed as an assumption. |
| long_run_day | string | no | Weekday of the long run. Default: the profile, else the weekday of their usual long run, else sun - the last two listed as an assumption. |
WRITE a proposed session to the athlete's Garmin account: upload the workout, schedule it on the proposal's day, push it to the watch, then read it back and verify structure and targets. Call ONLY after the athlete has seen the preview and explicitly agreed - a request ("plan me 10 km") is not…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| proposal_id | string | yes | The id propose_workout returned. |
Take a session (or a whole applied week) back OFF the athlete's Garmin calendar. The counterpart of apply_workout: use it when the athlete says the session should not be there after all, or after trying the write path out. It unschedules - the workout stays in their Garmin library, so applying the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| proposal_id | string | yes | The id of a proposal that was applied. |
No parameter schema on file.
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 Runspector 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 90 / 100
Release 0.10.0 · scanned 3 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 score96
Client score90
Findings12 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest097295ac152cbc79d97cae3ae701c08bc724bc57899863773ed2cbbbfe01642c
Score vectorthreat 96 → client 90
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| 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 (18 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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_athlete_profile | no tags | |
| get_coaching_reference | no tags | |
| get_training_readiness | no tags | |
| get_recovery_summary | no tags | |
| get_daily_metrics | no tags | |
| get_trend | no tags | |
| get_training_load | no tags | |
| get_recent_activities | no tags | |
| get_intensity_distribution | no tags | |
| analyze_workout | no tags | |
| get_vo2max_history | no tags | |
| sync_garmin | no tags | |
| propose_workout | no tags | |
| propose_week | no tags | |
| propose_change | no tags | |
| apply_workout | no tags | |
| undo_workout | no tags | |
| check_in | 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 digest097295ac152cbc79
Scanned2026-11-03
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.10.0. Pin a release below and the command asks for exactly that one.
0.10.0
2 Nov 2026
latestNo release note was published with this version.
0.8.0
1 Nov 2026
No release note was published with this version.
0.7.0
1 Nov 2026
No release note was published with this version.
0.6.0
31 Oct 2026
No release note was published with this version.
0.5.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 Runspector 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.