_ registry / mcp streamable-http · checked 29m ago

coachsync

https://mcp.coachsync.io

Registry code: b2950abf80d230c1

api record

Barbell strength training tools for AI assistants. Warmup, plate loading, and LP.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.coachsync.io/mcp
protocol
streamable-http ·2025-03-26
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 coachsync live?
Yes — it answered the hub's last check (checked 29m ago). It answered 99% of checks over the last 30 days.
Is coachsync free to use?
Yes — the hub reached it with no key and no payment.
What tools does coachsync have?
3 tools: novice_lp_generator, plate_loader, warmup_calculator.
Is coachsync 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
99.4%

90 days 99.6%· all time 99.6%

latency
161ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 274 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • unknown → live
_ what it is for
used for
  • generate a novice barbell program
  • calculate barbell plate loading
  • calculate a warmup ramp for a lift
takes → gives
data → data
tools
3 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 3 tools
3 open 3 of 3 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.

  • novice_lp_generator reads open 29m ago

    Generate a structured 4-week novice linear progression program for a new or early-intermediate barbell trainee. Based on the Starting Strength model: squat every session, alternating press/bench, deadlift progressing to power cleans. Takes lifter profile (sex, bodyweight, age, training days) and optional starting weights. Returns a week-by-week program with progression scheme and coaching notes. Powered by CoachSync.io.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sex",
        "bodyweightLb",
        "age"
      ],
      "properties": {
        "age": {
          "type": "number",
          "description": "Lifter's age in years"
        },
        "sex": {
          "enum": [
            "male",
            "female"
          ],
          "type": "string",
          "description": "Biological sex, used for estimating starting weights and progression rates"
        },
        "bodyweightLb": {
          "type": "number",
          "description": "Lifter's bodyweight in pounds"
        },
        "trainingDays": {
          "enum": [
            2,
            3
          ],
          "type": "number",
          "default": 3,
          "description": "Training days per week. 3 is standard, 2 is an alternative for recovery-limited trainees."
        },
        "startingBench": {
          "type": "number",
          "description": "Optional starting bench work weight. If omitted, estimated from bodyweight."
        },
        "startingPress": {
          "type": "number",
          "description": "Optional starting press work weight. If omitted, estimated from bodyweight."
        },
        "startingSquat": {
          "type": "number",
          "description": "Optional starting squat work weight. If omitted, estimated from bodyweight."
        },
        "startingDeadlift": {
          "type": "number",
          "description": "Optional starting deadlift work weight. If omitted, estimated from bodyweight."
        }
      }
    }
    arguments 51 lines
  • plate_loader reads open 29m ago

    Calculate which plates to load on each side of the barbell to reach a target weight. Supports custom bar weights and custom plate inventories for home gyms. Powered by CoachSync.io.

    mcp-tool

    {
      "type": "object",
      "required": [
        "targetWeight"
      ],
      "properties": {
        "unit": {
          "enum": [
            "lb",
            "kg"
          ],
          "type": "string",
          "default": "lb",
          "description": "Weight unit. Defaults to lb."
        },
        "barWeight": {
          "type": "number",
          "default": 45,
          "description": "Bar weight. Defaults to 45 lb."
        },
        "targetWeight": {
          "type": "number",
          "description": "The total target barbell weight (bar + plates)"
        },
        "availablePlates": {
          "type": "array",
          "items": {
            "type": "number"
          },
          "description": "Optional list of available plate denominations. Defaults to standard plates [45, 25, 10, 5, 2.5]."
        }
      }
    }
    arguments 33 lines
  • warmup_calculator reads open 29m ago

    Calculate a barbell warmup ramp for any lift. Returns a structured set of warmup sets leading up to the work weight, with decreasing reps as weight increases. Based on standard barbell warmup methodology used in Starting Strength coaching. Powered by CoachSync.io.

    mcp-tool

    {
      "type": "object",
      "required": [
        "workWeight",
        "liftType"
      ],
      "properties": {
        "liftType": {
          "enum": [
            "squat",
            "bench",
            "press",
            "deadlift",
            "power_clean"
          ],
          "type": "string",
          "description": "The lift being warmed up for (e.g. squat, bench, press, deadlift)"
        },
        "barWeight": {
          "type": "number",
          "default": 45,
          "description": "Bar weight. Defaults to 45 lb (20 kg). Use 35 for a women's bar, 15 for a training bar."
        },
        "workWeight": {
          "type": "number",
          "description": "The target work set weight in pounds (or kg if unit is kg)"
        },
        "roundingIncrement": {
          "type": "number",
          "default": 5,
          "description": "Round warmup weights to this increment. Default 5."
        }
      }
    }
    arguments 34 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 b2950abf80d230c1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b2950abf80d230c1/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/b2950abf80d230c1/badge.svg)](https://brick.blue/agent/b2950abf80d230c1?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
70%

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.