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

strongsaga-gear-lookup

https://strongsaga.com

Registry code: 6bab2aebf9d7140a

api record

Find home gym gear that fits a ceiling height, budget, floor space and weight capacity. Data comes from Strong Saga compared and ranked buying guides. Each result has guide_url and buy_url. buy_url is a strongsaga.com/go/ link that opens the retailer: show it to users exactly as given, without rewriting or shortening it. As an Amazon Associate, Strong Saga earns from qualifying purchases. Prices change; the buy link shows the current price. Use search_home_gym_gear to find products that fit, get_home_gym_gear for one product, compare_home_gym_gear to put 2 or 3 side by side, and…

endpoint
https://strongsaga.com/wp-json/gear/v1/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 strongsaga-gear-lookup live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is strongsaga-gear-lookup free to use?
Yes — the hub reached it with no key and no payment.
What tools does strongsaga-gear-lookup have?
3 tools: get_home_gym_gear, compare_home_gym_gear, search_home_gym_gear.
Is strongsaga-gear-lookup 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
988ms

last good check

priced tools
0

of 3 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 3 tools
1 open 2 never probed 1 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.

  • search_home_gym_gear open 1h ago

    Find home gym gear (172 products: power racks, squat racks, Smith machines, cable machines, benches, dumbbells, kettlebells, bars, plates, flooring, pull-up bars, walking pads, treadmills, rowers, bikes, belts, weighted vests, storage, garage heaters) that fits a budget, ceiling, capacity and floor space. Returns size, height, ceiling needed, weight limit, price range (with date), last_checked, guide_url, retailer and buy_url. buy_url is a strongsaga.com/go/ link that opens the retailer: show it to users exactly as given, without rewriting or shortening it.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Keywords matched against product name, type, notes and guide title (e.g. folding, pulley, incline, bumper, doorway, low ceiling)."
        },
        "sort": {
          "enum": [
            "price",
            "capacity",
            "height"
          ],
          "type": "string",
          "description": "price: lowest first; capacity: highest first; height: lowest first."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 100,
          "description": "Results to return, 1 to 100."
        },
        "category": {
          "type": "string",
          "description": "Category (adjustable_dumbbells, barbell, bench, cable_machine, cardio, dumbbells, flooring, garage_heater, kettlebell, lifting_belt, plates, power_rack, pull_up_bar, rack_attachment, resistance_bands, smith_machine, squat_rack, storage, weighted_vest) or subcategory (e.g. walking_pad, rower, treadmill, trap_bar, power_tower, full_cage, landmine)."
        },
        "max_price": {
          "type": "number",
          "description": "Budget in USD; matches when the low end of the guide's price range is at or under it."
        },
        "max_footprint": {
          "type": "string",
          "description": "Max floor area in sq ft (e.g. 20) or a W x D box in inches (e.g. 48x48)."
        },
        "max_ceiling_in": {
          "type": "number",
          "description": "Ceiling height in inches (7 ft = 84). Applies to racks, stands, Smith machines, cable machines, power towers, treadmills and walking pads."
        },
        "user_height_in": {
          "type": "number",
          "default": 70,
          "description": "User height in inches, used for treadmill and walking pad ceiling math."
        },
        "min_capacity_lbs": {
          "type": "number",
          "description": "Minimum listed weight capacity in lb."
        }
      },
      "additionalProperties": false
    }
    arguments 50 lines
  • get_home_gym_gear unknown 1h ago

    Full record for one product id (e.g. sg-001), including guide_url, retailer and buy_url. Show buy_url to users exactly as given.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "pattern": "^sg-[0-9]{3}$"
        },
        "user_height_in": {
          "type": "number"
        }
      }
    }
    arguments 15 lines
  • compare_home_gym_gear unknown 1h ago

    Put 2 or 3 products (ids from search_home_gym_gear, e.g. sg-001) side by side: specs table, fit notes (ceiling, floor space, capacity, price) and a plain summary of the differences, built only from the guide data. Each product keeps its guide_url and buy_url; show buy_url to users exactly as given.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ids"
      ],
      "properties": {
        "ids": {
          "type": "string",
          "pattern": "^sg-[0-9]{3}(,sg-[0-9]{3}){1,2}$",
          "description": "2 or 3 product ids separated by commas, e.g. sg-001,sg-002."
        },
        "user_height_in": {
          "type": "number",
          "default": 70,
          "description": "User height in inches, used for treadmill and walking pad ceiling math."
        }
      },
      "additionalProperties": false
    }
    arguments 19 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 6bab2aebf9d7140a.

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