UCP Checker
Back to status
timxiaohuang.com icon
UCP Score

UCP Score for timxiaohuang.com

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

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

timxiaohuang.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

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

Latency
408ms
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,457 Wixes we monitor.

fastWix median 398msslow
Your store
408ms
Wix percentile
Below median
Faster than 45% of Wix stores
Cohort range
359–461ms
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.

3.0 KB36c8719ec67b9557
# 夜游HAPPY小组
> 夜游HAPPY小组提供在马尼拉、东京、大阪等地的高端伴游和出差服务,包括菲律宾、越南、日韩等地的女性。服务内容多样,从伴游、上门按摩到与AV女优的私人预约。网站还提供芭提雅的旅游项目,如跳伞、出海一日游,以及曼谷和胡志明市的KTV预订服务。用户可以通过网站或联系客服进行预约,并根据会员身份享受不同优惠。

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

## AI 專員存取權

此網站由 Wix 提供技術支援,並支援 Model Context Protocol (MCP),
以進行代理式 AI 存取。AI 專員可以直接連結,以擷取即時、
最新的網站內容,無需進行抓取。\n- [**網站 MCP 端點**](https://www.timxiaohuang.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
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://timxiaohuang.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 timxiaohuang.com badge for https://ucpchecker.com/score/timxiaohuang.comLive preview
Markdown
[![UCP Score for timxiaohuang.com](https://ucpchecker.com/score/timxiaohuang.com/badge.svg)](https://ucpchecker.com/score/timxiaohuang.com)
HTML
<a href="https://ucpchecker.com/score/timxiaohuang.com"><img src="https://ucpchecker.com/score/timxiaohuang.com/badge.svg" alt="UCP Score for timxiaohuang.com"></a>
New · Early access open
Is timxiaohuang.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 timxiaohuang.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.