Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
goblingains 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.
93/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Conditioning workouts from a coached library: suggest, vary or invent one for your kit and time.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http goblingains-mcp https://api.goblingains.com/mcp
# 2 — ask your agent for something these tools do
# list_archetypes, list_equipment, find_movements and 4 more
goblingains costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GOAll 1 server
goblingains1 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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http goblingains-mcp https://api.goblingains.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: 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 pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 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.
The workout archetypes the generator makes, one per line: key, name, formats, minutes, line count, and the session slots it serves.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| style | no | Keep only one style's archetypes: crossfit, hyrox or hybrid; all when omitted. Example: "hyrox". |
The equipment suggest_workouts' equipment takes, one per line: key: name, with "(machine)" on ergometers (rower, ski erg, bikes). Keys, names and common names ("echo", "row erg", "DB", "kb") all work.
No parameter schema on file.
Movement slugs whose name holds query (e.g. "row", "sled"), for suggest_workouts' include and exclude, machines and runs first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Text the movement name holds, any case. Example: "sled". |
| kind | no | Keep one movement kind only, one of strength, olympic, plyo, cyclic, carry, mobility (cyclic: row, ski, bike, run); all when omitted. Example: "cyclic". |
New workouts from our generator, as text. Ask this instead of writing workouts yourself. Nothing is saved. Example, two people with an echo bike, rower and ski erg, 40-60 min: suggest_workouts(count=5, people=2, minutes_min=40, minutes_max=60, equipment=["echo-bike", "row-ergometer", "ski-erg"], bodyweight=False) A shortfall says what blocked it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| archetype | no | A key or name from list_archetypes; any when omitted. Example: "A5" or "chipper". | |
| count | integer | no | How many workouts, at most 5; from 3 on, a mix of archetypes (at most 2 of one unless nothing else fits). Example: 3. |
| include | no | Movement slugs or names (from find_movements) every workout must hold. Example: ["wallballs", "sled-push"]. | |
| only | boolean | no | True: the workouts hold the included movements and nothing else (each may repeat). Needs include. Example: true. |
| exclude | no | Movement slugs or names (from find_movements) every workout must leave out. Example: ["burpees"]. | |
| minutes_min | no | Shortest estimated workout length, in minutes. Example: 40. | |
| minutes_max | no | Longest estimated workout length, in minutes. Example: 60. | |
| cap_minutes | no | A time cap the workout must fit, in whole minutes. Example: 30. | |
| partner | no | True: only partner workouts (two people share the work: turns at a station, or each on a station at once, then swap). False: none. Omitted: either. Example: true. | |
| equipment | no | What the athletes have, as list_equipment keys or names ("echo-bike" or "echo", "row erg", "ski erg"), one item per entry. Say "1 dumbbell" or "1 kettlebell" when there is only one: movements needing | |
| bodyweight | boolean | no | False also leaves out movements needing no equipment (burpees, runs), so only the listed equipment is used. Example: false. |
| people | integer | no | How many train together with one of each machine. Above 1, only workouts they can share come back: partner workouts (taking turns on a station), or EMOMs/intervals with a different machine on every li |
| temperature | number | no | 0 to 1. 0: the same ask always brings the same workouts. Above 0: other ones each call, the higher the further from the library workouts they vary (0.3 close variations, 1 far ones). Example: 0.3. |
| sex | no | Who trains, for the weights and machine doses: "men", "women", or "mixed" (a man and a woman together: each at their own; Hyrox stations at the mixed doubles race load). Omitted when the user did not | |
| show_scores | boolean | no | True adds a line of scores under each workout: feasibility (0-100, can it be done as written), difficulty (0-100, the chance of not finishing inside the cap), and against the workout it was made from: |
Variations of one library workout from our generator (no AI), as text, in its own format or another. Nothing is saved. A shortfall says what blocked it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The library workout's name or part of it, any case; several matches are an error listing them (up to 10) to ask again. Example: "Fran". |
| count | integer | no | How many variations, at most 5. Example: 3. |
| temperature | number | no | 0 to 1, how far they stray from it (0.2 close, 1 far). Example: 0.5. |
| equipment | no | What the athletes have, as list_equipment keys or names ("echo-bike" or "echo", "row erg", "ski erg"), one item per entry. Say "1 dumbbell" or "1 kettlebell" when there is only one: movements needing | |
| bodyweight | boolean | no | False also leaves out movements needing no equipment (burpees, runs), so only the listed equipment is used. Example: false. |
| people | integer | no | How many train together with one of each machine. Above 1, only workouts they can share come back: partner workouts (taking turns on a station), or EMOMs/intervals with a different machine on every li |
| sex | no | Who trains, for the weights and machine doses: "men", "women", or "mixed" (a man and a woman together: each at their own; Hyrox stations at the mixed doubles race load). Omitted when the user did not | |
| format | no | Turn it into this format first: for_time, amrap, emom, intervals. About its minutes: an EMOM gives each line its own minute when a round is over 40 s, intervals rest as long as a round's work. Omitted | |
| show_scores | boolean | no | True adds a line of scores under each workout: feasibility (0-100, can it be done as written), difficulty (0-100, the chance of not finishing inside the cap), and against the workout it was made from: |
New workouts unlike any in the library, from our generator (no AI), as text: evolved from the library's workouts and movements (more lines, fewer, other formats) into kinds it does not hold. For one person. Nothing is saved; other ones each call. suggest_workouts and vary_workout stay close to library workouts instead. A shortfall says what blocked it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| count | integer | no | How many workouts, at most 5. Example: 3. |
| format | no | Only this format: for_time, amrap, emom, intervals. Any when omitted. Example: "amrap". | |
| include | no | Movement slugs or names (from find_movements) every workout must hold; fewer come back the more are named. Example: ["wallballs"]. | |
| exclude | no | Movement slugs or names (from find_movements) every workout must leave out. Example: ["burpees"]. | |
| minutes_min | no | Shortest estimated workout length, in minutes. Example: 10. | |
| minutes_max | no | Longest estimated workout length, in minutes. Example: 25. | |
| equipment | no | What the athletes have, as list_equipment keys or names ("echo-bike" or "echo", "row erg", "ski erg"), one item per entry. Say "1 dumbbell" or "1 kettlebell" when there is only one: movements needing | |
| bodyweight | boolean | no | False also leaves out movements needing no equipment (burpees, runs), so only the listed equipment is used. Example: false. |
| sex | no | Who trains, for the weights and machine doses: "men", "women", or "mixed" (a man and a woman together: each at their own; Hyrox stations at the mixed doubles race load). Omitted when the user did not | |
| show_scores | boolean | no | True adds a line of scores under each workout: feasibility (0-100, can it be done as written), difficulty (0-100, the chance of not finishing inside the cap), and against the workout it was made from: |
Send Goblin Gains what the user thinks of a workout from these tools. Call it whenever the user points out a mistake (wrong equipment, a weight, a dose that cannot fit) or says a workout is bad or good: the words go to Goblin Gains, nothing else about the user does.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| note | string | yes | What the user said about the workout, in their words. Example: "Farmers carry needs two dumbbells; I said I have one." |
| verdict | string | yes | One of mistake, bad, good: "mistake" (something in it is wrong), "bad" (it works but is a poor workout), "good". Example: "mistake". |
| workout | no | The workout's save link from suggest_workouts, vary_workout or generate_workouts, or its id; omitted for the tools as a whole. Example: "https://app.goblingains.com/w/<id>". |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 goblingains 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: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 2 Nov 2026
Graded from the tools this server lists, not from its source code.
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 score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest140c96bd697c6da1d855235ceafd96fcc21453d17d18a2254894973ed286af08
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_archetypes | no tags | |
| list_equipment | no tags | |
| find_movements | no tags | |
| suggest_workouts | no tags | |
| vary_workout | no tags | |
| generate_workouts | no tags | |
| report_workout | state-write | state-write: declares readOnlyHint: false |
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 digest140c96bd697c6da1
Scanned2026-11-02
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.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 goblingains 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.