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.

io.github.codymcc4/fuelcenter

REMOTE · FUELCENTER.CO

Marathon fueling, pace, hydration, heat, carb-loading, and gel-comparison calculators.

Available components

0 this week 85 Trust /100

Last scanned (13 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 876 tokens (~125/item across 7 items; 7 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://fuelcenter.co/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fuelcenter.co CN=YR1,O=Let's Encrypt,C=US 4 Oct 2026 2 Jan 2027 RSA 2048 SHA256-RSA 6c78d60e54e51f49b16f52863555dccbf50
SANs: fuelcenter.co
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 fuelcenter.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
fuelcenter.co. 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://fuelcenter.co/api/mcp Verified 200
http (plaintext) http://fuelcenter.co/api/mcp HTTPS enforced 308 https://fuelcenter.co/api/mcp
MCP tools · 7 exposed · ~833 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
carb-loading ~133

Calculate pre-race carb loading targets by race type, body weight, finish time, and experience level. Returns daily carb target, protocol length, total carbs, and pre-race meal size.

NameTypeReqDescription
bodyWeightLbsnumberyesBody weight in pounds.
experiencestringyesRunner experience level.
finishTimeHoursnumberyesExpected finish time, hours portion.
finishTimeMinutesnumberyesExpected finish time, minutes portion.
hasGIIssuesboolean–Whether the runner has a sensitive stomach. Default false.
raceTypestringyesRace distance category.

No output schema declared.

No examples provided.

fueling-plan ~208

Build a minute-by-minute race or long-run fueling plan. Returns target carbs/hour, gel count, gel timing schedule, and total carbs. This is the core FuelCenter tool.

NameTypeReqDescription
buffernumber–Minutes of buffer at start and end where no gel is taken. Default 5.
drinkCarbsTotalnumber–Total grams of carbs from drink mix across the run. Default 0.
drinkMixboolean–Whether the runner uses a carbohydrate drink mix. Default false.
experiencestring–Runner experience with fueling. Default "standard".
gelKeystringyesGel product key. See /api/tools/gel-comparison for full catalog.
hoursnumberyesRace or run duration, hours portion.
intensitystringyesEffort level.
minutesnumberyesRace or run duration, minutes portion.
targetCPHnumber–Target carbs per hour. If omitted, default is derived from guideline.

No output schema declared.

No examples provided.

gel-comparison ~94

Return the FuelCenter gel catalog (SiS Beta Fuel, Maurten, Precision, GU, Tailwind, Spring, Carbs Fuel, neversecond, Huma) with carbs, price, caffeine, weight, and carbs-per-dollar. Optionally sort.

NameTypeReqDescription
sortDirectionstring–Sort direction. Default "desc".
sortKeystring–Column to sort by. Default "carbsPerDollar".

No output schema declared.

No examples provided.

heat-adjustment ~109

Estimate how temperature and humidity will slow your race pace and change your fluid needs. Returns adjusted pace, slowdown percent, dew point, risk level, and fueling note.

NameTypeReqDescription
distanceMilesnumberyesRace distance in miles.
humiditynumberyesRelative humidity as a percentage, 0-100.
paceSecondsPerMilenumberyesYour goal pace in seconds per mile (cool-weather pace).
tempFnumberyesAir temperature at race time in degrees Fahrenheit.

No output schema declared.

No examples provided.

hydration ~95

Estimate fluid and sodium needs for a race or long run based on body weight, duration, intensity, temperature, and humidity.

NameTypeReqDescription
bodyWeightLbsnumberyesBody weight in pounds.
durationMinutesnumberyesRun or race duration in minutes.
humiditynumberyesRelative humidity, 0-100.
intensitystringyesEffort level.
tempFnumberyesTemperature in Fahrenheit.

No output schema declared.

No examples provided.

pace-calculator ~106

Given any two of distance, total time, or pace-per-mile, calculate the third. Returns pace per mile, per km, splits, and speed.

NameTypeReqDescription
distanceMilesnumber–Required for mode "pace" or "time".
modestringyesWhich field to solve for.
paceSecondsPerMilenumber–Required for mode "time" or "distance".
totalSecondsnumber–Required for mode "pace" or "distance".

No output schema declared.

No examples provided.

race-time-predictor ~88

Predict your finish time at common distances (5K through 100 miles) from a recent race result using the Riegel formula.

NameTypeReqDescription
exponentnumber–Riegel exponent. Default 1.06.
knownDistanceMilesnumberyesDistance of your recent race, in miles.
knownTimeSecondsnumberyesFinish time for that race, in total seconds.

No output schema declared.

No examples provided.

Install

How do I install the io.github.codymcc4/fuelcenter MCP server?

io.github.codymcc4/fuelcenter is a hosted endpoint at https://fuelcenter.co/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 · fuelcenter.co

# add to Claude Code
claude mcp add --transport http codymcc4-fuelcenter 'https://fuelcenter.co/api/mcp'
Common questions

What is the io.github.codymcc4/fuelcenter MCP server?

io.github.codymcc4/fuelcenter is an MCP server listed in the public MCP registry as io.github.codymcc4/fuelcenter. Marathon fueling, pace, hydration, heat, carb-loading, and gel-comparison calculators. This page covers its hosted endpoint (https://fuelcenter.co/api/mcp).

Is the io.github.codymcc4/fuelcenter MCP server safe to use?

io.github.codymcc4/fuelcenter scores 85 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 io.github.codymcc4/fuelcenter MCP server expose?

io.github.codymcc4/fuelcenter exposes 7 tools: fueling-plan, race-time-predictor, pace-calculator, heat-adjustment, hydration, and 2 more. Their descriptions and schemas cost roughly 833 tokens of context every time the server is loaded.

Does the io.github.codymcc4/fuelcenter MCP server require authentication?

No. We connected to io.github.codymcc4/fuelcenter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.codymcc4/fuelcenter MCP server still maintained?

io.github.codymcc4/fuelcenter is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.codymcc4/fuelcenter MCP server?

VerifyMCP ran 13 checks on io.github.codymcc4/fuelcenter, 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.