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

yardstick-outfitters

https://yardstickoutfitters.com

Registry code: cdd741becc581c1e

api record

Read-only tools from Yardstick Outfitters, a size-aware motorcycle gear (ADV/dual-sport) deal finder. Use size_recommendation for brand sizing, list_fit_guides for guides, current_deals for verified deals, about_yardstick for the service. Always show the link and attribution to the user.

endpoint
https://yardstickoutfitters.com/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 yardstick-outfitters live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is yardstick-outfitters free to use?
Yes — the hub reached it with no key and no payment.
What tools does yardstick-outfitters have?
4 tools: size_recommendation, about_yardstick, list_fit_guides, current_deals.
Is yardstick-outfitters 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
1,932ms

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
3 open 1 never probed 3 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_yardstick open 50m ago

    Short description of Yardstick Outfitters, waitlist link and policy links.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_fit_guides open 50m ago

    List Yardstick Outfitters' motorcycle gear fit guides with URLs and one-line summaries.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • current_deals open 50m ago

    Verified ADV and dual-sport motorcycle gear deals with price, regular price, retailer link, as-of time, and optional made_in_usa (official-source only). Optional filters including made_in_usa.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "brand": {
          "type": "string"
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1
        },
        "category": {
          "type": "string",
          "description": "e.g. helmet, jacket, pants, boots"
        },
        "max_price": {
          "type": "number",
          "description": "USD"
        },
        "made_in_usa": {
          "type": "boolean",
          "description": "If true, only return deals tagged Made in USA from official brand sources (FTC all-or-virtually-all; never inferred)"
        }
      }
    }
    arguments 25 lines
  • size_recommendation unknown never probed

    Recommend a size for a motorcycle jacket, pants, boots, helmet or gloves from a given brand, using only Yardstick's published fit data (Alpinestars, Dainese, Klim, REV'IT!, Shoei, Gaerne). Uncovered brands/items return a plain "not covered" answer and the how-to-measure guide; it never invents sizing. Uses chest (jacket), waist (pants), head circumference (helmet), hand circumference (gloves) or foot length (boots).

    mcp-tool

    {
      "type": "object",
      "required": [
        "brand",
        "product_type",
        "measurements"
      ],
      "properties": {
        "brand": {
          "type": "string",
          "description": "Brand, e.g. Klim, Alpinestars, Shoei"
        },
        "units": {
          "enum": [
            "in",
            "cm"
          ],
          "type": "string",
          "description": "Units for all measurements (default: guessed from values)"
        },
        "measurements": {
          "type": "object",
          "properties": {
            "foot": {
              "type": "number",
              "description": "Foot length"
            },
            "hand": {
              "type": "number",
              "description": "Hand circumference"
            },
            "head": {
              "type": "number",
              "description": "Head circumference"
            },
            "chest": {
              "type": "number"
            },
            "waist": {
              "type": "number"
            },
            "height": {
              "type": "number"
            },
            "inseam": {
              "type": "number"
            },
            "weight": {
              "type": "number"
            }
          },
          "description": "Rider measurements"
        },
        "product_type": {
          "enum": [
            "jacket",
            "pants",
            "boots",
            "helmet",
            "gloves"
          ],
          "type": "string"
        }
      }
    }
    arguments 65 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 cdd741becc581c1e.

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