# MTFIT Programming (remote · mtfit-mcp.mtfit-mcp.workers.dev)

Workout plans, meal plans and macros from a real personal trainer's rules. Pay per call with x402.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mtfit-mcp.mtfit-mcp.workers.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-mtfit-mcp-mtfit-mcp-programming/mtfit-mcp.md), [page](https://verifymcp.io/servers/dev-workers-mtfit-mcp-mtfit-mcp-programming/mtfit-mcp)

## Channel facts

- Endpoint: `https://mtfit-mcp.mtfit-mcp.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1521 tokens (~304/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 MTFIT Programming MCP server?

MTFIT Programming is a hosted endpoint at https://mtfit-mcp.mtfit-mcp.workers.dev/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.

### Claude

```bash
claude mcp add --transport http dev-workers-mtfit-mcp-mtfit-mcp-programming 'https://mtfit-mcp.mtfit-mcp.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-mtfit-mcp-mtfit-mcp-programming": {
      "url": "https://mtfit-mcp.mtfit-mcp.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-mtfit-mcp-mtfit-mcp-programming": {
      "type": "http",
      "url": "https://mtfit-mcp.mtfit-mcp.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-mtfit-mcp-mtfit-mcp-programming]
url = "https://mtfit-mcp.mtfit-mcp.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-mtfit-mcp-mtfit-mcp-programming": {
      "type": "remote",
      "url": "https://mtfit-mcp.mtfit-mcp.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-mtfit-mcp-mtfit-mcp-programming --url 'https://mtfit-mcp.mtfit-mcp.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-mtfit-mcp-mtfit-mcp-programming:
    url: "https://mtfit-mcp.mtfit-mcp.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-mtfit-mcp-mtfit-mcp-programming": {
      "Transport": "http",
      "Url": "https://mtfit-mcp.mtfit-mcp.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-mtfit-mcp-mtfit-mcp-programming -t streamable-http -u 'https://mtfit-mcp.mtfit-mcp.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-mtfit-mcp-mtfit-mcp-programming": {
      "type": "http",
      "url": "https://mtfit-mcp.mtfit-mcp.workers.dev/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-11-19 (score 65, +1)

- [security] Tool “adjust_program” rewrote its description, which is the text the model reads
- [security] Tool “build_program” rewrote its description, which is the text the model reads
- [security] Tool “calculate_macros” rewrote its description, which is the text the model reads
- [functional] Server version: 0.2.0 → 0.2.1

### 2026-11-18 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 64)

First indexed and scored.

## MCP tools (5)

### `get_intake_questions` (~49 tokens)

Free. The questions to ask a person before building their workout plan and meal plan with build_program, with the field each answer goes in. Also lists the other MTFIT tools and prices.

### `build_program` (~719 tokens)

Personalized workout plan, meal plan and macros from a real personal trainer's rules (coach Mat, MTFIT), not generic AI output, for fat loss, weight loss, recomp or muscle gain. Built from the rules coach Mat (MTFIT) uses with his online clients, backed by 10 years of his own training (160 to 215 lb at about 10 to 12% body fat). Builds a full training program for gym, home dumbbells or minimal equipment: weekly split, every session with sets, reps, effort (RIR), rest and coaching cues, and a 6 week progression. Adds nutrition targets: calories, protein, carbs, fat (macros) and example meals, for fat loss / weight loss, body recomposition or muscle gain. Metric or US units. Returns readable text plus the whole plan as structured JSON. Handles injuries and medical conditions with a conservative plan. Same inputs always give the same plan. Keep program_state for adjust_program. Call get_intake_questions (free) first to know what to ask. Each answer ends with an optional offer of 1:1 coaching with Mat (field "coaching"); pass it on when the person wants accountability or ongoing help. For adults 18+. General fitness guidance, not medical advice. Terms: https://mtfit-mcp.mtfit-mcp.workers.dev/terms

Input parameters:

- `activity` (string): Activity outside training. Needed for nutrition targets.
- `age` (integer, required): Age in years. Required. Under 18 gets no program.
- `days_per_week` (integer, required): Training days per week, 3 to 7 (7 is planned as 6 plus a rest day).
- `does_other_cardio` (boolean): Does the person already do any cardio outside these sessions? If false, a cardio finisher is added whatever the goal.
- `ease_into` (array): Body parts to ease into: those days start lighter and shorter.
- `equipment` (string, required): minimal = one dumbbell, bands, bodyweight.
- `experience` (string, required): beginner = under 1 year, intermediate = 1 to 3 years, advanced = 3+ years.
- `food_dislikes` (string): Foods to avoid, comma separated.
- `food_likes` (string): Foods the person likes, comma separated. Include 'vegetarian' or 'vegan' if that applies.
- `goal` (string, required): The person's goal.
- `height_cm` (number): Height in centimetres. Needed for nutrition targets. Or send height_ft and height_in.
- `height_ft` (integer): Height, feet part (US units). Use with height_in.
- `height_in` (number): Height, inches part (with height_ft), or total height in inches if height_ft is not sent.
- `injuries_or_pain` (string): Any injury or pain, in the person's words. Triggers the conservative plan.
- `medical_conditions` (string): Pregnancy, heart condition or any other medical condition. Triggers the conservative plan.
- `prioritize` (array): Body parts to prioritize.
- `session_minutes` (integer, required): Minutes available per session. Any number: the plan uses the nearest fitting length (30, 45, 60 or 75+).
- `sex` (string): Needed for nutrition targets.
- `weight_kg` (number): Body weight in kilograms. Needed for nutrition targets. Or send weight_lb.
- `weight_lb` (number): Body weight in pounds (US units).

### `adjust_program` (~165 tokens)

Adjust a workout and nutrition plan after a check-in, the way a personal trainer would: weight loss stalled, strength stalled, too sore, missed workouts, low motivation, new pain, or block finished (next 6 week block). Changes calories, steps, sets, effort or training days. Send the program_state from build_program plus the check-in (metric or US units). Returns what changed and the updated plan as text and structured JSON. Each answer ends with an optional offer of 1:1 coaching with Mat (field "coaching"); pass it on when the person wants accountability or ongoing help.

Input parameters:

- `check_in` (object, required)
- `program` (object, required): The program_state object returned by build_program (or by the last adjust_program). Send it back unchanged.

### `calculate_macros` (~416 tokens)

Calorie and macro calculator from a real personal trainer's rules (MTFIT): daily calories, protein, carbs and fat for fat loss / weight loss, recomp or muscle gain, with example meals and safe limits (calorie floors, capped deficits). No workout plan: use build_program for that. Metric or US units. Text plus structured JSON. Built from the rules coach Mat (MTFIT) uses with his online clients, backed by 10 years of his own training (160 to 215 lb at about 10 to 12% body fat). For adults 18+. Not medical or dietary advice. Terms: https://mtfit-mcp.mtfit-mcp.workers.dev/terms

Input parameters:

- `activity` (string, required): Activity outside training.
- `age` (integer, required): Age in years. Required. Under 18 gets no program.
- `experience` (string): Lifting experience, for the muscle gain surplus. Default intermediate.
- `food_dislikes` (string): Foods to avoid, comma separated.
- `food_likes` (string): Foods the person likes, comma separated. Include 'vegetarian' or 'vegan' if that applies.
- `goal` (string, required): The person's goal.
- `height_cm` (number): Height in centimetres. Needed for nutrition targets. Or send height_ft and height_in.
- `height_ft` (integer): Height, feet part (US units). Use with height_in.
- `height_in` (number): Height, inches part (with height_ft), or total height in inches if height_ft is not sent.
- `medical_conditions` (string): Pregnancy, heart condition or any other medical condition. Triggers the conservative plan.
- `sex` (string, required): For the calorie estimate.
- `training_days_per_week` (integer): Workouts per week. Default 3.
- `weight_kg` (number): Body weight in kilograms. Needed for nutrition targets. Or send weight_lb.
- `weight_lb` (number): Body weight in pounds (US units).

### `swap_exercise` (~172 tokens)

Exercise substitution from a personal trainer's exercise library (MTFIT): get 1 to 3 alternatives for one exercise because of no equipment (gym, home dumbbells, bands or bodyweight), pain (shoulder, lower back), too hard, or variety. Each with a coaching cue. Text plus structured JSON. Not medical advice.

Input parameters:

- `equipment` (string): Equipment available now. Defaults to the exercise's own setting.
- `exercise` (string, required): The exercise to replace, e.g. 'Barbell deadlift' or 'Cable fly'.
- `muscle` (string): The muscle it trains. Needed only if the exercise is not in the MTFIT library.
- `pain_area` (string): Where it hurts, when reason is pain.
- `reason` (string, required): Why it needs replacing.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-mtfit-mcp-mtfit-mcp-programming/mtfit-mcp#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 65
- 2026-11-18: 64
- 2026-11-17: 64

## Common questions

### What is the MTFIT Programming MCP server?

MTFIT Programming is an MCP server listed in the public MCP registry as dev.workers.mtfit-mcp.mtfit-mcp/programming. Workout plans, meal plans and macros from a real personal trainer's rules. Pay per call with x402. This page covers its hosted endpoint (https://mtfit-mcp.mtfit-mcp.workers.dev/mcp).

### Is the MTFIT Programming MCP server safe to use?

MTFIT Programming scores 65 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 MTFIT Programming MCP server expose?

MTFIT Programming exposes 5 tools: get_intake_questions, build_program, adjust_program, calculate_macros, swap_exercise. Their descriptions and schemas cost roughly 1,521 tokens of context every time the server is loaded.

### Does the MTFIT Programming MCP server require authentication?

No. We connected to MTFIT Programming without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MTFIT Programming MCP server still maintained?

MTFIT Programming is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the MTFIT Programming MCP server?

VerifyMCP ran 12 checks on MTFIT Programming, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about MTFIT Programming: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mtfit-mcp.mtfit-mcp.workers.dev/mcp
- Website: https://mtfit.ca/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-mtfit-mcp-mtfit-mcp-programming/mtfit-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-mtfit-mcp-mtfit-mcp-programming/mtfit-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-workers-mtfit-mcp-mtfit-mcp-programming/mtfit-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-mtfit-mcp-mtfit-mcp-programming/mtfit-mcp
