IronLedger strength calculators
REMOTE · WWW.IRONLEDGER.APP
Free strength-training calculators, plus a checker for program files you import into IronLedger.
Available components
Last scanned (1 hour ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1369 tokens (~195/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.ironledger.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.ironledger.app | CN=YR1,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | RSA 2048 | SHA256-RSA | 65b64a9f6efb80780403ce933fb5248e479 |
| SANs: www.ironledger.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.ironledger.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| ironledger.app. | present | 2371 | 13 | Verified |
| www.ironledger.app. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://us-assets.i.posthog.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://www.google-analytics.com; font-src 'self'; connect-src 'self' https://us.i.posthog.com https://us-assets.i.posthog.com https://www.google-analytics.com https://*.google-analytics.com; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.ironledger.app/mcp | Verified | 200 | |
| http (plaintext) | http://www.ironledger.app/mcp | HTTPS enforced | 308 | https://www.ironledger.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_program_file IronLedger program file checker ~252
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 to import into IronLedger, and fix anything it reports first. The app names the program after the file, so pass the file name you will give it.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 conta… |
| fileName | string | – | 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. |
No output schema declared.
No examples provided.
one_rep_max One-rep max calculator ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| formula | string | – | One-rep max formula: epley (weight × (1 + reps ÷ 30), the one the IronLedger app uses) or brzycki (weight × 36 ÷ (37 − reps)). |
| reps | integer | yes | Reps completed, 1 to 30. |
| unit | string | – | Weight unit for every load in and out: kg or lb. |
| weight | number | yes | Weight lifted for the set. |
No output schema declared.
No examples provided.
plate_loading Barbell plate calculator ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bar | number | – | Bar weight in the chosen unit. Defaults to 20 kg or 45 lb. |
| collarWeight | number | – | Weight of each collar. Defaults to 2.5 kg or 5 lb. |
| collars | boolean | – | Count a collar on each side. |
| plates | string | – | 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). |
| target | number | yes | Total weight wanted on the bar, including the bar. |
| unit | string | – | Weight unit for every load in and out: kg or lb. |
No output schema declared.
No examples provided.
powerlifting_score DOTS, IPF GL and Wilks calculator ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bodyweight | number | yes | Bodyweight in the chosen unit. |
| equipment | string | – | For IPF GL: raw (classic) or equipped. |
| event | string | – | For IPF GL: sbd (full powerlifting total) or bench (bench press only). |
| sex | string | yes | The formulas have separate male and female coefficients. |
| total | number | yes | Total lifted (squat + bench + deadlift), or the bench press for event "bench". |
| unit | string | – | Weight unit for every load in and out: kg or lb. |
No output schema declared.
No examples provided.
rpe_estimate_max Estimate one-rep max from a set and its RPE ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| formula | string | – | One-rep max formula: epley (weight × (1 + reps ÷ 30), the one the IronLedger app uses) or brzycki (weight × 36 ÷ (37 − reps)). |
| 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 | – | Weight unit for every load in and out: kg or lb. |
| weight | number | yes | Weight lifted for the set. |
No output schema declared.
No examples provided.
rpe_target_load Load for a target reps and RPE ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| formula | string | – | One-rep max formula: epley (weight × (1 + reps ÷ 30), the one the IronLedger app uses) or brzycki (weight × 36 ÷ (37 − reps)). |
| 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 | – | Weight unit for every load in and out: kg or lb. |
No output schema declared.
No examples provided.
warmup_sets Warm-up set calculator ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bar | number | – | Bar weight in the chosen unit. Defaults to 20 kg or 45 lb. |
| sets | integer | – | Number of warm-up sets, 1 to 12. |
| unit | string | – | Weight unit for every load in and out: kg or lb. |
| workingWeight | number | yes | The first working set’s weight. |
No output schema declared.
No examples provided.
How do I install the IronLedger strength calculators MCP server?
IronLedger strength calculators is a hosted endpoint at https://www.ironledger.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.ironledger.app
claude mcp add --transport http app-ironledger-strength-calculators 'https://www.ironledger.app/mcp'
What is the IronLedger strength calculators MCP server?
IronLedger strength calculators is an MCP server listed in the public MCP registry as app.ironledger/strength-calculators. Free strength-training calculators, plus a checker for program files you import into IronLedger. This page covers its hosted endpoint (https://www.ironledger.app/mcp).
Is the IronLedger strength calculators MCP server safe to use?
IronLedger strength calculators scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the IronLedger strength calculators MCP server expose?
IronLedger strength calculators exposes 7 tools: one_rep_max, rpe_estimate_max, rpe_target_load, plate_loading, warmup_sets, and 2 more. Their descriptions and schemas cost roughly 1,309 tokens of context every time the server is loaded.
Does the IronLedger strength calculators MCP server require authentication?
No. We connected to IronLedger strength calculators without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the IronLedger strength calculators MCP server still maintained?
IronLedger strength calculators is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.