# io.github.dropflyai/fitfly-engine (remote · workout-engine-production-5dd7.up.railway.app)

Deterministic fitness coaching engine: adaptive programs, progression math, readiness autoregulation

- Trust score: 64/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `workout-engine-production-5dd7.up.railway.app`: 64/100 (this document), [markdown](https://verifymcp.io/servers/dropflyai-fitfly-engine/workout-engine-production-5dd7.md), [page](https://verifymcp.io/servers/dropflyai-fitfly-engine/workout-engine-production-5dd7)

## Channel facts

- Endpoint: `https://workout-engine-production-5dd7.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.2.0`

## Trust breakdown

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

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 621 tokens (~62/item across 10 items; 10 tools + 0 resources), lean.
  - 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**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 35% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dropflyai-fitfly-engine https://workout-engine-production-5dd7.up.railway.app/mcp
```

### Codex

```toml
[mcp_servers.dropflyai-fitfly-engine]
url = "https://workout-engine-production-5dd7.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dropflyai-fitfly-engine": {
      "type": "remote",
      "url": "https://workout-engine-production-5dd7.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dropflyai-fitfly-engine --url https://workout-engine-production-5dd7.up.railway.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dropflyai-fitfly-engine:
    url: "https://workout-engine-production-5dd7.up.railway.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dropflyai-fitfly-engine": {
      "type": "http",
      "url": "https://workout-engine-production-5dd7.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-03 (score 64, +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-08-01 (score 63, +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-07-31 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 60, +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-07-27 (score 59, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (10)

### `get_todays_session` (~87 tokens)

Get today's training session

Today's workout: exercises, sets/reps, per-exercise load guidance and concrete target weights, plus nutrition targets and cycle status. Auto-applies the user's readiness check-in (autoregulation) if they've done one today. Call this to see what the athlete should do now.

Input parameters:

- `dayIndex` (integer): Which program day (1-based). Defaults to the first day.

### `readiness_checkin` (~108 tokens)

Log a readiness check-in

Record how the athlete feels today (energy, sleep, soreness — each 1–5). The engine scores readiness and, on the next get_todays_session, reshapes the workout accordingly (reduce volume / reduce intensity / recovery day). Returns the readiness score + modifier.

Input parameters:

- `energy` (integer, required): 1 drained … 5 great
- `sleep` (integer, required): 1 terrible … 5 great
- `soreness` (integer, required): 1 none … 5 very sore

### `log_workout` (~93 tokens)

Log completed sets

Record what the athlete actually lifted. The engine runs progression (double-progression, e1RM), detects PRs, and returns per-exercise outcomes (established/progressed/held/deloaded) with next-time targets. Weights are in kg.

Input parameters:

- `dayIndex` (integer)
- `exercises` (array, required): Per-exercise completed sets (weights in kg).
- `goal` (string)

### `list_swap_options` (~45 tokens)

List same-area swap options for an exercise

Valid alternatives for an exercise — same muscle group, filtered to the athlete's equipment/level/injuries. Use before swap_exercise.

Input parameters:

- `exerciseId` (string, required)

### `swap_exercise` (~81 tokens)

Swap an exercise

Replace an exercise with a valid same-area alternative. scope 'today' = just this session; scope 'program' = going forward. The new lift starts fresh (day-one calibration).

Input parameters:

- `dayIndex` (integer)
- `exerciseId` (string, required)
- `scope` (string): Default 'program'.
- `toExerciseId` (string, required)

### `get_program` (~19 tokens)

Get the active program

The athlete's current multi-day program (render-ready).

### `regenerate_program` (~32 tokens)

Regenerate the program

Rebuild the whole program from the stored profile (~20s AI generation). Use after a profile change or a plateau.

### `nutrition_targets` (~27 tokens)

Get nutrition targets

The athlete's daily calorie + macro targets, computed from body stats, activity, and goal.

### `meal_plan` (~73 tokens)

Generate a meal plan

A day of meals hitting the athlete's targets, USDA truth-checked (flags feasible=false with a note when macros are approximate). Slow (~15s AI call).

Input parameters:

- `dietaryStyle` (string)
- `exclusions` (array)
- `mealsPerDay` (integer)
- `trainingDay` (boolean)

### `changelog` (~56 tokens)

What the engine changed and why

The 'what changed & why' feed — the engine's coaching decisions (volume bumps, deloads, swaps) in Coach Fly's voice. Use to explain to the athlete why their plan evolved.

Input parameters:

- `limit` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dropflyai-fitfly-engine/workout-engine-production-5dd7#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 61
- 2026-07-29: 61
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 59

## Links

- Remote endpoint: https://workout-engine-production-5dd7.up.railway.app/mcp
- Authorisation metadata: https://workout-engine-production-5dd7.up.railway.app/.well-known/oauth-protected-resource/mcp
- Website: https://workout-engine-production-5dd7.up.railway.app/connect
- Changelog RSS feed: https://verifymcp.io/servers/dropflyai-fitfly-engine/workout-engine-production-5dd7/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dropflyai-fitfly-engine/workout-engine-production-5dd7/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dropflyai-fitfly-engine/workout-engine-production-5dd7