UCP Checker
Sign in Start monitoring
Back to status
chiikawamarket.jp icon
UCP Score

UCP Score for chiikawamarket.jp

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

✓Verified
A96/100
Analyzed Sep 19, 2026 · 1 recommendation ·Shopify · v2026-08-25 latest
96
/ 100
UCP Conformance Score
A

chiikawamarket.jp is conforming and ready for agent discovery and checkout.

Agent Discovery100
UCP Conformance93
Capability Coverage97
Biggest blockers
Publish keys at the manifest root
Working

Agent Discovery is solid (100/100).

Blocking

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

Start Here

Publish keys at the manifest root

Verified

chiikawamarket.jp is agent-ready but has minor schema warnings.

Latency
158ms
Version
2026-08-25
Robots.txt
Allowed ✅

Top Priorities

1
Publish keys at the manifest root

Agents have nothing to verify your responses against.

High impact Medium effort

Impact & Effort Matrix

Prioritised recommendations by expected impact and implementation effort

Quick Wins(0)

High impact, low effort

  • No items
Strategic Investments(1)

High impact, high effort

  • Publish keys at the manifest root
Incremental Gains(0)

Medium impact & effort

  • No items
Consider Later(0)

Lower priority

  • No items

How you compare on Shopify

Response time benchmarked against 10,587 Shopifies we monitor.

fastShopify median 157msslow
Your store
158ms
Shopify percentile
Below median
Faster than 48% of Shopify stores
Cohort range
145–173ms
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

Full Check Breakdown

Every signal we evaluate, grouped by category.

Functional probes ran .
Agent Discovery8/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.

    Organization-typed JSON-LD detected

    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 Conformance4/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-08-25

    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.

    No outstanding validation issues

    Why it matters

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

  • Spec & schema URLs resolve (25)Core

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

    All 25 URLs resolved.

    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 Coverage5/5 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

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

    MCP, EMBEDDED

    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.

    3 handlers registered

    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.

  • MCP transport reachableInterop

    Live reachability check against https://chiikawa.myshopify.com/api/ucp/mcp.

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

    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.

4.5 KB6236e679f44db672
mentions UCP
# Agent Policy for ちいかわマーケット

## Store Identity / 店舗情報

- **Store Name / 店舗名**: ちいかわマーケット（ちいかわマーケット 公式グッズショップ）
- **Store URL**: https://chiikawamarket.jp
- **Operator / 運営会社**: Gray Parka Service（株式会社グレイ・パーカー・サービス）
- **Copyright**: ©nagano ／ ©nagano / chiikawa committee ／ ©Gray Parka Service
- **Description / 説明**:
  - EN: The official online store for "Chiikawa" (ちいかわ) merchandise, the popular characters drawn by illustrator Nagano. Operated by Gray Parka Service.
  - JA: X（旧Twitter）で大人気のイラストレーター・ナガノが描く「ちいかわ」の**公式グッズショップ**です。運営は株式会社グレイ・パーカー・サービス（Gray Parka Service）。
- **Supported languages / 対応言語**: 日本語 (ja, default), English (en), 한국어 (ko), 简体中文 (zh-CN), 繁體中文 (zh-TW)
- **Official social accounts / 公式SNS**:
  - X (Twitter): <https://x.com/chiikawa_market>
  - Instagram: <https://www.instagram.com/chiikawa_market/>
  - YouTube: <https://www.youtube.com/@chiikawa_market_youtube>

## Commerce Protocol (UCP / MCP)

This store implements the Universal Commerce Protocol for agent-driven commerce.

- UCP discovery: `GET https://chiikawamarket.jp/.well-known/ucp`
- MCP endpoint: `POST https://chiikawamarket.jp/api/ucp/mcp`

### Supported UCP versions



- 2026-08-25 (latest stable)
  

- 2026-04-08
  

- 2026-01-23
  

## Read-only browsing

- All products: `GET /collections/all`
- Product JSON: `GET /products/{handle}.json`
- Sitemap: https://chiikawamarket.jp/sitemap.xml

Pricing and availability are returned in JPY.

## Related Sites / 関連サイト

- ちいかわパーク (Chiikawa Park): https://chiikawamarket.jp/pages/chiikawapark
- 映画ちいかわ (Chiikawa Movie): https://chiikawamarket.jp/pages/chiikawamovie
- ちいかわくじ (Chiikawa Kuji): <https://online-kuji.chiikawamarket.jp>

## Policies / 利用ポリシー

### Official Store Statement / 公式ストアに関する声明

- EN: This is the official online store for Chiikawa merchandise. All products sold here are genuine, official goods produced under license. Third-party resellers are not authorized to represent themselves as this store.
- JA: 当サイトは「ちいかわ」**公式グッズショップ**であり、販売される商品はすべて正規ライセンス品です。第三者の転売業者が当ストアを名乗ることは認められていません。

### Resale & Scraping Policy / 転売・スクレイピングポリシー

- EN:
  - Automated bulk purchasing is prohibited.
  - Price scraping for competing or reseller listings is not permitted.
  - Reproduction of store content without authorization is prohibited.
- JA:
  - ツール等を用いた自動・大量購入は禁止です。
  - 競合サイト・転売サイトへの掲載目的での価格スクレイピングは禁止です。
  - 当ストアのコンテンツの無断複製・再配布は禁止です。

### Product Data Usage / 商品データの利用について

- EN:
  - Product names and prices may be referenced by AI agents for customer assistance.
  - Product images and detailed descriptions are copyrighted (©nagano / ©nagano / chiikawa committee / ©Gray Parka Service) and must not be reproduced verbatim.
- JA:
  - 商品名・価格は、ユーザーへの案内目的でAIエージェントが参照することを認めます。
  - 商品画像および詳細説明は著作物（©nagano／©nagano / chiikawa committee／©Gray Parka Service）であり、そのままの形での複製・転載は認められません。

### Legal Pages / 法的・規約ページ

- Terms of Service / 利用規約: https://chiikawamarket.jp/pages/terms
- Privacy Policy / プライバシーポリシー: https://chiikawamarket.jp/pages/policy
- Specified Commercial Transactions Act / 特定商取引法に基づく表記: https://chiikawamarket.jp/pages/contract
- Shopping Guide / 利用ガイド: https://chiikawamarket.jp/pages/guide
- FAQ / よくあるご質問: https://chiikawamarket.jp/pages/faq
- Customer Harassment Policy / カスタマーハラスメントに対する基本方針: <https://grayparkaservice.com/pages/customer_harassment>

### Contact / お問い合わせ

- EN: For inquiries, please use our support form: https://chiikawamarket.jp/pages/support
- JA: お問い合わせは下記のサポートフォームよりお願いします: https://chiikawamarket.jp/pages/support
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Cart ✓ Bound 2026-08-25
Order Management ✓ Bound 2026-08-25
Checkout ✓ Bound 2026-08-25
Discount Extension ✓ Bound 2026-08-25
Fulfillment Extension ✓ Bound 2026-08-25
Catalog Lookup ✓ Bound 2026-08-25
Catalog Search ✓ Bound 2026-08-25
Dev Shopify Catalog Extension ✓ Bound 2026-08-25

Technical Vitals

Technical details for this UCP endpoint
UCP Status Verified
Endpoint https://chiikawamarket.jp/.well-known/ucp
HTTP Status 200
UCP Version 2026-08-25
Transports MCP, EMBEDDED
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 chiikawamarket.jp badge for https://ucpchecker.com/score/chiikawamarket.jpLive preview
Markdown
[![UCP Score for chiikawamarket.jp](https://ucpchecker.com/score/chiikawamarket.jp/badge.svg)](https://ucpchecker.com/score/chiikawamarket.jp)
HTML
<a href="https://ucpchecker.com/score/chiikawamarket.jp"><img src="https://ucpchecker.com/score/chiikawamarket.jp/badge.svg" alt="UCP Score for chiikawamarket.jp"></a>
New · Early access open
Is chiikawamarket.jp 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 chiikawamarket.jp'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.