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

upfit

https://www.upfit.mobile

Registry code: 827565534c0b9d9b

api record

Read-only bodyweight workout builder and exercise form cues from the Upfit iPhone app.

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

endpoint
https://www.upfit.mobile/mcp
protocol
http-sse ·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 upfit live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is upfit free to use?
Yes — the hub reached it with no key and no payment.
What tools does upfit have?
4 tools: get_exercise_form_cues, build_home_workout, about_upfit, list_exercises.
Is upfit 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
197ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 4 tools
2 open 2 never probed 2 of 4 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.

  • about_upfit open 1h ago

    Use this when the user asks what Upfit is, how it works, or what it cannot check. Returns a short description and links to Upfit's own explanation pages.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_exercises open 1h ago

    Use this when the user wants to see which bodyweight exercises Upfit can run. Returns the enabled exercises with Upfit's own difficulty rating (1 easiest to 9 hardest) and, where Upfit documents it, how you stand to the phone (facing it, side-on to it, or on the floor). Optional difficulty filters.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "max_difficulty": {
          "type": "integer",
          "maximum": 9,
          "minimum": 1,
          "description": "Only exercises at or below this difficulty."
        },
        "min_difficulty": {
          "type": "integer",
          "maximum": 9,
          "minimum": 1,
          "description": "Only exercises at or above this difficulty."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • get_exercise_form_cues unknown never probed

    Use this when the user asks what Upfit's coach says or checks for a specific bodyweight exercise (for example 'squat' or 'low plank hold'). Returns the app's real spoken coach lines for that exercise and, for exercises that have an Upfit page, what the camera checks and does not check. If the exercise is unknown it says so and lists close matches. It never invents form advice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "exercise"
      ],
      "properties": {
        "exercise": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Exercise name, such as 'squat', 'jumping jacks' or 'low plank hold'."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • build_home_workout unknown 1h ago

    Use this when the user wants a bodyweight, no-equipment home workout session. Builds a 15-move session the way the Upfit iPhone app builds one: 2 warm-ups, 10 main moves balanced around the chosen level, then 3 harder finishers. Returns each move's name, phase, set length and rest. Read-only; collects no personal data and needs no body measurements. The same seed returns the same session.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "level"
      ],
      "properties": {
        "seed": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 64
            },
            {
              "type": "number"
            }
          ],
          "description": "Optional. Any word or number; the same seed rebuilds the same session. Leave out for a fresh random one."
        },
        "level": {
          "enum": [
            "beginner",
            "intermediate",
            "advanced"
          ],
          "type": "string",
          "description": "Training experience: beginner, intermediate or advanced."
        }
      },
      "additionalProperties": false
    }
    arguments 31 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 827565534c0b9d9b.

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

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.