UCP Checker
Sign in Start monitoring
Back to status
musubiwedding.com icon
UCP Score

UCP Score for musubiwedding.com

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

✓Verified
B84/100
Analyzed Sep 19, 2026 · 7 recommendations ·Wix · v2026-04-08 upgrade
84
/ 100
UCP Conformance Score
B

Solid UCP setup on musubiwedding.com with a few gaps left to close.

Agent Discovery95
UCP Conformance81
Capability Coverage77
Biggest blockers
Publish keys at the manifest rootRepair declared transport endpoints
Working

Agent Discovery is solid (95/100).

Blocking

Publish keys at the manifest root — Agents have nothing to verify your responses against.

Start Here

Publish keys at the manifest root → Repair declared transport endpoints → Fix broken spec or schema URLs

Verified

musubiwedding.com is agent-ready but has minor schema warnings.

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

Top Priorities

1
Publish keys at the manifest root

Agents have nothing to verify your responses against.

High impact Medium effort
2
Repair declared transport endpoints

One or more declared transport endpoints did not respond when probed.

High impact Medium effort
3
Fix broken spec or schema URLs

One or more spec/schema URLs declared in the manifest do not resolve.

Medium 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(2)

High impact, high effort

  • Publish keys at the manifest root
  • Repair declared transport endpoints
Incremental Gains(2)

Medium impact & effort

  • Fix broken spec or schema URLs
  • Publish Organization schema (JSON-LD) on the homepage
Consider Later(3)

Lower priority

  • Confirm checkout-link redirect strategy
  • Upgrade to the latest UCP spec version
  • Publish a schema URL for the service

How you compare on Wix

Response time benchmarked against 6,773 Wixes we monitor.

fastWix median 136msslow
Your store
141ms
Wix percentile
Below median
Faster than 42% of Wix stores
Cohort range
122–165ms
p25 to p75 (middle half)

Recommendations

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

1

Publish keys at the manifest root

High impact Medium effort

Agents have nothing to verify your responses against.

Why it matters

Signing keys let agents cryptographically verify checkout responses came from you, not a man-in-the-middle. Tokenized payment flows in v2026-04-08+ require them. Since 2026-07-12 the spec's canonical field is a root-level RFC 7517 "keys" array (the legacy "signing_keys" field was removed from the profile schema; we accept both during the migration). Stores using checkout-link redirects (e.g. WooCommerce) often skip this safely.

Show fix

Generate an Ed25519 keypair, publish the public key as a JWK in a root-level "keys" array (the canonical field since spec PR #566; "signing_keys" is legacy). Rotate annually; keep "kid" stable across rotations of the same key.

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

Repair declared transport endpoints

High impact Medium effort

One or more declared transport endpoints did not respond when probed.

Why it matters

A manifest that declares transports without working endpoints is the worst kind of broken — it looks perfect to static validators but agents hit a dead end the moment they try to use the capability. Connection refused, DNS failure, TLS errors, and 5xx responses all fall here. See the Full Check Breakdown below for the specific endpoints that failed.

UCP_PROBE_TRANSPORT_FAILED
3

Fix broken spec or schema URLs

Medium impact Low effort ×5

One or more spec/schema URLs declared in the manifest do not resolve.

Why it matters

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 manifest setup. See the Full Check Breakdown for the specific URLs that failed.

UCP_PROBE_URL_BROKEN
4

Publish Organization schema (JSON-LD) on the homepage

Medium impact Medium effort

No Organization-typed JSON-LD detected on your homepage.

Why it matters

Organization schema gives agents a structured representation of your brand identity — name, logo, social profiles, contact info, founding date. Agents use this to verify you are who you claim to be and to link your manifest data to a recognizable entity.

Show fix

Drop into <head> or end of <body>. Use OnlineStore (more specific) when the entire site is an ecommerce store; Organization is the generic fallback.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "name": "Yourstore",
  "url": "https://yourstore.com",
  "logo": "https://yourstore.com/logo.png",
  "sameAs": [
    "https://twitter.com/yourstore",
    "https://www.instagram.com/yourstore"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-800-000-0000",
    "contactType": "Customer Service"
  }
}
</script>
UCP_MISSING_ORG_SCHEMA
5

Confirm checkout-link redirect strategy

Low impact Low effort

payment_handlers is present but empty.

Why it matters

An empty payment_handlers array tells agents "I do not tokenize — redirect the buyer to my hosted checkout instead." Common and valid for WooCommerce stores. Only an issue if you intended to support tokenized payment.

UCP_EMPTY_PAYMENT_HANDLERS
6

Upgrade to the latest UCP spec version

Low impact Low effort

Your manifest declares a valid but older spec version. A newer published version is available.

Why it matters

Older versions stay valid (agents pin to the version you declare), but newer agent capabilities — embedded checkout, AP2 mandates, identity linking, 3DS payment authentication, payment terms and location lookup — only resolve against the latest spec. The manifest envelope barely moved: signing_keys went from inside ucp to the root as of 2026-04-08, and v2026-08-25 replaced it with keys (a JWK Set). Everything else in v2026-08-25 changed in the capability vocabulary, not the envelope.

Show fix

Bump version to 2026-08-25 and publish your public keys as a root-level keys array (JWK Set). Legacy signing_keys is still accepted, at the root or nested, but keys is the canonical field every verifier reads. See /specs/2026-08-25 for the full release notes.

"ucp": {
  "version": "2026-08-25",
  ...
},
"keys": [ ... ]   // JWK Set, sibling of ucp, not nested inside
UCP_VERSION_OUTDATED
7

Publish a schema URL for the service

Low impact Medium effort

Service is missing its "schema" URL.

Why it matters

The schema lets agents validate request/response shapes before sending. Highly recommended for any non-trivial endpoint.

Show fix 
"schema": "https://yourstore.com/.well-known/ucp/schemas/shopping.json"
UCP_SERVICE_MISSING_SCHEMA

Full Check Breakdown

Every signal we evaluate, grouped by category.

Functional probes ran .
Agent Discovery7/8 passed

Can AI agents find your store and its UCP manifest?

  • HTTPSCore

    Manifest served over a secure connection.

    Manifest 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 manifest reachableCore

    Manifest 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 manifest.

    robots.txt allows /.well-known/ucp

    Why it matters

    Agents respect robots.txt. Even a published manifest 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.

    Missing or incomplete on homepage

    Why it matters

    Gives agents a structured representation of your brand identity — used to verify you are who your manifest 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/5 passed

Does your manifest meet the published spec?

  • Manifest passes schema validationCore

    Manifest structure conforms to the published UCP spec.

    No structural errors

    Why it matters

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

  • Spec 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.

  • Validation warnings clearCore

    Manifest passes structural and field-level rules.

    2 warnings

    Why it matters

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

  • Spec & schema URLs resolve (10)Core

    Resolves the 10 spec/schema URLs declared across the manifest to confirm agents can fetch each one.

    Did not resolve (5 of 10): https://ucp.dev/services/shopping/rest.openapi.json, https://ucp.dev/schemas/shopping/checkout.json, https://ucp.dev/schemas/shopping/fulfillment.json, https://ucp.dev/schemas/shopping/catalog-search.json, https://ucp.dev/schemas/shopping/catalog-lookup.json

    Why it matters

    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.

Capability Coverage3/6 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

    2 capabilities detected

    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.

  • REST transport reachableInterop

    Live reachability check against https://www.wixapis.com/ecom/ucp/b2bca6da-27a4-4f14-a7f2-5861ba6d0d66.

    Host responded with HTTP 404 — endpoint reachable but path may be method-restricted

    Why it matters

    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 manifest itself looks perfect.

  • MCP transport reachableInterop

    Live reachability check against https://www.wixapis.com/ecom/ucp/b2bca6da-27a4-4f14-a7f2-5861ba6d0d66/mcp.

    tools/list returned a JSON-RPC response in 178ms

    Why it matters

    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 manifest itself looks perfect.

/llms.txt content

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

2.9 KB6a958982e29c4872
# yorimichi
> 順道パン提供手工製作的風呂敷餅乾禮盒，強調使用優質食材和環保包裝。網站展示了多款餅乾和禮盒選項，並提供婚禮喜餅和彌月禮盒的試吃預約服務。品牌理念著重於傳遞美味記憶與分享的溫暖，並鼓勵禮盒的重複利用以減少環境負擔。

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

## AI 專員存取權

此網站由 Wix 提供技術支援，並支援 Model Context Protocol (MCP)，
以進行代理式 AI 存取。AI 專員可以直接連結，以擷取即時、
最新的網站內容，無需進行抓取。\n- [**網站 MCP 端點**](https://www.musubiwedding.com/_api/mcp)
- [**Wix MCP Docs**](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 方法的絕對網址（例如：https://www.wixapis.com/...)。使用 SearchSiteApiDocs 擷取。
- **method** - 用於 API 呼叫的 HTTP 方法。
- **body** - 做為有效 JSON 字串的請求主體。

### ReadFullDocsArticle
從 Wix 開發人員文件入口網站擷取完整文章。
- **articleUrl** - Wix 開發人員文件入口網站中的文章網址。

### ReadFullDocsMethodSchema
擷取 Wix API 方法的完整結構描述。應在透過 CallWixSiteAPI 呼叫
實際方法之前呼叫。
- **articleUrl** - Wix API 方法的參照文章網址。

## 訪客可透過 AI + MCP 執行哪些操作

- 取得商家詳細資訊（聯絡資訊、地點、營業時間）
- 探索提供的產品和服務
- 預訂服務與訂位
- 開始採購並由系統導向至網站以完成結帳
- 提出問題並取得相關答案，無需瀏覽網站

## 備註

- 連結至 MCP 端點無需驗證
- 僅限可在網站上存取的公開資訊才可供使用
- 內容一律為即時且為最新狀態
- 若要接收工具更新，請在收到工具更新通知時實作 tools/list 呼叫
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
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://musubiwedding.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 musubiwedding.com badge for https://ucpchecker.com/score/musubiwedding.comLive preview
Markdown
[![UCP Score for musubiwedding.com](https://ucpchecker.com/score/musubiwedding.com/badge.svg)](https://ucpchecker.com/score/musubiwedding.com)
HTML
<a href="https://ucpchecker.com/score/musubiwedding.com"><img src="https://ucpchecker.com/score/musubiwedding.com/badge.svg" alt="UCP Score for musubiwedding.com"></a>
New · Early access open
Is musubiwedding.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 musubiwedding.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.