io.github.dorian-K/alpha-progression-mcp
PYPI · ALPHA-PROGRESSION-MCP
Analyse your Alpha Progression gym training and adjust your plan.
Available components
Last scanned (1 hour ago)
Scores higher than 66% of PyPI servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1481 tokens (~113/item across 13 items; 13 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (38% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 66
First indexed and scored.
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 · Analysed pypi/alpha-progression-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_plan_exercise ~134
Add one exercise to a day of the training plan, at the end or right after the exercise named in `after`. Example: day="Day 2", exercise="Seated Leg Curls (machine)", sets=3, reps=10, after="Deadlifts". Returns a preview; nothing is saved unless apply=true (only after the user approved the preview).
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| apply | boolean | – | – |
| day | string | yes | – |
| exercise | string | yes | – |
| plan | string | – | – |
| reps | integer | yes | – |
| sets | integer | yes | – |
No output schema declared.
No examples provided.
find_exercises ~76
Search exercises by name and/or muscle or group (e.g. "chest", "quads", "legs"), most recently done first. By default only exercises the user has done, with how often and when last.
| Name | Type | Req | Description |
|---|---|---|---|
| muscle | string | – | – |
| only_used | boolean | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_document ~40
Any single stored document by id, for anything the other tools don't cover (e.g. "settings", "profile").
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | – |
No output schema declared.
No examples provided.
get_exercise_history ~117
One exercise over time: a summary plus one row per workout (newest first) with the top set, e1RM, working sets and volume. `exercise` is a name (partial names like "bench press" work if they are unambiguous) or an id. include_sets=true adds every set, including warm-ups.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | – |
| exercise | string | yes | – |
| include_sets | boolean | – | – |
| limit | integer | – | – |
| start_date | string | – | – |
No output schema declared.
No examples provided.
get_measurements ~28
Recorded body measurements (bodyweight, body fat, waist, ...) with dates, oldest first.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_plans ~50
Training plans: per day the exercises with their muscle and weekly set/rep/RIR targets. Only the current plan by default; active_only=false returns all plans.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_progress ~151
Which exercises are improving or stalled. Defaults to the last 6 months. Per exercise done at least `min_sessions` times: sessions, working sets per week, e1RM at the start and end of the range (median of the first and last 3 sessions, to smooth out single days), best e1RM, change in % and the last date. Unweighted exercises compare top-set reps instead. Sorted by muscle group. Filter with `muscle` or a group (chest, back, shoulders, arms, legs, core).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | – |
| min_sessions | integer | – | – |
| muscle | string | – | – |
| start_date | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_session ~42
One workout with every set: weight, unit, reps, RIR (reps in reserve), duration, notes and targets.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
get_sessions ~127
Performed workouts as compact summaries, newest first. Per workout: name, plan, start, duration, working sets, volume (kg x reps), and per exercise the muscle, working sets, top set and e1RM. `skipped` lists exercises that were planned but not done; `mobility` lists stretches (not counted as training). Dates are YYYY-MM-DD, inclusive. Cached 5 min; refresh=true reloads.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | – |
| limit | integer | – | – |
| refresh | boolean | – | – |
| start_date | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_weekly_training ~183
Weekly training load, the main input for volume and frequency guidance. Defaults to the last 8 weeks. Per week (Monday start): workouts, minutes, working sets, and per muscle the fractional working sets (1 per set for the target muscle, 0.5 for its main secondary muscles) and frequency (days trained). `average_per_week` gives the same per muscle averaged over the range, with its muscle group. Weeks without any workout (holiday, illness) are left out of the average unless skip_empty_weeks=false. Filter with `muscle` (e.g. "chest") or a group: chest, back, shoulders, arms, legs, core.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | – |
| muscle | string | – | – |
| skip_empty_weeks | boolean | – | – |
| start_date | string | – | – |
No output schema declared.
No examples provided.
remove_plan_exercise ~93
Take one exercise off a day of the training plan. Past workouts with it stay in the history. Example: day="Day 2", exercise="Overhead Triceps Extensions". Returns a preview; nothing is saved unless apply=true (only after the user approved the preview).
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | – | – |
| day | string | yes | – |
| exercise | string | yes | – |
| plan | string | – | – |
No output schema declared.
No examples provided.
set_plan_targets ~112
Change the target sets and/or reps of one exercise in the training plan. Example: day="Day 1", exercise="Bench Press", sets=4, reps=6. `day` is a day name or number. Returns a preview; nothing is saved unless apply=true (only after the user approved the preview).
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | – | – |
| day | string | yes | – |
| exercise | string | yes | – |
| plan | string | – | – |
| reps | – | – | – |
| sets | – | – | – |
No output schema declared.
No examples provided.
swap_plan_exercise ~130
Replace one exercise on a day of the training plan with another, keeping its targets unless sets/reps are given. Example: day="Day 2", exercise="Overhead Triceps Extensions", new_exercise="Dips", sets=3, reps=8. Returns a preview; nothing is saved unless apply=true (only after the user approved the preview).
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | – | – |
| day | string | yes | – |
| exercise | string | yes | – |
| new_exercise | string | yes | – |
| plan | string | – | – |
| reps | – | – | – |
| sets | – | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.dorian-K/alpha-progression-mcp server?
io.github.dorian-K/alpha-progression-mcp runs locally as a PyPI package, launched with uvx alpha-progression-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · alpha-progression-mcp
claude mcp add dorian-k-alpha-progression-mcp -- uvx alpha-progression-mcp
What is the io.github.dorian-K/alpha-progression-mcp server?
io.github.dorian-K/alpha-progression-mcp is listed in the public MCP registry as io.github.dorian-K/alpha-progression-mcp. Analyse your Alpha Progression gym training and adjust your plan. This page covers its PyPI package (alpha-progression-mcp).
Is the io.github.dorian-K/alpha-progression-mcp server safe to use?
io.github.dorian-K/alpha-progression-mcp scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.dorian-K/alpha-progression-mcp server expose?
io.github.dorian-K/alpha-progression-mcp exposes 13 tools: get_sessions, get_session, get_weekly_training, get_progress, get_exercise_history, and 8 more. Their descriptions and schemas cost roughly 1,283 tokens of context every time the server is loaded.
Is the io.github.dorian-K/alpha-progression-mcp server still maintained?
io.github.dorian-K/alpha-progression-mcp 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.
What licence is the io.github.dorian-K/alpha-progression-mcp server under?
io.github.dorian-K/alpha-progression-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.