UCP Checker
Back to status
samimotorcycle.com icon
UCP Score

UCP Score for samimotorcycle.com

UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.

✓Verified
A90/100
Analyzed Oct 9, 2026 · 2 recommendations ·Wix · v2026-04-08 upgrade
90
/ 100
UCP Score
A

samimotorcycle.com publishes a conforming profile with broad capability coverage.

Agent Discovery100
UCP Conformance88
Capability Coverage81
Working

Agent Discovery is solid (100/100).

Start Here

Publish the public keys agents use to check your messages → Move to the latest UCP protocol version

Verified

samimotorcycle.com publishes a valid UCP profile, with minor schema warnings.

Latency
451ms
Version
2026-04-08
Robots.txt
Allowed ✅

Top Priorities

1
Publish the public keys agents use to check your messages

Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.

Medium impact Medium effort
2
Move to the latest UCP protocol version

Your profile declares a valid but older protocol version. A newer one is published.

Low impact Low effort

Impact & Effort Matrix

Prioritised recommendations by expected impact and implementation effort

Quick Wins(0)

High impact, low effort

  • No items
Strategic Investments(0)

High impact, high effort

  • No items
Incremental Gains(1)

Medium impact & effort

  • Publish the public keys agents use to check your messages
Consider Later(1)

Lower priority

  • Move to the latest UCP protocol version

How you compare on Wix

Response time benchmarked against 7,459 Wixes we monitor.

fastWix median 410msslow
Your store
451ms
Wix percentile
Below median
Faster than 34% of Wix stores
Cohort range
365–479ms
p25 to p75 (middle half)

Recommendations

All improvements ranked by priority, with evidence and actionable fixes.

1

Publish the public keys agents use to check your messages

Medium impact Medium effort

Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.

Why it matters

Agents use these keys to check that checkout messages really came from you. A store that takes payment through the agent needs them. A store that sends the buyer to its own checkout page can manage without them for now.

Show fix

Create an Ed25519 key pair. Add the public key to a "keys" list at the top level of your UCP profile, as in the example, and keep the private key on your server. Replace the key once a year, giving each new key its own "kid".

{
  "keys": [
    {
      "kty": "OKP",
      "crv": "Ed25519",
      "x": "<base64url-encoded-public-key>",
      "kid": "key-2026-04",
      "alg": "EdDSA"
    }
  ],
  "ucp": { ... }
}
UCP_MISSING_SIGNING_KEYS
2

Move to the latest UCP protocol version

Low impact Low effort

Your profile declares a valid but older protocol version. A newer one is published.

Why it matters

Older versions stay valid (agents use the version you declare), but newer abilities (embedded checkout, agent payment mandates, linked customer accounts, card authentication, payment terms and store location lookup) only work against the latest version. The profile itself barely changes: the signing keys move to a root-level "keys" list, and the rest of the update is in what capabilities can say.

Show fix

Set the version to 2026-08-25 and publish your public keys as a root-level "keys" list. The older "signing_keys" field is still accepted, but "keys" is the one every verifier reads.

"ucp": {
  "version": "2026-08-25",
  ...
},
"keys": [ ... ]   // beside "ucp", not inside it
UCP_VERSION_OUTDATED

Full Check Breakdown

Every signal we evaluate, grouped by category.

Agent Discovery8/8 passed

Can AI agents find your store and its UCP profile?

  • HTTPSCore

    Profile served over a secure connection.

    Profile URL uses https://

    Why it matters

    Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.

  • UCP profile reachableCore

    Profile fetched OK from /.well-known/ucp.

    HTTP 200

    Why it matters

    Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.

  • AI bot accessCore

    robots.txt allows agent crawlers to fetch the profile.

    robots.txt allows /.well-known/ucp

    Why it matters

    Agents respect robots.txt. Even a published profile gets ignored if the file is disallowed for known agent user-agents.

  • llms.txtExperimental

    Hand-written brief at /llms.txt for AI agents.

    Found at /llms.txt

    Why it matters

    Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.

  • sitemap.xmlCore

    XML sitemap published at /sitemap.xml.

    Found at /sitemap.xml

    Why it matters

    Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.

  • Open Graph tagsCore

    OG meta tags on the homepage.

    og:title and og:type/url present

    Why it matters

    OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.

  • Organization schema (JSON-LD)Core

    Schema.org Organization (or OnlineStore) JSON-LD on homepage.

    Organization-typed JSON-LD detected

    Why it matters

    Gives agents a structured representation of your brand identity — used to verify you are who your profile claims you are.

  • Mobile viewport metaCore

    Viewport meta tag for mobile rendering.

    <meta name="viewport"> present

    Why it matters

    Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.

UCP Conformance2/4 passed

Does your profile meet the published spec?

  • Profile passes schema validationCore

    Profile structure conforms to the published UCP spec.

    No structural errors

    Why it matters

    Strict UCP agents reject profiles with structural errors. The error code in the diagnostic shows which field failed.

  • Protocol version present and well-formedCore

    ucp.version follows YYYY-MM-DD format.

    Version: 2026-04-08

    Why it matters

    UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.

  • Signing keys publishedCore

    Root-level keys array (canonical since 2026-07-12; legacy signing_keys also accepted) for response verification.

    No signing_keys at root (common for managed/redirect-checkout stores)

    Why it matters

    Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.

  • No validation warningsCore

    Profile passes structural and field-level rules.

    1 warning

    Why it matters

    Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.

Capability Coverage3/4 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

    3 of 6 capability families detected: Checkout, Cart Management, Catalog. A family counts once however many namespaces or extensions declare it.

    Why it matters

    Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.

  • Checkout capabilityCore

    Store declares a checkout-namespaced capability.

    dev.ucp.shopping.checkout detected

    Why it matters

    Without a checkout capability, agents can browse but can't complete a purchase end-to-end.

  • Transports declaredInterop

    Service transports (REST/MCP/A2A/Embedded) declared on services.

    REST, MCP

    Why it matters

    Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.

  • Payment handlersCore

    Tokenized payment handlers registered for in-conversation checkout.

    Empty array: checkout-link redirect strategy

    Why it matters

    Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.

/llms.txt content

The plain-text brief this store publishes to AI agents. Captured on the most recent check.

4.3 KB518dcaddafc0017f
# sami-motorcycle
> サミモーターサイクルは、日常的なエンジンのオーバーホールから一般的な修理、フルオーバーホール、チューニングまで幅広く対応するバイクショップです。国内では入手困難なパーツの取り寄せも可能で、知識のない方にも丁寧に説明してから作業を行います。エンジンの状態や予算に合わせた最適なオーバーホールメニューを提案し、部品単位での分解・清掃・再組み立てにより新品時の性能回復を目指します。また、中古車両の販売や通信販売も行っており、全国からの修理依頼も受け付けています。

## Homepage link
- [home](https://www.samimotorcycle.com/)

## AI エージェントによるアクセス

このサイトは Wix で作成されており、エージェント AI によるアクセス用の MCP (Model Context Protocol) に対応しています。AI エージェントは直接接続して、公開中の最新のサイトコンテンツを取得できます。スクレイピングは不要です。

- [**サイト MCP エンドポイント**](https://www.samimotorcycle.com/_api/mcp)
- [**Wix MCP ドキュメンテーション**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)

## 利用可能な MCP ツール

### GetBusinessDetails
ビジネスとサイトの詳細(時間帯(タイムゾーン)、メールアドレス、電話番号、住所など)を取得します。- パラメータは必要ありません。

### SearchInSite
サイト内の情報を検索します。
- **searchTerm** - サイト内で検索する語句。

### SearchSiteApiDocs
このサイトにインストールされている Wix ビジネスソリューションの API ドキュメントを取得し、AI クライアントに API の使用方法を通知します。商品とサービスのクエリにこのツールを使用します(SearchInSite の代わりに)。
- **searchTerm** - サイトの API ドキュメント内で検索する語句。

### GenerateVisitorToken
新しいサイト訪問者セッションを作成し、サイト用のサイト訪問者アクセストークンを取得します。コンテキストに訪問者トークンがまだない場合は、CallWixSiteAPI リクエストを行う前に呼び出す必要があります。
- パラメータは必要ありません。

### CallWixSiteAPI
サイト上で API メソッドを呼び出し、サイト訪問者に代わってアクション(サイトデータのクエリ、プライベート予約を行う、購入を開始するなど)を実行します。
- **visitorToken** - サイト訪問者アクセストークン。利用できない場合は、最初に GenerateVisitorToken を使用します。
- **url** - 呼び出す API メソッドの絶対 URL(例:https://www.wixapis.com/...)。SearchSiteApiDocs を使用して取得します。
- **method** - API 呼び出しに使用する HTTP メソッド。
- **body** - 有効な JSON 文字列としてのリクエストボディ。

### ReadFullDocsArticle
Wix開発者ドキュメンテーションポータルから完全な記事を読み出します。
- **articleUrl** - Wix 開発者ドキュメンテーションポータル内の記事の URL。

### ReadFullDocsMethodSchema
Wix APIメソッドの完全なスキーマを読み出します。実際のメソッドを CallWixSiteAPI で呼び出す前に、先にこのメソッドを呼び出す必要があります。
- **articleUrl** - Wix API メソッドのリファレンス記事の URL。

## AI + MCPでサイト訪問者ができること

- ビジネスの詳細(連絡先情報、ビジネス拠点、営業時間)を取得する
- 提供されている商品 / サービスを見つける
- サービスや予約を行う
- 購入を開始し、死払い手続きを完了するためにサイトに誘導される
- サイトを閲覧することなく質問し、関連する回答を得る

## メモ

- MCP エンドポイントへの接続に認証は不要です
- サイトでアクセス可能な公開情報のみ利用できます
- コンテンツは常にリアルタイムで最新です
- ツール更新を受け取るには、ツール更新通知を受領した際に tools/list の呼び出しを実装してください。
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Cart ✓ Bound 2026-04-08
Checkout ✓ Bound 2026-04-08
Fulfillment Extension ✓ Bound 2026-04-08
Catalog Lookup ✓ Bound 2026-04-08
Catalog Search ✓ Bound 2026-04-08

Technical Vitals

Technical details for this UCP endpoint
UCP Status Verified
Endpoint https://samimotorcycle.com/.well-known/ucp
HTTP Status 200
UCP Version 2026-04-08
Transports REST, MCP
Last Observed
Last Full Index

Embed your UCP Score

Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.

UCP Score for samimotorcycle.com badge for https://ucpchecker.com/score/samimotorcycle.comLive preview
Markdown
[![UCP Score for samimotorcycle.com](https://ucpchecker.com/score/samimotorcycle.com/badge.svg)](https://ucpchecker.com/score/samimotorcycle.com)
HTML
<a href="https://ucpchecker.com/score/samimotorcycle.com"><img src="https://ucpchecker.com/score/samimotorcycle.com/badge.svg" alt="UCP Score for samimotorcycle.com"></a>
New · Early access open
Is samimotorcycle.com yours? Claim it & monitor it daily

Prove ownership with one DNS record and the new monitoring dashboard watches it every day — score trends, break alerts, staging drift and a watchlist that benchmarks you against the field. Free while in beta.

Start monitoring →

This score reflects data from the most recent crawl. Run a fresh check to update, or read the methodology to see how each signal is scored.

Save this report

Track samimotorcycle.com's UCP score over time. We'll re-run the full check weekly and email you if the score drops, a capability regresses, or status flips.

Free. One email when something changes — no marketing. Privacy.