Almost Fire
REMOTE · STRENGTH.ALMOSTFIRE.COM
Strength training plans for 26 weeks, plus set, meal and progress logging in Almost Fire.
Available components
Last scanned (15 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (save_plan). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5484 tokens (~161/item across 34 items; 28 tools + 6 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 Management43
- Stability observed for 13 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
- Structured output schemas are declared (100% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 30 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 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.
- 16 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.
- 14 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.
- 12 Nov 26 +1
- Tool “log_foods” rewrote its description, which is the text the model reads security
- “log_foods” added an optional parameter “replaces” cosmetic
- 11 Nov 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “log_foods” rewrote its description, which is the text the model reads security
- Tool “read_meal_photo” rewrote its description, which is the text the model reads security
- Tool “read_meal_photo_upload” rewrote its description, which is the text the model reads security
- Tool “record_checkin” rewrote its description, which is the text the model reads security
- Tool “save_plan” rewrote its description, which is the text the model reads security
- Tool “search_foods” rewrote its description, which is the text the model reads security
- Tool “edit_set” is now declared destructive security
- Tool “log_foods” is now declared destructive security
- Tool “move_session” is now declared destructive security
- Tool “read_meal_photo” is now declared destructive security
- Tool “read_meal_photo_upload” is now declared destructive security
- Tool “record_checkin” is now declared destructive security
- Tool “save_plan” is now declared destructive security
- Tool “swap_exercise” is now declared destructive security
- Tool “undo” is now declared destructive security
- Tool “undo_review_change” is now declared destructive security
- Tool “update_session” is now declared destructive security
- Schema quality: 140 → 159 ▼ functional
- Tool coverage: 42% → 100% ▲ functional
- Schema quality: good → excellent functional
- “delete_food_entry” reworded the description of “entryId” cosmetic
- “delete_set” reworded the description of “setId” cosmetic
- “edit_set” reworded the description of “load” cosmetic
- “edit_set” reworded the description of “loadUnit” cosmetic
- “edit_set” reworded the description of “reps” cosmetic
- “edit_set” reworded the description of “rir” cosmetic
- “edit_set” reworded the description of “setId” cosmetic
- “get_nutrition” reworded the description of “date” cosmetic
- “get_schedule” reworded the description of “from” cosmetic
- “get_schedule” reworded the description of “to” cosmetic
- “get_session” reworded the description of “sessionId” cosmetic
- “get_weekly_review” reworded the description of “week” cosmetic
- “list_alternatives” reworded the description of “sessionId” cosmetic
- “list_alternatives” reworded the description of “slot” cosmetic
- “log_cardio” reworded the description of “avgHeartRate” cosmetic
- “log_cardio” reworded the description of “distanceKm” cosmetic
- “log_cardio” reworded the description of “effort” cosmetic
- “log_cardio” reworded the description of “exerciseKey” cosmetic
- “log_cardio” reworded the description of “incline” cosmetic
- “log_cardio” reworded the description of “intervals” cosmetic
- “log_cardio” reworded the description of “kcal” cosmetic
- “log_cardio” reworded the description of “level” cosmetic
- “log_cardio” reworded the description of “maxHeartRate” cosmetic
- “log_cardio” reworded the description of “minutes” cosmetic
- “log_cardio” reworded the description of “sessionId” cosmetic
- “log_cardio” reworded the description of “startedAt” cosmetic
- “log_foods” reworded the description of “eatenAt” cosmetic
- “log_foods” reworded the description of “items” cosmetic
- “log_set” reworded the description of “load” cosmetic
- “log_set” reworded the description of “loadUnit” cosmetic
- “log_set” reworded the description of “reps” cosmetic
- “log_set” reworded the description of “rir” cosmetic
- “log_set” reworded the description of “sessionId” cosmetic
- “log_set” reworded the description of “setNumber” cosmetic
- “log_set” reworded the description of “slot” cosmetic
- “log_weight” reworded the description of “measuredAt” cosmetic
- “log_weight” reworded the description of “unit” cosmetic
- “log_weight” reworded the description of “weight” cosmetic
- “move_session” reworded the description of “end” cosmetic
- “move_session” reworded the description of “sessionId” cosmetic
- “move_session” reworded the description of “start” cosmetic
- “read_meal_photo_upload” reworded the description of “mimeType” cosmetic
- “read_meal_photo_upload” reworded the description of “note” cosmetic
- “record_checkin” reworded the description of “note” cosmetic
- “record_checkin” reworded the description of “readiness” cosmetic
- “record_checkin” reworded the description of “sessionId” cosmetic
- “record_checkin” reworded the description of “symptoms” cosmetic
- “search_foods” reworded the description of “query” cosmetic
- “show_progress_chart” reworded the description of “metric” cosmetic
- “swap_exercise” reworded the description of “exerciseKey” cosmetic
- “swap_exercise” reworded the description of “sessionId” cosmetic
- “swap_exercise” reworded the description of “slot” cosmetic
- “swap_exercise” reworded the description of “untilWeek” cosmetic
- “undo_review_change” reworded the description of “index” cosmetic
- “undo_review_change” reworded the description of “week” cosmetic
- “update_session” reworded the description of “feeling” cosmetic
- “update_session” reworded the description of “gym” cosmetic
- “update_session” reworded the description of “notes” cosmetic
- “update_session” reworded the description of “sessionId” cosmetic
- “update_session” reworded the description of “status” cosmetic
- 10 Nov 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.
- 9 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://strength.almostfire.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=strength.almostfire.com | CN=YR1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | RSA 2048 | SHA256-RSA | 50bdaaaa4e66f0ff3e101f602a487674d73 |
| SANs: strength.almostfire.com | ||||||
| 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 insecure
Validation of strength.almostfire.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| almostfire.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://strength.almostfire.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://strength.almostfire.com/api/mcp | HTTPS enforced | 308 | https://strength.almostfire.com/api/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 →
delete_food_entry Remove a food ~108
Use this when the person asks to remove a food they logged by mistake. Give its entry id from get_nutrition. Comes back with an Undo. Do not use for a food they still ate; log the right amount instead.
| Name | Type | Req | Description |
|---|---|---|---|
| entryId | string | yes | The logged food's entry id, from get_nutrition. |
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
delete_set Remove a set ~99
Use this when the person asks to remove a set they logged by mistake. Give its setId. Comes back with an Undo. Do not use to change a set's numbers; use edit_set.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| setId | string | yes | The set's id, from get_today or get_session. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
edit_set Correct a set ~191
Use this when the person corrects a set they already logged. Give its setId from get_today or get_session and only the values they change; null keeps the rest. Comes back with an Undo. Do not use to log a new set; use log_set.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| load | number|null | – | The corrected weight; null keeps it. |
| loadUnit | string|null | – | The new load's unit, as in log_set. Only with a new load. |
| reps | integer|null | – | The corrected reps; null keeps them. |
| rir | number|null | – | Corrected reps in reserve, only when they say it; null keeps it. |
| setId | string | yes | The set's id, from get_today or get_session. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_nutrition Food for a day ~101
Use this when the person asks what they've eaten or how their calories and protein are going, and before removing a logged food. Reads a day's food (date null is today): every entry with its id, the totals against the day's targets, their usual foods and saved recipes, and the weight trend. Do not use to log food; use log_foods.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | – | The day, as YYYY-MM-DD; null is today. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_progress Progress ~68
Use this when the person asks how they're progressing, in numbers. Reads their Progress page: training volume by week, bests, each lift's estimated max and trend, sessions done, bodyweight and cardio, as the app shows them. Do not use for a graph; use show_progress_chart.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_schedule Sessions in a range ~96
Use this when the person asks what's coming up this week or next, or what they did on other days. Lists their sessions between two ISO times (from, to), each with its id, day, time and status. Do not use for today's session; use get_today.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start of the range, an ISO date-time. |
| to | string | yes | End of the range, an ISO date-time. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_session One session ~79
Use this when you need one session in full, by its id from get_today or get_schedule. Reads its exercises (slots) with each target, the exercises each slot allows, and the sets logged. Do not use to list sessions; use get_schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | The session's id, from get_today or get_schedule. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_today Today ~86
Use this when the person asks what's on today or how today's session is going, and before logging a set. Reads today's session (or the next one) in their Almost Fire account with every exercise, its target and the sets logged, this week's sessions and training volume, and their food and weight so far today. Do not use for another day's session; use get_schedule and get_session.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_weekly_review The Sunday review ~124
Use this when the person asks how their week went or what changes next week. Reads the Sunday review of a program week (null is the latest): sessions, volume, new bests, the pace, each change Stoke made to next week with its reason, and what was kept and why. Those changes follow fixed rules: explain each from its reason, never invent another. Do not use for today's session; use get_today.
| Name | Type | Req | Description |
|---|---|---|---|
| week | integer|null | – | The program week (1 on; the plan keeps going past 26); null is the latest review. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_alternatives Swaps for an exercise ~122
Use this when the person wants a different exercise in a session (a busy machine, a sore joint, missing kit). Lists the swaps that train the same movement in that slot and week, best first, by sessionId and slot. Nothing changes; swap with swap_exercise. Do not use to explain how an exercise is done; use show_exercise.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | The session's id, from get_today or get_schedule. |
| slot | string | yes | The exercise's slot in that session, from get_today or get_session. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
log_cardio Log cardio ~444
Use this when the person tells you about cardio they did: a run, a ride, the rower, a walk. Record cardio the person did, with the numbers they give: minutes always; distance, heart rate, level, incline, energy and intervals only when given. Never invent them. effort is a talk test: easy (could hold a conversation), steady (short sentences), hard (a few words). Give sessionId to count it in that session (it fills the session's planned cardio when it is the same exercise), or null for cardio on its own. Null startedAt is just finished. Cardio counts as minutes, never kilograms. Applied immediately with Undo. Do not use for a lifting set; use log_set.
| Name | Type | Req | Description |
|---|---|---|---|
| avgHeartRate | integer|null | – | Average heart rate in beats a minute, only if they give it. |
| distanceKm | number|null | – | Distance in kilometres, only if they give it. |
| effort | string|null | – | The talk test: easy (could hold a conversation), steady (short sentences), hard (a few words). |
| exerciseKey | string | yes | Which cardio: bike, treadmill, run, walk, rower, skierg, stairs, elliptical, swim. |
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| incline | number|null | – | Incline in percent, only if they give it. |
| intervals | – | – | The intervals they did; null for steady cardio. |
| kcal | number|null | – | Calories the machine or watch showed, only if they give it. |
| level | number|null | – | The machine's resistance level, only if they give it. |
| maxHeartRate | integer|null | – | Highest heart rate in beats a minute, only if they give it. |
| minutes | number | yes | How long, in minutes. |
| sessionId | string|null | – | The session to count it in, from get_today; null for cardio on its own. |
| startedAt | string|null | – | When it started, an ISO date-time; null is just finished. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
log_foods Log a meal ~226
Use this when the person has agreed what they ate and wants it logged. Logs one entry per food using the reviewed photo estimates, a saved food or recipe by id and grams, or a named estimate with its serving and nutrients. Logging a saved food by grams can replace its usual portion. A correction to food already logged passes replaces, so the original comes off in the same change. Undo removes the log entries and brings back any replaced. eatenAt null is now. Do not use before they've agreed the foods and amounts, or for a meal they're only planning.
| Name | Type | Req | Description |
|---|---|---|---|
| eatenAt | string|null | – | When they ate, an ISO date-time; null is now. |
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| items | array | yes | One entry per food. |
| replaces | – | – | Logged entries this corrects (their ids, from get_nutrition), taken off in the same change so the original isn't left beside the fix; null adds to the log. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
log_set Log a set ~280
Use this when the person tells you a set they did. Give the session and slot from get_today or get_session, and the load and reps they said. Never invent a number. loadUnit kg or lb as they said it (label for a machine's own numbers); rir only if they say it. setNumber null logs the next set. Comes back with an Undo. Do not use to correct a set already logged; use edit_set.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| load | number | yes | The weight they lifted, in loadUnit. |
| loadUnit | string|null | – | kg or lb as they said it, or label for a machine's own numbers. Null is kg, or the machine's numbers on a labelled machine. |
| reps | integer | yes | The reps they did. |
| rir | number|null | – | Reps in reserve, only when they say it; null otherwise. |
| sessionId | string | yes | The session's id, from get_today or get_schedule. |
| setNumber | integer|null | – | Which set, from 1. Null logs the next set not yet logged. |
| slot | string | yes | The exercise's slot in that session, from get_today or get_session. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
log_weight Log a weigh-in ~143
Use this when the person tells you their weight. Give the weight and unit, and when (null is now). Targets follow the smoothed trend, never one reading. Comes back with an Undo. Do not use to set a weight goal.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| measuredAt | string|null | – | When they weighed, an ISO date-time; null is now. |
| unit | string|null | – | kg or lb; null is their program's unit. |
| weight | number | yes | The weight the scale showed, in unit. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
make_plan Make a training plan ~330
Use this when someone asks for a strength, gym, weightlifting or muscle-building program or workout plan, at a gym or at home. Builds all 26 weeks from Almost Fire's plan engine, the one the app uses: the split for their days, each session's exercises with sets, reps, rest and effort, a lighter week to end each block, and gentler swaps for anything they protect. No account needed. Ask how many days they can train first; fill the rest from what they've said and leave the others null. Do not use for running or race plans, sport-specific conditioning, diet plans or injury rehab.
| Name | Type | Req | Description |
|---|---|---|---|
| buildPriorities | – | – | Up to two areas to build most. |
| daysPerWeek | integer | yes | Training days a week. |
| equipment | string|null | – | commercial (a full gym), home (a home gym with a rack) or dumbbells only. |
| goal | string|null | – | strength, muscle or fat_loss; null when they haven't said. |
| loveLifts | – | – | Lifts they want in. |
| protect | – | – | Areas to go easy on (a sore knee, a shoulder): the plan picks gentler options there. |
| sessionMinutes | integer|null | – | How long a session can be. |
| skipLifts | – | – | Lifts they don't want. |
| split | string|null | – | full, upper_lower, ppl or body_part; auto or null picks the one that suits their days. |
| style | – | – | How they like to train: supersets, straight sets, heavy, pump, machines, free weights, a finisher. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
move_session Move a session ~137
Use this when the person asks to move a session to another day or time. Give its sessionId and the new start and end as ISO times. Comes back with an Undo. Do not use to skip a session; use update_session.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | The new end, an ISO date-time. |
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| sessionId | string | yes | The session's id, from get_today or get_schedule. |
| start | string | yes | The new start, an ISO date-time. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
open_camera Open the Almost Fire camera ~100
Use this when the person wants to log a meal from a photo but hasn't attached one, or the app can't hand you their photo. Opens the Almost Fire camera in the chat: they take or choose a photo there, Stoke reads each food with its grams and calories, and Log saves it. Do not use when they've attached a photo; use read_meal_photo.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string|null | – | Anything they said about the meal, for the read. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
read_meal_photo Read a meal photo ~138
Use this when the person attaches a photo of food they ate or will eat. Returns estimated foods, grams, calories and macros for a plate, nutrition per 100 g for a packet, or grams for a kitchen scale. Processing uses one read from their daily food-photo allowance. Review the estimates and corrections with them before logging separately with log_foods or Log it on the card. Do not use for a photo that isn't food, or to judge anyone's body.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string|null | – | Anything they said about it ("half the rice", "oat flat white"). |
| photo | object | yes | The photo they attached. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
read_meal_photo_upload Read the camera's photo ~87
Processes a photo from the Almost Fire camera card using one read from their daily food-photo allowance. The card shows the result for review. Log it saves the food separately.
| Name | Type | Req | Description |
|---|---|---|---|
| image | string | yes | The photo, base64. |
| mimeType | string | yes | The photo's type, such as image/jpeg. |
| note | string|null | – | Anything they said about it. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
record_checkin Check in ~191
Use this when the person wants to check in about training or asks to record pain or swelling. Records their check-in. A morning milestone can post to their crew and notify crew members. Do not use to diagnose pain, when symptoms were mentioned only to ask for advice, or to log their weight.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| note | string|null | – | Anything else they said, in their words. |
| readiness | integer|null | – | How they feel today: 1 Flat, 2 Meh, 3 Okay, 4 Good, 5 On fire. |
| sessionId | string|null | – | The session it's about, from get_today; null for a morning check-in. |
| symptoms | object | yes | What they reported; null for anything they didn't say. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
save_plan Save the plan to Almost Fire ~399
Use this when the person wants to keep, save or start a plan make_plan made, or presses Save on its card. Saves the plan to their Almost Fire account for free and replaces any unstarted plan. Send the answers make_plan used, so the saved plan is the one they saw. The card then opens their plan page in Almost Fire, where their first week starts. emailWeekly true also opts them into emails with each week's sessions on Monday mornings, until they start in the app. Do not use before make_plan has shown them a plan, or to change the plan of someone who already trains in Almost Fire.
| Name | Type | Req | Description |
|---|---|---|---|
| buildPriorities | – | – | Up to two areas to build most. |
| daysPerWeek | integer | yes | Training days a week. |
| emailWeekly | boolean|null | – | true only when the person said yes, in this chat, to an email of each week's sessions on Monday mornings. Null otherwise; never assume it. |
| equipment | string|null | – | commercial (a full gym), home (a home gym with a rack) or dumbbells only. |
| goal | string|null | – | strength, muscle or fat_loss; null when they haven't said. |
| idempotencyKey | string|null | – | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| loveLifts | – | – | Lifts they want in. |
| protect | – | – | Areas to go easy on (a sore knee, a shoulder): the plan picks gentler options there. |
| sessionMinutes | integer|null | – | How long a session can be. |
| skipLifts | – | – | Lifts they don't want. |
| split | string|null | – | full, upper_lower, ppl or body_part; auto or null picks the one that suits their days. |
| style | – | – | How they like to train: supersets, straight sets, heavy, pump, machines, free weights, a finisher. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
search_foods Find their foods ~495
Use this when the person tells you a food they ate without a photo, before log_foods. Find the person's own foods before anything else, by name or by kind: the words they used ("protein powder", "milk", "my usual bread"), not a brand you guess. mine is their saved foods that fit, each with an id, macros per 100 g, their usual grams (lastGrams), match (name: its name holds the words; kind: it is that kind of food, so "protein powder" finds their whey; word: only the last of their words, the one that says what it is, fits, so it is a different food of that sort, never theirs unless they say so) and lastEatenAt. When none fits by name, recent lists the saved foods they logged lately: read it too, because their food is often named by brand (a protein powder called Impact Lean Whey, a milk called Light Start). list is at most three plain foods from the food list, each with a foodKey; logging one saves it as a new food of theirs. Use their own food (mine or recent) when it is the same thing, or the kind of food they named (their milk for "milk", their whey for "protein powder"); a food that only sounds alike or shares a word is not it (corn flour is not corn, dark soy sauce is not dark chocolate). "My most recent" or "my usual" means the one they ate latest. Use list, an estimate or create_food only when none of theirs is it, and say it's new. Search before estimating, and log what it finds by grams. A meal of several foods is one search: put them in one query separated by semicolons ("egg pasta; halloumi; butter; olive oil") and foods comes back with one result for each, so you can log the whole meal in your next step. A recipe has recipe set: its foods and their grams, serves, cookedGrams and gramsLeft, what's left of the pot. Do not use to read a photo; use read_meal_photo.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The words they used for the food, such as "protein powder" or "my usual bread"; several foods separated by semicolons ("oats; milk; whey") come back as foods, one result each. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
show_exercise Show an exercise ~91
Use this when someone asks how to do an exercise, which muscles it works, or what to do instead. Shows it on the body map with its equipment, its cues and swaps that train the same thing. No account needed. Do not use to diagnose pain or to give rehab exercises.
| Name | Type | Req | Description |
|---|---|---|---|
| exercise | string | yes | The exercise's name ("Romanian deadlift") or Almost Fire key ("rdl"). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
show_progress_chart Show a progress graph ~163
Use this when the person asks to see their progress on a graph. Draws one of their Progress graphs from their records: lift_max or lift_volume per session for one exercise (key), weekly_volume, body_weight (90 days), cardio_distance, cardio_pace or cardio_heart_rate, daily_kcal or daily_protein (30 days). Training volume is the number that matters most. Do not use for sleep or heart-rate numbers, which stay in the Almost Fire app.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string|null | – | The exercise key for lift_max, lift_volume and the cardio graphs; null otherwise. |
| metric | string | yes | Which of their Progress graphs to draw. |
| note | string|null | – | One line on what the graph shows, in your words. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
swap_exercise Swap an exercise ~242
Use this when the person asks to swap the exercise in a session. Give the sessionId and slot, and the exerciseKey they chose, or a same-movement one from list_alternatives when they leave it to you. The new exercise brings its own rules, and loads never carry over between exercises. untilWeek null swaps that session only; a week keeps the swap for that day through that program week. Comes back with an Undo. Do not use to move a session; use move_session.
| Name | Type | Req | Description |
|---|---|---|---|
| exerciseKey | string | yes | The exercise to put in the slot: its key from list_alternatives or get_session. |
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| sessionId | string | yes | The session's id, from get_today or get_schedule. |
| slot | string | yes | The exercise's slot in that session, from get_today or get_session. |
| untilWeek | integer|null | – | Keep the swap for that day through this program week (the plan keeps going past week 26); null swaps this session only. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
undo Undo a change ~112
Use this when the person wants to take back a change made here (a logged set, meal, weigh-in or any other) while its Undo is open. Give the undo.id the change came back with. Do not use for a change they made in the Almost Fire app itself.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| undoId | string | yes | The undo.id a change came back with. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
undo_review_change Keep next week as planned ~135
Use this when the person doesn't want one of the changes the Sunday review made to next week. Give the change's index from get_weekly_review. Next week goes back to the program's target for that change. Do not use for a change they made themselves; use undo.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| index | integer | yes | The change's index in that review, from get_weekly_review. |
| week | integer | yes | The review's program week, from get_weekly_review. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_session Start or finish a session ~243
Use this when the person starts, finishes or skips a session, or says how it felt. status IN_PROGRESS starts it, DONE finishes it and SKIPPED skips it; feeling is 1 to 5; notes and gym as they say. Null leaves a field as it is. Comes back with an Undo. Do not use to move a session to another day; use move_session.
| Name | Type | Req | Description |
|---|---|---|---|
| feeling | string|null | – | How it felt, 1 to 5; an empty string clears it, null leaves it. |
| gym | string|null | – | The gym they trained at, as they name it; null leaves it. |
| idempotencyKey | string | yes | A new random id for this change (a UUID). Send the same one again only to retry this exact change. |
| notes | string|null | – | Their notes on the session; an empty string clears them, null leaves them. |
| sessionId | string | yes | The session's id, from get_today or get_schedule. |
| status | string|null | – | IN_PROGRESS starts it, DONE finishes it, SKIPPED skips it, PLANNED puts it back; null leaves it. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
How do I install the Almost Fire MCP server?
Almost Fire is a hosted endpoint at https://strength.almostfire.com/api/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 · strength.almostfire.com
claude mcp add --transport http com-almostfire-strength-training 'https://strength.almostfire.com/api/mcp'
What is the Almost Fire MCP server?
Almost Fire is an MCP server listed in the public MCP registry as com.almostfire/strength-training. Strength training plans for 26 weeks, plus set, meal and progress logging in Almost Fire. This page covers its hosted endpoint (https://strength.almostfire.com/api/mcp).
Is the Almost Fire MCP server safe to use?
Almost Fire scores 74 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 Almost Fire MCP server expose?
Almost Fire exposes 28 tools: make_plan, save_plan, show_exercise, get_today, get_schedule, and 23 more. Their descriptions and schemas cost roughly 5,030 tokens of context every time the server is loaded.
Does the Almost Fire MCP server require authentication?
No. We connected to Almost Fire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Almost Fire MCP server still maintained?
Almost Fire 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 Almost Fire MCP server?
VerifyMCP ran 14 checks on Almost Fire, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. 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.