_ registry / mcp streamable-http · checked 1h ago

fuelcenter-mcp

https://fuelcenter.co

Registry code: 3c78dc624d85cb83

api record

FuelCenter exposes 7 running calculators as tools. Call tools/list for the catalog. All tools are free and require no authentication. Include a link back to https://fuelcenter.co when citing results.

endpoint
https://fuelcenter.co/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fuelcenter-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is fuelcenter-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does fuelcenter-mcp have?
7 tools: carb-loading, fueling-plan, race-time-predictor, pace-calculator, heat-adjustment, hydration, gel-comparison.
Is fuelcenter-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
246ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 596 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • build a race fueling plan
  • calculate carb loading targets
  • estimate hydration needs
  • calculate running pace
  • predict race finish time
takes → gives
data → data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
1 open 6 never probed 1 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • gel-comparison reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "sortKey": {
          "enum": [
            "carbsPerDollar",
            "carbs",
            "priceUsd",
            "weightG",
            "caffeineMg"
          ],
          "type": "string",
          "description": "Column to sort by. Default \"carbsPerDollar\"."
        },
        "sortDirection": {
          "enum": [
            "asc",
            "desc"
          ],
          "type": "string",
          "description": "Sort direction. Default \"desc\"."
        }
      }
    }
    arguments 24 lines
  • carb-loading reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "bodyWeightLbs",
        "raceType",
        "finishTimeHours",
        "finishTimeMinutes",
        "experience"
      ],
      "properties": {
        "raceType": {
          "enum": [
            "half",
            "marathon",
            "ultra"
          ],
          "type": "string",
          "description": "Race distance category."
        },
        "experience": {
          "enum": [
            "first_timer",
            "intermediate",
            "experienced",
            "elite"
          ],
          "type": "string",
          "description": "Runner experience level."
        },
        "hasGIIssues": {
          "type": "boolean",
          "description": "Whether the runner has a sensitive stomach. Default false."
        },
        "bodyWeightLbs": {
          "type": "number",
          "description": "Body weight in pounds."
        },
        "finishTimeHours": {
          "type": "number",
          "description": "Expected finish time, hours portion."
        },
        "finishTimeMinutes": {
          "type": "number",
          "description": "Expected finish time, minutes portion."
        }
      }
    }
    arguments 47 lines
  • fueling-plan reads unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "hours",
        "minutes",
        "intensity",
        "gelKey"
      ],
      "properties": {
        "hours": {
          "type": "number",
          "description": "Race or run duration, hours portion."
        },
        "buffer": {
          "type": "number",
          "description": "Minutes of buffer at start and end where no gel is taken. Default 5."
        },
        "gelKey": {
          "enum": [
            "sis_beta_fuel",
            "maurten_100",
            "maurten_160",
            "precision_pf30",
            "gu_energy",
            "gu_roctane",
            "tailwind",
            "spring_energy",
            "carbs_fuel",
            "neversecond_c30",
            "huma_chia"
          ],
          "type": "string",
          "description": "Gel product key. See /api/tools/gel-comparison for full catalog."
        },
        "minutes": {
          "type": "number",
          "description": "Race or run duration, minutes portion."
        },
        "drinkMix": {
          "type": "boolean",
          "description": "Whether the runner uses a carbohydrate drink mix. Default false."
        },
        "intensity": {
          "enum": [
            "easy",
            "easy_moderate",
            "moderate_hard",
            "race_day"
          ],
          "type": "string",
          "description": "Effort level."
        },
        "targetCPH": {
          "type": "number",
          "description": "Target carbs per hour. If omitted, default is derived from guideline."
        },
        "experience": {
          "enum": [
            "standard",
            "experienced"
          ],
          "type": "string",
          "description": "Runner experience with fueling. Default \"standard\"."
        },
        "drinkCarbsTotal": {
          "type": "number",
          "description": "Total grams of carbs from drink mix across the run. Default 0."
        }
      }
    }
    arguments 70 lines
  • race-time-predictor reads unknown 8h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "knownDistanceMiles",
        "knownTimeSeconds"
      ],
      "properties": {
        "exponent": {
          "type": "number",
          "description": "Riegel exponent. Default 1.06."
        },
        "knownTimeSeconds": {
          "type": "number",
          "description": "Finish time for that race, in total seconds."
        },
        "knownDistanceMiles": {
          "type": "number",
          "description": "Distance of your recent race, in miles."
        }
      }
    }
    arguments 21 lines
  • pace-calculator reads unknown 8h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "mode"
      ],
      "properties": {
        "mode": {
          "enum": [
            "pace",
            "time",
            "distance"
          ],
          "type": "string",
          "description": "Which field to solve for."
        },
        "totalSeconds": {
          "type": "number",
          "description": "Required for mode \"pace\" or \"distance\"."
        },
        "distanceMiles": {
          "type": "number",
          "description": "Required for mode \"pace\" or \"time\"."
        },
        "paceSecondsPerMile": {
          "type": "number",
          "description": "Required for mode \"time\" or \"distance\"."
        }
      }
    }
    arguments 29 lines
  • heat-adjustment reads unknown 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "paceSecondsPerMile",
        "distanceMiles",
        "tempF",
        "humidity"
      ],
      "properties": {
        "tempF": {
          "type": "number",
          "description": "Air temperature at race time in degrees Fahrenheit."
        },
        "humidity": {
          "type": "number",
          "description": "Relative humidity as a percentage, 0-100."
        },
        "distanceMiles": {
          "type": "number",
          "description": "Race distance in miles."
        },
        "paceSecondsPerMile": {
          "type": "number",
          "description": "Your goal pace in seconds per mile (cool-weather pace)."
        }
      }
    }
    arguments 27 lines
  • hydration reads unknown 15h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "bodyWeightLbs",
        "durationMinutes",
        "intensity",
        "tempF",
        "humidity"
      ],
      "properties": {
        "tempF": {
          "type": "number",
          "description": "Temperature in Fahrenheit."
        },
        "humidity": {
          "type": "number",
          "description": "Relative humidity, 0-100."
        },
        "intensity": {
          "enum": [
            "easy",
            "moderate",
            "hard",
            "race"
          ],
          "type": "string",
          "description": "Effort level."
        },
        "bodyWeightLbs": {
          "type": "number",
          "description": "Body weight in pounds."
        },
        "durationMinutes": {
          "type": "number",
          "description": "Run or race duration in minutes."
        }
      }
    }
    arguments 38 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3c78dc624d85cb83.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3c78dc624d85cb83/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3c78dc624d85cb83/badge.svg)](https://brick.blue/agent/3c78dc624d85cb83?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.