Skip to content

MCP servers › com.almostfire › strength-training

MCP server · registry snapshot 2026-11-08 · last tested 2026-11-13

strength-training MCP server

Registry name com.almostfire/strength-training

Almost Fire — the publisher's title

by almostfire.com · domain (the registry's namespace rule)repository owner on GitHub: davidgibbon1 (personal account)Source ↗Website ↗

Strength training plans for 26 weeks, plus set, meal and progress logging in Almost Fire. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-13version 1.3.1streamable HTTP28 tools

Summary

com.almostfire/strength-training is a remote MCP server listed in the official MCP registry at version 1.3.1, under the namespace of the domain almostfire.com. Its linked repository is github.com/davidgibbon1/almost-fire-plugin; GitHub reports its owner as davidgibbon1, a personal account. On 2026-11-13 ProtocolProbe connected to it in read-only mode and read its inventory: 28 tools, 6 resources and 3 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
28
Last tested
2026-11-13

Tool list size

14,285 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (28 tools). Counted with Anthropic's token counter on 2026-11-13, from the tool list we read on 2026-11-13. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-13 (strength.almostfire.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.3.1).

Add to your client

Observed fact

This server accepted a session without any credential and lists 14 tools whose name or declaration suggests they change data (save_plan, log_set, edit_set, delete_set, swap_exercise and 9 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-13.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-13
Mode
read-only (no tool calls)
Latest version
1.3.1, published 2026-11-08 (registry, as of the 2026-11-08 snapshot)
First listed version
2026-11-08 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-11-08; 2 in the 90 days before the 2026-11-08 snapshot.
Most recent 2 versions
  • 1.3.1 · 2026-11-08
  • 1.3.0 · 2026-11-08
(versions still listed in the registry only)
Registry data
snapshot 2026-11-08
Package and repository
checked 2026-11-08
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-07, listed on 2026-11-08 with version 1.3.1 (published 2026-11-08).

Source: the official MCP Registry list on 2026-11-07 and on 2026-11-08.

What it is

What does this server offer?

Observed inventory
28tools
6resources
3prompts

None of its 28 tools are described as changing anything. For 28 the reading was uncertain, so no mark is shown.

  • make_plan

    “Use this when someone asks for a strength, gym, weightlifting or muscle-building program or workout plan, at a gym or at home.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    10 inputs, 1 required
    • daysPerWeekintegerrequired“Training days a week.”
    • goalstring or null“strength, muscle or fat_loss; null when they haven't said.”
    • equipmentstring or null“commercial (a full gym), home (a home gym with a rack) or dumbbells only.”
    • sessionMinutesinteger or null“How long a session can be.”
    • splitstring or null“full, upper_lower, ppl or body_part; auto or null picks the one that suits their days.”
    • protectarray or null“Areas to go easy on (a sore knee, a shoulder): the plan picks gentler options there.”
    • skipLiftsarray or null“Lifts they don't want.”
    • loveLiftsarray or null“Lifts they want in.”
    • buildPrioritiesarray or null“Up to two areas to build most.”
    • stylearray or null“How they like to train: supersets, straight sets, heavy, pump, machines, free weights, a finisher.”
  • save_plan

    “Use this when the person wants to keep, save or start a plan make_plan made, or presses Save on its card.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    12 inputs, 1 required
    • daysPerWeekintegerrequired“Training days a week.”
    • goalstring or null“strength, muscle or fat_loss; null when they haven't said.”
    • equipmentstring or null“commercial (a full gym), home (a home gym with a rack) or dumbbells only.”
    • sessionMinutesinteger or null“How long a session can be.”
    • splitstring or null“full, upper_lower, ppl or body_part; auto or null picks the one that suits their days.”
    • protectarray or null“Areas to go easy on (a sore knee, a shoulder): the plan picks gentler options there.”
    • skipLiftsarray or null“Lifts they don't want.”
    • loveLiftsarray or null“Lifts they want in.”
    • buildPrioritiesarray or null“Up to two areas to build most.”
    • stylearray or null“How they like to train: supersets, straight sets, heavy, pump, machines, free weights, a finisher.”
    • emailWeeklyboolean or null“true only when the person said yes, in this chat, to an email of each week's sessions on Monday mornings.”
    • idempotencyKeystring or null“A new random id for this change (a UUID).”
  • show_exercise

    “Use this when someone asks how to do an exercise, which muscles it works, or what to do instead.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • exercisestringrequired“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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Use this when the person asks what's coming up this week or next, or what they did on other days.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • fromstringrequired“Start of the range, an ISO date-time.”
    • tostringrequired“End of the range, an ISO date-time.”
  • “Use this when you need one session in full, by its id from get_today or get_schedule.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • sessionIdstringrequired“The session's id, from get_today or get_schedule.”
  • “Use this when the person tells you a set they did.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    8 inputs, 5 required
    • sessionIdstringrequired“The session's id, from get_today or get_schedule.”
    • slotstringrequired“The exercise's slot in that session, from get_today or get_session.”
    • loadUnitstring or null“kg or lb as they said it, or label for a machine's own numbers.”
    • setNumberinteger or null“Which set, from 1.”
    • loadnumberrequired“The weight they lifted, in loadUnit.”
    • repsintegerrequired“The reps they did.”
    • rirnumber or null“Reps in reserve, only when they say it; null otherwise.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • edit_set

    “Use this when the person corrects a set they already logged.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    6 inputs, 2 required
    • setIdstringrequired“The set's id, from get_today or get_session.”
    • loadUnitstring or null“The new load's unit, as in log_set.”
    • loadnumber or null“The corrected weight; null keeps it.”
    • repsinteger or null“The corrected reps; null keeps them.”
    • rirnumber or null“Corrected reps in reserve, only when they say it; null keeps it.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • delete_set

    “Use this when the person asks to remove a set they logged by mistake.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • setIdstringrequired“The set's id, from get_today or get_session.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • list_alternativeson 12 other servers

    “Use this when the person wants a different exercise in a session (a busy machine, a sore joint, missing kit).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • sessionIdstringrequired“The session's id, from get_today or get_schedule.”
    • slotstringrequired“The exercise's slot in that session, from get_today or get_session.”
  • swap_exerciseon 1 other server

    “Use this when the person asks to swap the exercise in a session.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    5 inputs, 4 required
    • sessionIdstringrequired“The session's id, from get_today or get_schedule.”
    • slotstringrequired“The exercise's slot in that session, from get_today or get_session.”
    • exerciseKeystringrequired“The exercise to put in the slot: its key from list_alternatives or get_session.”
    • untilWeekinteger or null“Keep the swap for that day through this program week (the plan keeps going past week 26); null swaps this session only.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • update_sessionon 5 other servers

    “Use this when the person starts, finishes or skips a session, or says how it felt.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    6 inputs, 2 required
    • sessionIdstringrequired“The session's id, from get_today or get_schedule.”
    • statusstring or null“IN_PROGRESS starts it, DONE finishes it, SKIPPED skips it, PLANNED puts it back; null leaves it.”
    • feelingstring or null“How it felt, 1 to 5; an empty string clears it, null leaves it.”
    • notesstring or null“Their notes on the session; an empty string clears them, null leaves them.”
    • gymstring or null“The gym they trained at, as they name it; null leaves it.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
Show 16 more tools
  • move_session

    “Use this when the person asks to move a session to another day or time.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    4 inputs, 4 required
    • sessionIdstringrequired“The session's id, from get_today or get_schedule.”
    • startstringrequired“The new start, an ISO date-time.”
    • endstringrequired“The new end, an ISO date-time.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • “Use this when the person tells you about cardio they did: a run, a ride, the rower, a walk.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    13 inputs, 3 required
    • sessionIdstring or null“The session to count it in, from get_today; null for cardio on its own.”
    • exerciseKeystringrequired“Which cardio: bike, treadmill, run, walk, rower, skierg, stairs, elliptical, swim.”
    • minutesnumberrequired“How long, in minutes.”
    • distanceKmnumber or null“Distance in kilometres, only if they give it.”
    • avgHeartRateinteger or null“Average heart rate in beats a minute, only if they give it.”
    • maxHeartRateinteger or null“Highest heart rate in beats a minute, only if they give it.”
    • effortstring or null“The talk test: easy (could hold a conversation), steady (short sentences), hard (a few words).”
    • levelnumber or null“The machine's resistance level, only if they give it.”
    • inclinenumber or null“Incline in percent, only if they give it.”
    • kcalnumber or null“Calories the machine or watch showed, only if they give it.”
    • intervalsobject or null“The intervals they did; null for steady cardio.”
    • startedAtstring or null“When it started, an ISO date-time; null is just finished.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • record_checkin

    “Use this when the person wants to check in about training or asks to record pain or swelling.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    5 inputs, 2 required
    • sessionIdstring or null“The session it's about, from get_today; null for a morning check-in.”
    • readinessinteger or null“How they feel today: 1 Flat, 2 Meh, 3 Okay, 4 Good, 5 On fire.”
    • symptomsobjectrequired“What they reported; null for anything they didn't say.”
    • notestring or null“Anything else they said, in their words.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • “Use this when the person tells you their weight.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • weightnumberrequired“The weight the scale showed, in unit.”
    • unitstring or null“kg or lb; null is their program's unit.”
    • measuredAtstring or null“When they weighed, an ISO date-time; null is now.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • open_camera

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • notestring or null“Anything they said about the meal, for the read.”
  • read_meal_photo

    “Use this when the person attaches a photo of food they ate or will eat.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 1 required
    • photoobjectrequired“The photo they attached.”
    • notestring or null“Anything they said about it ("half the rice", "oat flat white").”
  • read_meal_photo_upload

    “Processes a photo from the Almost Fire camera card using one read from their daily food-photo allowance.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 2 required
    • imagestringrequired“The photo, base64.”
    • mimeTypestringrequired“The photo's type, such as image/jpeg.”
    • notestring or null“Anything they said about it.”
  • search_foodson 9 other servers

    “Use this when the person tells you a food they ate without a photo, before log_foods.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • querystringrequired“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, …”
  • log_foods

    “Use this when the person has agreed what they ate and wants it logged.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    4 inputs, 2 required
    • eatenAtstring or null“When they ate, an ISO date-time; null is now.”
    • itemsarrayrequired“One entry per food.”
    • replacesarray or null“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.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • delete_food_entry

    “Use this when the person asks to remove a food they logged by mistake.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • entryIdstringrequired“The logged food's entry id, from get_nutrition.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • get_nutritionon 5 other servers

    “Use this when the person asks what they've eaten or how their calories and protein are going, and before removing a logged food.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • datestring or null“The day, as YYYY-MM-DD; null is today.”
  • show_progress_chart

    “Use this when the person asks to see their progress on a graph.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • metricstringrequired“Which of their Progress graphs to draw.”
    • keystring or null“The exercise key for lift_max, lift_volume and the cardio graphs; null otherwise.”
    • notestring or null“One line on what the graph shows, in your words.”
  • get_progresson 8 other servers

    “Use this when the person asks how they're progressing, in numbers.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_weekly_reviewon 3 other servers

    “Use this when the person asks how their week went or what changes next week.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • weekinteger or null“The program week (1 on; the plan keeps going past 26); null is the latest review.”
  • undo_review_change

    “Use this when the person doesn't want one of the changes the Sunday review made to next week.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 3 required
    • weekintegerrequired“The review's program week, from get_weekly_review.”
    • indexintegerrequired“The change's index in that review, from get_weekly_review.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”
  • “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.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • undoIdstringrequired“The undo.id a change came back with.”
    • idempotencyKeystringrequired“A new random id for this change (a UUID).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-13.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 104
Tools with a description
100% of 28
Typical description length
390 characters

The tool set

Counted from the listing

Tools
28
Size of the list
about 13,095 tokens for an agent to load (characters ÷ 4)
Naming
27 of 28 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 28 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-13 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://strength.almostfire.com/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "strength-training": {
      "url": "https://strength.almostfire.com/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "strength-training": {
      "type": "http",
      "url": "https://strength.almostfire.com/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"strength-training","type":"http","url":"https://strength.almostfire.com/api/mcp"}'
Claude Code
claude mcp add --transport http strength-training https://strength.almostfire.com/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "strength-training": {
      "type": "streamableHttp",
      "url": "https://strength.almostfire.com/api/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "strength-training": {
      "httpUrl": "https://strength.almostfire.com/api/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.strength-training]
url = "https://strength.almostfire.com/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "strength-training": {
      "url": "https://strength.almostfire.com/api/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://strength.almostfire.com/api/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint strength.almostfire.com/api/mcpSession openedmatchesour test · 2026-11-13
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-13
Repository github.com/davidgibbon1/almost-fire-pluginOpens publiclymatchesapi.github.com · 2026-11-08

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
com.almostfire
GitHub owner
a personal account (davidgibbon1)
Repository
github.com/davidgibbon1/almost-fire-plugin
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-08; security policy read from GitHub · 2026-11-08.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint strength.almostfire.com/api/mcp

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-08 to 2026-11-13; version 1.3.1).

Last change seen between our reads on 2026-11-08 (version 1.3.1) and 2026-11-13 (version 1.3.1). Changed without a new version: both reads list version 1.3.1.

Changed (23):

delete_food_entry: input schemadelete_set: input schemaedit_set: input schema, annotationsget_nutrition: input schemaget_schedule: input schemaget_session: input schemaget_weekly_review: input schemalist_alternatives: input schemalog_cardio: input schemalog_foods: description, input schema, annotationslog_set: input schemalog_weight: input schemamove_session: input schema, annotationsread_meal_photo: description, input schema, annotationsread_meal_photo_upload: description, input schema, annotationsrecord_checkin: description, input schema, annotationssave_plan: description, annotationssearch_foods: description, input schemashow_progress_chart: input schemaswap_exercise: input schema, annotationsundo: annotationsundo_review_change: input schema, annotationsupdate_session: input schema, annotations

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-13 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-08 (security policy 2026-11-08). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.almostfire/strength-training

Answered from the data above

Who publishes com.almostfire/strength-training?

The registry ties the namespace com.almostfire to the domain almostfire.com; only its owner can publish under it. Its linked repository is github.com/davidgibbon1/almost-fire-plugin; GitHub reports its owner as davidgibbon1, a personal account. These are facts from the registry and GitHub, not a rating.

Is com.almostfire/strength-training safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.almostfire/strength-training need an API key or sign-in?

It opened a session without any credential on 2026-11-13. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.almostfire/strength-training been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does com.almostfire/strength-training publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of com.almostfire/strength-training?

In github.com/davidgibbon1/almost-fire-plugin, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-13
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 5
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-13, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,549 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 28 tools, 6 resources, 3 prompts.
  4. 11,586 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-08; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
not stated
GitHub detects no source language in this repository (docs-only or empty)
Hosting type
registry · 2026-11-08
MCP capability
prompts, resources, tools
our test · 2026-11-13
Transport
streamable HTTP
registry · 2026-11-08
Required credentials
none declared
registry · 2026-11-08 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-08
Lifecycle status
registry · 2026-11-08
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-08
Maintenance
api.github.com · 2026-11-08
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-08

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.almostfire/strength-training: MCP server record.” Data checked 2026-11-13. https://protocolprobe.com/mcp/servers/com.almostfire/strength-training

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.almostfire/strength-training)](https://protocolprobe.com/mcp/servers/com.almostfire/strength-training)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology