Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TrainRec

REMOTE · API.TRAINREC.APP

Your AI assistant logs your meals and workouts, then plans your week from what you did.

Available components

+3 this week 80 Trust /100

Last scanned (18 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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 Security97
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5196 tokens (~152/item across 34 items; 34 tools + 0 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 52% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 20 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.

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1
    • Tool “trainrec_set_reminder” rewrote its description, which is the text the model reads security
    • Server version: 1.0.0+7a993c95e7a8 → 1.0.0+de64a3137af9 functional
    • “trainrec_set_reminder” added an optional parameter “amount” cosmetic
    • “trainrec_set_reminder” added an optional parameter “date” cosmetic
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 13 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “trainrec_edit_food” rewrote its description, which is the text the model reads security
    • Tool “trainrec_log_food” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0+b1ba19ea1ea5 → 1.0.0+7a993c95e7a8 functional
    • “trainrec_edit_food” added an optional parameter “planned” cosmetic
  • 12 Nov 26 76

    First indexed and scored.

Diagnostics

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://api.trainrec.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.trainrec.app CN=YE1,O=Let's Encrypt,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA384 6309c65fae86e3c2baba3fb420e1ca6cd3d
SANs: api.trainrec.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.trainrec.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
trainrec.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://api.trainrec.app/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://api.trainrec.app/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Protected resource metadata

Document https://api.trainrec.app/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://api.trainrec.app/mcp
Authorisation server https://api.trainrec.app

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.trainrec.app/mcp Verified 200
http (plaintext) http://api.trainrec.app/mcp HTTPS enforced 301 https://api.trainrec.app/mcp
MCP tools · 34 exposed · ~4,300 tokens

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 →

Tool Tokens
trainrec_add_exercise ~87

Makes a custom exercise with a name, kind and muscles. equipment: "plate" for a plate-loaded machine or "smith" for a Smith machine gives it a sled or bar its base weight is counted from (change_settings baseWeight).

NameTypeReqDescription
equipmentstring––
kindstringyes–
musclesarray––
namestringyes–

No output schema declared.

No examples provided.

trainrec_change_settings ~281

Changes settings. unit: lb or kg. foodShows: the full list of extra nutrients shown, in order, replacing the old one ([] shows only the macros). exerciseCalories: none, half or all of each day's bonus calories (active calories beyond a usual day, or workout calories when there is no daily count) added to the calorie target. weightGoal: a body weight in goalUnit (or theirs), or 0 to clear it; progress counts from their current trend. baseWeight: what a plate-loaded or Smith machine's sled or bar weighs empty, for one exercise (0 when not counted), or a barbell exercise's bar when it is not the standard 45 lb / 20 kg (an EZ or trap bar); it does not change sets already logged. birthYear: the year they were born, used only to estimate their maximum heart rate for heart rate zones. The change shows in the app with Undo.

NameTypeReqDescription
baseWeightobject––
birthYearinteger–The year they were born.
exerciseCaloriesstring––
foodShowsarray––
goalUnitstring–Unit of weightGoal. Defaults to the person's.
unitstring––
weightGoalnumber–Weight to reach, in goalUnit. 0 clears the goal.

No output schema declared.

No examples provided.

trainrec_delete_food ~44

Removes one food entry, given its id and version. The person can undo it in the app.

NameTypeReqDescription
idstringyes–
versionintegeryes–

No output schema declared.

No examples provided.

trainrec_delete_measurement ~44

Removes one reading, given its id and version. The person can undo it in the app.

NameTypeReqDescription
idstringyes–
versionintegeryes–

No output schema declared.

No examples provided.

trainrec_delete_reminder ~59

Removes one reminder, given its id and version. To stop it for a while instead, set_reminder with on false. The person can undo it in the app.

NameTypeReqDescription
idstringyes–
versionintegeryes–

No output schema declared.

No examples provided.

trainrec_delete_routine ~52

Removes one routine, given its id and version. Workouts already done from it stay. The person can undo it in the app.

NameTypeReqDescription
idstringyes–
versionintegeryes–

No output schema declared.

No examples provided.

trainrec_delete_workout ~51

Removes one workout, given its id and version. The person can undo it in the app.

NameTypeReqDescription
idstringyes–
summarystring––
versionintegeryes–

No output schema declared.

No examples provided.

trainrec_edit_food ~157

Changes fields of one food entry, given its id and version. Fields left out stay as they are; perServing is replaced whole. planned: false marks a planned food eaten, with servings or perServing in the same call as what was actually had.

NameTypeReqDescription
daystring––
idstringyes–
mealstring––
namestring––
perServingobject–For ONE serving, as the label or a reliable source states it.
plannedboolean–false: eaten. true: planned, not eaten yet.
servingLabelstring––
servingsnumber––
summarystring––
versionintegeryes–

No output schema declared.

No examples provided.

trainrec_exercise_history ~179

One exercise over time: personal records (heaviest, best estimated one-rep max, most reps, best session volume) and every session that included it, oldest first. Warm-ups and sets not done are excluded. pace is a straight line through the last 12 weeks of session estimated one-rep maxes (from weights and reps only), with where that line is in 4, 8 and 12 weeks; with target, also the day the line reaches it. pace is a projection at the current rate.

NameTypeReqDescription
exerciseIdstringyes–
limitinteger–Most recent sessions to return. Default 10.
targetnumber–A one-rep max to reach, in unit.
unitstring–Unit for every weight in this call. Defaults to the person's own unit.

No output schema declared.

No examples provided.

trainrec_find_issues ~81

Bugs and ideas already sent to the TrainRec team that look like what the person describes, best match first, with whether each is fixed. Call this before report_issue: if one matches, add to it rather than sending a new one. Read-only.

NameTypeReqDescription
querystringyesWhat went wrong or what they want, in a few words.

No output schema declared.

No examples provided.

trainrec_food_day ~53

Everything eaten on one day, each entry with its id and version, totals by meal and for the day, and what is left of the targets.

NameTypeReqDescription
daystring–YYYY-MM-DD. Default today.

No output schema declared.

No examples provided.

trainrec_get_routine ~54

One routine with every set, in the person's unit, and its version.

NameTypeReqDescription
idstringyes–
unitstring–Unit for every weight in this call. Defaults to the person's own unit.

No output schema declared.

No examples provided.

trainrec_get_workout ~54

One workout with every set, in the person's unit, and its version.

NameTypeReqDescription
idstringyes–
unitstring–Unit for every weight in this call. Defaults to the person's own unit.

No output schema declared.

No examples provided.

trainrec_import_file ~155

Imports a CSV exported from Strong (workouts or measurements) or Hevy, as text exactly as the file has it; the server parses it. A large file can be sent in pieces split on whole workouts, each with the header line and the same batch id. Strong exports omit their unit. Workouts already imported are skipped. Only Strong and Hevy formats.

NameTypeReqDescription
batchstring–Returned by the first call; pass it on later pieces of the same file.
formatstring–Detected from the header when omitted.
textstringyesThe CSV text, header line first.
unitstring–Unit for every weight in this call. Defaults to the person's own unit.

No output schema declared.

No examples provided.

trainrec_import_food ~116

Imports past meals from another nutrition app or file: each entry's day, meal, name, numbers PER SERVING and servings. Up to 200 entries per call; the same batch id on later calls makes one import, undone together. Entries already imported from the same app are skipped.

NameTypeReqDescription
appstringyesWhere these came from, e.g. "MyFitnessPal".
batchstring–Returned by the first call; pass it on later calls in the same import.
entriesarrayyes–

No output schema declared.

No examples provided.

trainrec_import_measurements ~108

Imports past measurements (weight, body fat, tape, blood pressure, resting heart rate, HRV, sleep, daily calories), each with its time as the source wrote it, kind, value and unit, and origin when the source names one. Up to 1000 per call; the same batch id on later calls makes one import. Readings already recorded are skipped.

NameTypeReqDescription
appstringyes–
batchstring––
itemsarrayyes–

No output schema declared.

No examples provided.

trainrec_import_workouts ~150

Imports past workouts from another app or file. Exercises are matched to existing ones by name; unmatched names become custom exercises, listed in the result. Up to 100 workouts per call; the same batch id on later calls makes one import, undone together. Workouts already imported from the same app are skipped.

NameTypeReqDescription
appstringyesWhere these came from, e.g. "FitNotes", "JEFIT", "Notes app".
batchstring–Returned by the first call; pass it on later calls in the same import.
unitstring–Unit for every weight in this call. Defaults to the person's own unit.
workoutsarrayyes–

No output schema declared.

No examples provided.

trainrec_list_exercises ~46

Exercise ids, names and kinds, built-in and custom, optionally filtered by words in the name. The kind decides which set fields apply.

NameTypeReqDescription
querystring––

No output schema declared.

No examples provided.

trainrec_list_workouts ~77

Workouts between two dates, newest first, with each exercise and how many of its sets were done. Sets themselves are not included.

NameTypeReqDescription
fromstring–YYYY-MM-DD, inclusive.
limitinteger–Default 20, at most 100.
tostring–YYYY-MM-DD, inclusive.

No output schema declared.

No examples provided.

trainrec_log_food ~175

Adds one or more food entries, each with its numbers PER SERVING and the number of servings. perServing takes the macros and any label nutrient (sodiumMg, potassiumMg and the rest); a nutrient left out counts as unknown, not zero. A glass of plain water is an entry named "Water" with kcal and macros 0 and waterMl. Each entry is its own change, with Undo. When the person asks to note a food without numbers ("just note it"), leave perServing out: it shows as numbers not added yet, until edit_food gives it perServing. planned: true puts a meal on a day ahead (or later today) without counting it in any total until it is eaten (edit_food planned: false).

NameTypeReqDescription
entriesarrayyes–
summarystring––

No output schema declared.

No examples provided.

trainrec_log_measurement ~126

Records one measurement: weight, body fat, a tape measurement, blood pressure, resting heart rate, HRV or sleep, in the unit given (lb, kg, %, in, cm, bpm, ms, mmHg, min). Blood pressure takes systolic as value and diastolic as value2.

NameTypeReqDescription
atstring–When it was taken, ISO or YYYY-MM-DD HH:MM. Default now.
kindstringyes–
unitstring––
valuenumberyes–
value2number––

No output schema declared.

No examples provided.

trainrec_measurements ~150

Body measurements over time, one kind at a time, one value per day (the last reading of the day), in the person's units, newest last: weight, body fat, tape measurements, calories eaten per day, resting heart rate, HRV, blood pressure and sleep, and from Oura readiness, sleep score, temperature change and minutes stressed and restored. Without kind, the latest reading of every kind recorded. Each value has its id and version.

NameTypeReqDescription
fromstring–YYYY-MM-DD.
kindstring––
limitinteger–Most recent days to return. Default 60, at most 400.
tostring–YYYY-MM-DD.

No output schema declared.

No examples provided.

trainrec_overview ~112

Today's date and weight unit for this person, today's food against their targets, their last few workouts, their routines, notes they left, and what they changed in the app since the assistant's last change (sets done differently from a plan show the planned values beside them). Each planned workout says whether it is reviewed: the app shows "Reviewed by" if the assistant wrote the plan after the person's latest workout. suggestedNext is the app's own pick from their rotation when nothing is planned today. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trainrec_plan_workout ~276

Plans a workout for the person to do: saves it in TrainRec, where their phone and watch walk them through it one set at a time, with each set's target (weight and reps, time or distance) and the rest after it. Every set starts as not yet done. Given an id and version, it changes an existing plan, even during the workout: sets already done are kept, and the phone and watch show the change within seconds. A workout that already happened is recorded with save_workout.

NameTypeReqDescription
daystring–YYYY-MM-DD. Default today.
exercisesarrayyesIn the order performed, by exercise id (built-in or custom).
freshboolean–true puts a workout started by mistake back to a plan: no set done, no start time. Send the whole plan.
idstring–Omit to create.
namestringyese.g. "Easy 5K and core", "Upper body A".
notesstring–Shown at the top while they follow it: the goal of the session, cues.
summarystring––
unitstring–Unit for every weight in this call. Defaults to the person's own unit.
versioninteger–Required when id is given.

No output schema declared.

No examples provided.

trainrec_recent_changes ~40

The latest changes to this log, newest first, with who made each one and its seq number.

NameTypeReqDescription
limitinteger–Default 20.

No output schema declared.

No examples provided.

trainrec_reminders ~39

The person's reminders (notifications on their phone): what each says, when, whether it is on, and who set it up. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trainrec_report_issue ~159

Send a bug or an idea to the TrainRec team, only after the person agrees to. Call find_issues first: if an issue matches, pass its issueId with what this person adds; otherwise pass kind, title and details for a new one. Say what happened and where in the app, never anything about their health beyond what the bug needs.

NameTypeReqDescription
detailsstringyesWhat happened, where in the app, and what they expected; or, with issueId, what this person adds.
issueIdinteger–A matching issue from find_issues.
kindstring––
titlestring–A new issue: one plain line, like "Rest timer does not show on the watch".

No output schema declared.

No examples provided.

trainrec_save_routine ~121

Creates a routine (a reusable workout plan the person starts from the app), or replaces one given its id and version. Same shape as a workout, without a day.

NameTypeReqDescription
exercisesarrayyesIn the order performed, by exercise id (built-in or custom).
idstring––
namestringyes–
notesstring––
summarystring––
unitstring–Unit for every weight in this call. Defaults to the person's own unit.
versioninteger––

No output schema declared.

No examples provided.

trainrec_save_workout ~264

Logs a new workout, or replaces an existing one given its id and version: the whole workout as it should now be, so anything left out is removed. Sets default to done; planned sets for a later day have done: false. The change shows in the person's app with Undo.

NameTypeReqDescription
daystring–YYYY-MM-DD. Default today.
exercisesarrayyesIn the order performed, by exercise id (built-in or custom).
finishedAtstring–When it ended, ISO with offset. Marks a logged workout finished.
idstring–Omit to create.
namestringyese.g. "Push Day".
notesstring––
reopenboolean–true takes the finish off a workout ended by mistake, so it is under way again.
startedAtstring–When it started, ISO with offset, if the person said ("this morning at 7"). Kept when editing.
summarystring–One short line for the change list, e.g. "Logged Push Day".
unitstring–Unit for every weight in this call. Defaults to the person's own unit.
versioninteger–Required when id is given.

No output schema declared.

No examples provided.

trainrec_set_reminder ~670

Reminders are TrainRec's notifications on the person's phone. They start at zero: none exist until the person asks their assistant (you) to set one up, so when they ask to be reminded of something, this is how. Adds a reminder, or changes one (give its id and version). Kinds: weigh_in, log_food (optionally one meal), workout (names today's planned workout if there is one) and streak (training weeks in a row, sent only if this week has no workout yet) go at a local time, and each is skipped that day once it is done. goal goes when a daily number is approaching or has reached its target (calories, a macro, or a nutrient with a target), not between 22:00 and 07:00. custom says the person's own words at a time. recap sends the day's calories and protein against their targets and its workout, at a time, every day it is on. Every reminder needs its trigger from the person: a time (their local time, 24-hour HH:MM) for timed kinds, or the amount left for an approaching goal alert. If they didn't say one, or said only "before 9 am", ask them what time; never choose it yourself. At most 20 reminders and 6 notifications a day. It shows in the app under the assistant's name, with Undo. threshold goes once, the first time today's total of a food number goes over an amount the person sets, whatever their target. check goes at a time only if today's total is still under (or over) the amount they set. Both need the whole trigger from the person: the food number, over or under, the amount, and for check a time outside 22:00 to 07:00. If they say "my target", say the number back and use that number. Set one up only when the person asks for it. A workout reminder can be for one day (date) instead of days of the week, for a planned workout: "remind me at 5 before Tuesday's workout". Its time is still the one the person says.

NameTypeReqDescription
amountobject–threshold and check only.
atstring–Local time, HH:MM 24-hour, as the person says it. Required for every kind but goal; ask them if they didn't say.
datestring–workout only: the one day it is for, YYYY-MM-DD, instead of days.
daysarray–1 = Monday to 7 = Sunday. Leave out for every day.
goalobject–goal only.
idstring–To change an existing reminder. Leave out to add one.
kindstringyes–
mealstring–log_food only.
onboolean–Default true. false keeps it but sends nothing.
streakstring–streak only. training_weeks: weeks in a row with a workout; training_days: days in a row with a workout or food logged.
textstring–custom only. What it says, up to 80 characters: "Take creatine".
versioninteger–Required with id.

No output schema declared.

No examples provided.

trainrec_set_targets ~132

Sets the daily calorie and macro targets, and optionally a target for any other nutrient (the keys in overview.foodNutrients): a ceiling for the ones to limit, such as sodiumMg, cholesterolMg, sugarG, saturatedFatG or caffeineMg, and an amount to reach for the rest, such as potassiumMg, fiberG or calciumMg. nutrients left out keeps the ones already set; {} clears them.

NameTypeReqDescription
carbsGnumberyes–
fatGnumberyes–
kcalnumberyes–
nutrientsobject––
proteinGnumberyes–

No output schema declared.

No examples provided.

trainrec_settings ~97

The person's settings: weight unit, which nutrients beyond the macros show on their Food and Today screens, how much of a day's workout calories is added to their calorie target, their weight goal, and what the sled or bar of a plate-loaded or Smith machine weighs empty (baseWeights; a set's weight is the total, so plates loaded = weight - base). Also lists what only the person can change on the phone. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trainrec_undo_change ~48

Puts a record back the way it was before one change, given the change's seq. Refused if the record has been changed again since.

NameTypeReqDescription
seqintegeryes–

No output schema declared.

No examples provided.

trainrec_undo_import ~43

Removes everything one import added, given its batch id. All or nothing: refused if any of it has been edited since.

NameTypeReqDescription
batchstringyes–

No output schema declared.

No examples provided.

Install

How do I install the TrainRec MCP server?

TrainRec is a hosted endpoint at https://api.trainrec.app/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 · api.trainrec.app

# add to Claude Code
claude mcp add --transport http app-trainrec-trainrec 'https://api.trainrec.app/mcp'
Common questions

What is the TrainRec MCP server?

TrainRec is an MCP server listed in the public MCP registry as app.trainrec/trainrec. Your AI assistant logs your meals and workouts, then plans your week from what you did. This page covers its hosted endpoint (https://api.trainrec.app/mcp).

Is the TrainRec MCP server safe to use?

TrainRec scores 80 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 TrainRec MCP server expose?

TrainRec exposes 34 tools: trainrec_overview, trainrec_list_workouts, trainrec_get_workout, trainrec_exercise_history, trainrec_list_exercises, and 29 more. Their descriptions and schemas cost roughly 4,300 tokens of context every time the server is loaded.

Does the TrainRec MCP server require authentication?

Yes. TrainRec asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the TrainRec MCP server still maintained?

TrainRec 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 TrainRec MCP server?

VerifyMCP ran 13 checks on TrainRec, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.