Name: Almost Fire
Author: almostfire

Almost Fire MCP

Strength training plans for 26 weeks, plus set, meal and progress logging in Almost Fire.

Tool-list grade A Remote · Streamable HTTP No auth needed 28 tools v1.3.0

No reviews yet by almostfire The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Strength training plans for 26 weeks, plus set, meal and progress logging in Almost Fire.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http almost-fire-mcp https://strength.almostfire.com/api/mcp

# 2 — ask your agent for something these tools do
#   make_plan, save_plan, show_exercise and 25 more

Almost Fire costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

almostfire1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

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 day

Parameter	Type	Required	Notes
daysPerWeek	integer	yes	Training days a week.
goal	string/null	no	strength, muscle or fat_loss; null when they haven't said.
equipment	string/null	no	commercial (a full gym), home (a home gym with a rack) or dumbbells only.
sessionMinutes	integer/null	no	How long a session can be.
split	string/null	no	full, upper_lower, ppl or body_part; auto or null picks the one that suits their days.
protect		no	Areas to go easy on (a sore knee, a shoulder): the plan picks gentler options there.
skipLifts		no	Lifts they don't want.
loveLifts		no	Lifts they want in.
buildPriorities		no	Up to two areas to build most.
style		no	How they like to train: supersets, straight sets, heavy, pump, machines, free weights, a finisher.

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, free: the first time it asks them to sign in, which makes their account. 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

Parameter	Type	Required	Notes
daysPerWeek	integer	yes	Training days a week.
goal	string/null	no	strength, muscle or fat_loss; null when they haven't said.
equipment	string/null	no	commercial (a full gym), home (a home gym with a rack) or dumbbells only.
sessionMinutes	integer/null	no	How long a session can be.
split	string/null	no	full, upper_lower, ppl or body_part; auto or null picks the one that suits their days.
protect		no	Areas to go easy on (a sore knee, a shoulder): the plan picks gentler options there.
skipLifts		no	Lifts they don't want.
loveLifts		no	Lifts they want in.
buildPriorities		no	Up to two areas to build most.
style		no	How they like to train: supersets, straight sets, heavy, pump, machines, free weights, a finisher.
emailWeekly	boolean/null	no	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.
idempotencyKey	string/null	no	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
exercise	string	yes	The exercise's name ("Romanian deadlift") or Almost Fire key ("rdl").

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.

No parameter schema on file.

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.

Parameter	Type	Required	Notes
from	string	yes	—
to	string	yes	—

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.

Parameter	Type	Required	Notes
sessionId	string	yes	—

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.

Parameter	Type	Required	Notes
sessionId	string	yes	—
slot	string	yes	—
loadUnit	string/null	no	—
setNumber	integer/null	no	—
load	number	yes	—
reps	integer	yes	—
rir	number/null	no	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
setId	string	yes	—
loadUnit	string/null	no	—
load	number/null	no	—
reps	integer/null	no	—
rir	number/null	no	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
setId	string	yes	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
sessionId	string	yes	—
slot	string	yes	—

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 wit

Parameter	Type	Required	Notes
sessionId	string	yes	—
slot	string	yes	—
exerciseKey	string	yes	—
untilWeek	integer/null	no	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
sessionId	string	yes	—
status	string/null	no	—
feeling	string/null	no	—
notes	string/null	no	—
gym	string/null	no	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
sessionId	string	yes	—
start	string	yes	—
end	string	yes	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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 s

Parameter	Type	Required	Notes
sessionId	string/null	no	—
exerciseKey	string	yes	—
minutes	number	yes	—
distanceKm	number/null	no	—
avgHeartRate	integer/null	no	—
maxHeartRate	integer/null	no	—
effort	string/null	no	—
level	number/null	no	—
incline	number/null	no	—
kcal	number/null	no	—
intervals		no	—
startedAt	string/null	no	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

Use this when the person says how they feel before or after training, or tells you about pain or swelling. Record the person’s reported readiness and symptoms. symptoms.pec is pain anywhere (sharp means sharp pain or pulling) and symptoms.knee is swelling anywhere, whatever the body part. After a session they may also report feel, strength, effort (1–10 for the whole session), more (sets they coul

Parameter	Type	Required	Notes
sessionId	string/null	no	—
readiness	integer/null	no	—
symptoms	object	yes	—
note	string/null	no	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
weight	number	yes	—
unit	string/null	no	—
measuredAt	string/null	no	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
note	string/null	no	Anything they said about the meal, for the read.

Use this when the person attaches a photo of food they ate or will eat. Reads it as the Almost Fire camera does: a plate or bowl comes back as each food with its grams, calories, macros and how sure the read is; a packet as its label per 100 g; a pot on a kitchen scale as its grams. Nothing is logged: read it back, take their corrections, then call log_foods with its logItems (or they tap Log on t

Parameter	Type	Required	Notes
photo	object	yes	The photo they attached.
note	string/null	no	Anything they said about it ("half the rice", "oat flat white").

The Almost Fire camera card's photo, read as read_meal_photo reads one. Only the card calls it.

Parameter	Type	Required	Notes
image	string	yes	The photo, base64.
mimeType	string	yes	—
note	string/null	no	—

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 th

Parameter	Type	Required	Notes
query	string	yes	—

Use this when the person has agreed what they ate and wants it logged. One entry per food: from a photo read (read_meal_photo's logItems, with their corrections), a saved food or recipe by id and grams (from search_foods), or an estimate with a name, serving, quantity and its numbers per serving. eatenAt null is now. Comes back with an Undo. Do not use before they've agreed the foods and amounts,

Parameter	Type	Required	Notes
eatenAt	string/null	no	—
items	array	yes	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
entryId	string	yes	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
date	string/null	no	—

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,

Parameter	Type	Required	Notes
metric	string	yes	—
key	string/null	no	The exercise key for lift_max, lift_volume and the cardio graphs; null otherwise.
note	string/null	no	One line on what the graph shows, in your words.

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.

No parameter schema on file.

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.

Parameter	Type	Required	Notes
week	integer/null	no	—

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.

Parameter	Type	Required	Notes
week	integer	yes	—
index	integer	yes	—
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

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.

Parameter	Type	Required	Notes
undoId	string	yes	The undo.id a change came back with.
idempotencyKey	string	yes	A new random id for this change (a UUID). Send the same one again only to retry this exact change.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Almost Fire or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.3.0 · scanned 8 Nov 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 0 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digeste9c5b9a9262e6546c66d767c0595ed2c22dc71187dca7f2e2e6d800359051daf

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
make_plan	no tags
save_plan	state-write	state-write: declares readOnlyHint: false
show_exercise	no tags
get_today	no tags
get_schedule	no tags
get_session	no tags
log_set	state-write	state-write: declares readOnlyHint: false
edit_set	state-write	state-write: declares readOnlyHint: false
delete_set	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
list_alternatives	no tags
swap_exercise	state-write	state-write: declares readOnlyHint: false
update_session	state-write	state-write: declares readOnlyHint: false
move_session	state-write	state-write: declares readOnlyHint: false
log_cardio	state-write	state-write: declares readOnlyHint: false
record_checkin	state-write	state-write: declares readOnlyHint: false
log_weight	state-write	state-write: declares readOnlyHint: false
open_camera	no tags
read_meal_photo	no tags
read_meal_photo_upload	no tags
search_foods	no tags
log_foods	state-write	state-write: declares readOnlyHint: false
delete_food_entry	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
get_nutrition	no tags
show_progress_chart	no tags
get_progress	no tags
get_weekly_review	no tags
undo_review_change	state-write	state-write: declares readOnlyHint: false
undo	state-write	state-write: declares readOnlyHint: false

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digeste9c5b9a9262e6546

Scanned2026-11-08

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

Almost Fire MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also