# io.github.dorian-K/alpha-progression-mcp (pypi · alpha-progression-mcp)

Analyse your Alpha Progression gym training and adjust your plan.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `alpha-progression-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dorian-k-alpha-progression-mcp/alpha-progression-mcp.md), [page](https://verifymcp.io/servers/dorian-k-alpha-progression-mcp/alpha-progression-mcp)

## Channel facts

- Registry: `pypi`
- Package: `alpha-progression-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (38% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add dorian-k-alpha-progression-mcp -- uvx alpha-progression-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dorian-k-alpha-progression-mcp": {
      "command": "uvx",
      "args": [
        "alpha-progression-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dorian-k-alpha-progression-mcp": {
      "command": "uvx",
      "args": [
        "alpha-progression-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dorian-k-alpha-progression-mcp -- uvx alpha-progression-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dorian-k-alpha-progression-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "alpha-progression-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dorian-k-alpha-progression-mcp --command uvx --arg alpha-progression-mcp
```

### Hermes

```yaml
mcp_servers:
  dorian-k-alpha-progression-mcp:
    command: "uvx"
    args: ["alpha-progression-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dorian-k-alpha-progression-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "alpha-progression-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dorian-k-alpha-progression-mcp -t stdio -c uvx -a alpha-progression-mcp
```

### Other

```json
{
  "mcpServers": {
    "dorian-k-alpha-progression-mcp": {
      "command": "uvx",
      "args": [
        "alpha-progression-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 70, +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.

### 2026-11-03 (score 69, +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.

### 2026-11-01 (score 68, +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.

### 2026-10-30 (score 67, +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.

### 2026-10-28 (score 66)

First indexed and scored.

## MCP tools (13)

### `get_sessions` (~127 tokens)

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.

Input parameters:

- `end_date` (string)
- `limit` (integer)
- `refresh` (boolean)
- `start_date` (string)

Output parameters:

- `result` (array)

### `get_session` (~42 tokens)

One workout with every set: weight, unit, reps, RIR (reps in reserve), duration, notes and targets.

Input parameters:

- `session_id` (string, required)

### `get_weekly_training` (~183 tokens)

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.

Input parameters:

- `end_date` (string)
- `muscle` (string)
- `skip_empty_weeks` (boolean)
- `start_date` (string)

### `get_progress` (~151 tokens)

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).

Input parameters:

- `end_date` (string)
- `min_sessions` (integer)
- `muscle` (string)
- `start_date` (string)

Output parameters:

- `result` (array)

### `get_exercise_history` (~117 tokens)

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.

Input parameters:

- `end_date` (string)
- `exercise` (string, required)
- `include_sets` (boolean)
- `limit` (integer)
- `start_date` (string)

### `find_exercises` (~76 tokens)

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.

Input parameters:

- `muscle` (string)
- `only_used` (boolean)
- `query` (string)

Output parameters:

- `result` (array)

### `get_plans` (~50 tokens)

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.

Input parameters:

- `active_only` (boolean)

Output parameters:

- `result` (array)

### `get_measurements` (~28 tokens)

Recorded body measurements (bodyweight, body fat, waist, ...) with dates, oldest first.

Output parameters:

- `result` (array)

### `get_document` (~40 tokens)

Any single stored document by id, for anything the other tools don't cover (e.g. "settings", "profile").

Input parameters:

- `doc_id` (string, required)

### `set_plan_targets` (~112 tokens)

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).

Input parameters:

- `apply` (boolean)
- `day` (string, required)
- `exercise` (string, required)
- `plan` (string)
- `reps`
- `sets`

### `add_plan_exercise` (~134 tokens)

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).

Input parameters:

- `after` (string)
- `apply` (boolean)
- `day` (string, required)
- `exercise` (string, required)
- `plan` (string)
- `reps` (integer, required)
- `sets` (integer, required)

### `swap_plan_exercise` (~130 tokens)

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).

Input parameters:

- `apply` (boolean)
- `day` (string, required)
- `exercise` (string, required)
- `new_exercise` (string, required)
- `plan` (string)
- `reps`
- `sets`

### `remove_plan_exercise` (~93 tokens)

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).

Input parameters:

- `apply` (boolean)
- `day` (string, required)
- `exercise` (string, required)
- `plan` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/dorian-k-alpha-progression-mcp/alpha-progression-mcp#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 69
- 2026-11-03: 69
- 2026-11-02: 68
- 2026-11-01: 68
- 2026-10-31: 67
- 2026-10-30: 67
- 2026-10-29: 66
- 2026-10-28: 66

## Common questions

### 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.

### What did VerifyMCP test on the io.github.dorian-K/alpha-progression-mcp server?

VerifyMCP ran 16 checks on io.github.dorian-K/alpha-progression-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/alpha-progression-mcp/
- Socket report: https://socket.dev/pypi/package/alpha-progression-mcp
- Repository: https://github.com/dorian-k/alpha-progression-mcp
- Changelog RSS feed: https://verifymcp.io/servers/dorian-k-alpha-progression-mcp/alpha-progression-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dorian-k-alpha-progression-mcp/alpha-progression-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dorian-k-alpha-progression-mcp/alpha-progression-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dorian-k-alpha-progression-mcp/alpha-progression-mcp