Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
IronLedger strength calculators 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.
What it does
Free strength-training calculators, plus a checker for program files you import into IronLedger.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ironledger-strength-calculators-mcp https://www.ironledger.app/mcp
# 2 — ask your agent for something these tools do
# one_rep_max, rpe_estimate_max, rpe_target_load and 4 more
IronLedger strength calculators costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 ironledger-strength-calculators-mcp https://www.ironledger.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
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.
Estimate a one-rep max (1RM) from a set of weight × reps, with a percentage table and the load each rep count should allow. Epley by default, Brzycki optional. Estimates above 10 reps are flagged as less reliable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| weight | number | yes | Weight lifted for the set. |
| reps | integer | yes | Reps completed, 1 to 30. |
| unit | string | no | Weight unit for every load in and out: kg or lb. |
| formula | string | no | One-rep max formula: epley (weight × (1 + reps ÷ 30), the one the IronLedger app uses) or brzycki (weight × 36 ÷ (37 − reps)). |
Estimate a one-rep max from weight, reps and RPE, treating RPE as reps in reserve (RPE 8 = 2 reps left) and applying the one-rep max formula to reps + reps in reserve.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| weight | number | yes | Weight lifted for the set. |
| reps | integer | yes | Reps completed, 1 to 20. |
| rpe | number | yes | Rating of perceived exertion, 5 to 10, read as reps in reserve (RPE 8 = 2 reps left). Half points allowed. |
| unit | string | no | Weight unit for every load in and out: kg or lb. |
| formula | string | no | One-rep max formula: epley (weight × (1 + reps ÷ 30), the one the IronLedger app uses) or brzycki (weight × 36 ÷ (37 − reps)). |
Find the load for a set of a given number of reps at a target RPE, from a known or estimated one-rep max. Rounded to the nearest 0.5.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| oneRepMax | number | yes | Your one-rep max (tested or estimated). |
| reps | integer | yes | Target reps, 1 to 20. |
| rpe | number | yes | Rating of perceived exertion, 5 to 10, read as reps in reserve (RPE 8 = 2 reps left). Half points allowed. |
| unit | string | no | Weight unit for every load in and out: kg or lb. |
| formula | string | no | One-rep max formula: epley (weight × (1 + reps ÷ 30), the one the IronLedger app uses) or brzycki (weight × 36 ÷ (37 − reps)). |
Work out which plates to put on each side of a barbell to reach a target weight, using standard gym plates or the plates you list. Reports the exact load and anything your plates can’t make.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | number | yes | Total weight wanted on the bar, including the bar. |
| unit | string | no | Weight unit for every load in and out: kg or lb. |
| bar | number | no | Bar weight in the chosen unit. Defaults to 20 kg or 45 lb. |
| collars | boolean | no | Count a collar on each side. |
| collarWeight | number | no | Weight of each collar. Defaults to 2.5 kg or 5 lb. |
| plates | string | no | Plates available, heaviest first or in any order: "25,20,15,10,5,2.5,1.25" for as many as needed, or "25:4,20:2" for pairs owned. Defaults to standard gym plates (kg: 25 to 1.25; lb: 45 to 2.5). |
Build a warm-up ramp to a working weight: plate-friendly jumps, reps falling from 10 to singles, with the plates for each set. The same ramp the IronLedger app suggests.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workingWeight | number | yes | The first working set’s weight. |
| sets | integer | no | Number of warm-up sets, 1 to 12. |
| unit | string | no | Weight unit for every load in and out: kg or lb. |
| bar | number | no | Bar weight in the chosen unit. Defaults to 20 kg or 45 lb. |
Score a powerlifting total (or a bench press) against bodyweight with DOTS, IPF GL points and the original Wilks, using the coefficients the OpenPowerlifting rankings use.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| total | number | yes | Total lifted (squat + bench + deadlift), or the bench press for event "bench". |
| bodyweight | number | yes | Bodyweight in the chosen unit. |
| unit | string | no | Weight unit for every load in and out: kg or lb. |
| sex | string | yes | The formulas have separate male and female coefficients. |
| equipment | string | no | For IPF GL: raw (classic) or equipped. |
| event | string | no | For IPF GL: sbd (full powerlifting total) or bench (bench press only). |
Check a training program written as a CSV or TSV file exactly as the IronLedger app will import it, before anyone loads it on a phone. Returns the weeks, sessions and exercises it creates, every skipped row and warning with its row number, the exercise names the app will question ("Did you mean ...?"), and names that will become new custom exercises. Use it whenever you write a program for someone
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file | string | yes | The whole program file as text. Canonical header: Week,Day,Exercise,Sets,Reps,Load,RPE,RIR,Rest,Notes, then one row per exercise, such as 1,Day 1,Squat,5,5,100 kg,8,,3:00,belt. Wrap a cell that contai |
| fileName | string | no | The file name it will be saved as, such as "Texas Method.csv". The app names the program after it; without one the program is called Imported Spreadsheet. |
- 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 IronLedger strength calculators or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| one_rep_max | no tags | |
| rpe_estimate_max | no tags | |
| rpe_target_load | no tags | |
| plate_loading | no tags | |
| warmup_sets | no tags | |
| powerlifting_score | no tags | |
| check_program_file | 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
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.1.0.
No release note was published with this version.
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.
Any signed-in account that does not publish IronLedger strength calculators can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.