Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Yardstick Outfitters

REMOTE · YARDSTICKOUTFITTERS.COM

Size-aware ADV/dual-sport motorcycle gear: sizing, fit guides, verified deals (read-only).

+4 this week 78 Trust /100

Last scanned (19 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 586 tokens (~146/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “size_recommendation” rewrote its description, which is the text the model reads security
    • Schema quality: 127 → 146 ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://yardstickoutfitters.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yardstickoutfitters.com CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 70fa8bf0d7c1247613fb3a17e217b9ae
SANs: yardstickoutfitters.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of yardstickoutfitters.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
yardstickoutfitters.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://yardstickoutfitters.com/mcp Verified 200
http (plaintext) http://yardstickoutfitters.com/mcp HTTPS enforced 301 https://yardstickoutfitters.com/mcp
MCP tools · 4 exposed · ~495 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
about_yardstick ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

current_deals ~145

Verified motorcycle gear deals for every riding style, with price, retailer's listed price (the store's own comparison price, not verified by us), percent below that listed price, retailer link, as-of time, and optional made_in_usa (official-source only). Optional filters including made_in_usa.

NameTypeReqDescription
brandstring––
categorystring–e.g. helmet, jacket, pants, boots
limitinteger––
made_in_usaboolean–If true, only return deals tagged Made in USA from official brand sources (FTC all-or-virtually-all; never inferred)
max_pricenumber–USD

No output schema declared.

No examples provided.

list_fit_guides ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

size_recommendation ~298

Requires the rider's own free Yardstick Outfitters account: call with their signed-in session; otherwise it returns status requires_account and a free sign-up link (https://yardstickoutfitters.com/account/signin/?new=1) to pass on. Recommend a size for a motorcycle jacket, pants, boots, helmet or gloves, using only the brand's own official size chart (for example Alpinestars, Klim, Dainese, Aerostich, Sidi, Forma and some Bell, Klim, Nexx, Shark and Alpinestars helmets; see /fit-confidence/). If we have no verified official chart for that brand and item (for example REV'IT!, Shoei, Gaerne), it returns status no_chart with no size and the how-to-measure guide; it never uses a generic chart and never invents sizing. Uses chest (jacket), waist (pants), head circumference (helmet), hand circumference (gloves) or foot length (boots).

NameTypeReqDescription
brandstringyesBrand, e.g. Klim, Alpinestars, Shoei
measurementsobjectyesRider measurements
product_namestring–Exact model, e.g. Klim Krios Pro or Bell MX-9 Adventure (needed for per-model helmet charts)
product_typestringyes–
unitsstring–Units for all measurements (default: guessed from values)

No output schema declared.

No examples provided.

Install

How do I install the Yardstick Outfitters MCP server?

Yardstick Outfitters is a hosted endpoint at https://yardstickoutfitters.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · yardstickoutfitters.com

# add to Claude Code
claude mcp add --transport http com-yardstickoutfitters-mcp 'https://yardstickoutfitters.com/mcp'
Common questions

What is the Yardstick Outfitters MCP server?

Yardstick Outfitters is an MCP server listed in the public MCP registry as com.yardstickoutfitters/mcp. Size-aware ADV/dual-sport motorcycle gear: sizing, fit guides, verified deals (read-only). This page covers its hosted endpoint (https://yardstickoutfitters.com/mcp).

Is the Yardstick Outfitters MCP server safe to use?

Yardstick Outfitters scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Yardstick Outfitters MCP server expose?

Yardstick Outfitters exposes 4 tools: size_recommendation, list_fit_guides, current_deals, about_yardstick. Their descriptions and schemas cost roughly 495 tokens of context every time the server is loaded.

Does the Yardstick Outfitters MCP server require authentication?

No. We connected to Yardstick Outfitters without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Yardstick Outfitters MCP server still maintained?

Yardstick Outfitters is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Yardstick Outfitters MCP server?

VerifyMCP ran 13 checks on Yardstick Outfitters, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.