UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
toua-shoji.com publishes a conforming profile with broad capability coverage.
Agent Discovery is solid (100/100).
Fix broken spec or schema URLs → Publish the public keys agents use to check your messages → Move to the latest UCP protocol version
One or more spec/schema URLs declared in the profile do not resolve.
Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.
Your profile declares a valid but older protocol version. A newer one is published.
Prioritised recommendations by expected impact and implementation effort
High impact, low effort
High impact, high effort
Medium impact & effort
Lower priority
Response time benchmarked against 7,457 Wixes we monitor.
All improvements ranked by priority, with evidence and actionable fixes.
One or more spec/schema URLs declared in the profile do not resolve.
Spec and schema URLs let agents validate request/response shapes before sending. When they 404 or time out, runtime validation degrades to "best effort" and strict agents reject the integration entirely. Common cause: copy-pasting a placeholder URL during initial profile setup. See the Full Check Breakdown for the specific URLs that failed.
Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.
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.
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": { ... }
}Your profile declares a valid but older protocol version. A newer one is published.
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.
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 itEvery signal we evaluate, grouped by category.
Can AI agents find your store and its UCP profile?
Profile served over a secure connection.
Profile URL uses https://
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
Profile fetched OK from /.well-known/ucp.
HTTP 200
Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.
robots.txt allows agent crawlers to fetch the profile.
robots.txt allows /.well-known/ucp
Agents respect robots.txt. Even a published profile gets ignored if the file is disallowed for known agent user-agents.
Hand-written brief at /llms.txt for AI agents.
Found at /llms.txt
Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.
XML sitemap published at /sitemap.xml.
Found at /sitemap.xml
Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.
OG meta tags on the homepage.
og:title and og:type/url present
OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.
Schema.org Organization (or OnlineStore) JSON-LD on homepage.
Organization-typed JSON-LD detected
Gives agents a structured representation of your brand identity — used to verify you are who your profile claims you are.
Viewport meta tag for mobile rendering.
<meta name="viewport"> present
Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.
Does your profile meet the published spec?
Profile structure conforms to the published UCP spec.
No structural errors
Strict UCP agents reject profiles with structural errors. The error code in the diagnostic shows which field failed.
ucp.version follows YYYY-MM-DD format.
Version: 2026-04-08
UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.
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)
Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.
Profile passes structural and field-level rules.
1 warning
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Resolves the 12 spec/schema URLs declared across the profile to confirm agents can fetch each one.
Did not resolve (6 of 12): https://ucp.dev/services/shopping/rest.openapi.json, https://ucp.dev/schemas/shopping/cart.json, https://ucp.dev/schemas/shopping/catalog-lookup.json, https://ucp.dev/schemas/shopping/checkout.json, https://ucp.dev/schemas/shopping/fulfillment.json, …
Spec and schema URLs let agents validate request/response shapes before sending. Broken URLs degrade runtime validation to "best effort" and cause strict agents to refuse the capability entirely.
What operations can agents actually perform?
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.
Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.
Store declares a checkout-namespaced capability.
dev.ucp.shopping.checkout detected
Without a checkout capability, agents can browse but can't complete a purchase end-to-end.
Service transports (REST/MCP/A2A/Embedded) declared on services.
REST, MCP
Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.
Tokenized payment handlers registered for in-conversation checkout.
Empty array: checkout-link redirect strategy
Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.
Live reachability check against https://www.wixapis.com/ecom/ucp/9dd05f15-3464-4ae3-90cb-02c32106aef5.
Host responded with HTTP 404 — endpoint reachable but path may be method-restricted
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the profile itself looks perfect.
Live reachability check against https://www.wixapis.com/ecom/ucp/9dd05f15-3464-4ae3-90cb-02c32106aef5/mcp.
tools/list returned a JSON-RPC response in 1275ms
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the profile itself looks perfect.
The plain-text brief this store publishes to AI agents. Captured on the most recent check.
# 東亜商事株式会社
> 東亜商事株式会社は、北九州市エリアを中心に鉄・非鉄金属・スクラップ全般の買取を行っています。重機、フォークリフト、各種コンテナ、計量器などの設備を充実させ、お客様のニーズに合わせた金属スクラップの現地回収やコンテナ無料貸出サービスを提供しています。買取は1kgから可能で、当日の相場で現金または銀行振込にて迅速に精算されます。出張買取も可能ですが、個人宅への訪問は行っていません。土曜日・祝日も営業しており、幅広いお客様に対応しています。
## Homepage link
- [home](https://www.toua-shoji.com/)
## AI エージェントによるアクセス
このサイトは Wix で作成されており、エージェント AI によるアクセス用の MCP (Model Context Protocol) に対応しています。AI エージェントは直接接続して、公開中の最新のサイトコンテンツを取得できます。スクレイピングは不要です。
- [**サイト MCP エンドポイント**](https://www.toua-shoji.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 の呼び出しを実装してください。| 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 |
| UCP Status | Verified |
| Endpoint | https://toua-shoji.com/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-04-08 |
| Transports | REST, MCP |
| Last Observed | |
| Last Full Index |
Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.
Live preview[](https://ucpchecker.com/score/toua-shoji.com)<a href="https://ucpchecker.com/score/toua-shoji.com"><img src="https://ucpchecker.com/score/toua-shoji.com/badge.svg" alt="UCP Score for toua-shoji.com"></a>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.
Track toua-shoji.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.
Track domains and get emailed when their UCP status changes.
By continuing you agree to our Terms & Privacy Policy.