UCP Checker
Sign in Start monitoring
Back to status
iikanjini.info icon
UCP Score

UCP Score for iikanjini.info

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

✓Verified
A86/100
Analyzed Sep 28, 2026 · 3 recommendations ·Wix · v2026-08-25 latest
86
/ 100
UCP Conformance Score
A

iikanjini.info publishes a conforming manifest with broad capability coverage.

Agent Discovery100
UCP Conformance81
Capability Coverage80
Working

Agent Discovery is solid (100/100).

Start Here

Fix broken spec or schema URLs → Publish keys at the manifest root → Publish a schema URL for the service

Verified

iikanjini.info publishes a valid UCP manifest, with minor schema warnings.

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

Top Priorities

1
Fix broken spec or schema URLs

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

Medium impact Low effort
2
Publish keys at the manifest root

Agents have nothing to verify your responses against.

Medium impact Medium effort
3
Publish a schema URL for the service

Service is missing its "schema" URL.

Low 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(0)

High impact, high effort

  • No items
Incremental Gains(2)

Medium impact & effort

  • Fix broken spec or schema URLs
  • Publish keys at the manifest root
Consider Later(1)

Lower priority

  • Publish a schema URL for the service

How you compare on Wix

Response time benchmarked against 7,497 Wixes we monitor.

fastWix median 438msslow
Your store
388ms
Wix percentile
Top quartile
Faster than 81% of Wix stores
Cohort range
398–497ms
p25 to p75 (middle half)

Recommendations

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

1

Fix broken spec or schema URLs

Medium impact Low effort ×6

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
2

Publish keys at the manifest root

Medium impact Medium effort

Agents have nothing to verify your responses against.

Why it matters

Signing keys let agents check that checkout responses really came from you. Tokenized payment flows in v2026-04-08+ require them. Since 2026-07-12 the spec expects a root-level "keys" list (the older "signing_keys" field is still accepted while stores move). Stores that hand the buyer a checkout link instead of taking payment through the agent can go without them for now.

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
3

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

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

  • No validation warningsCore

    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 (12)Core

    Resolves the 12 spec/schema URLs declared across the manifest 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, …

    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 Coverage4/6 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

    3 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/bcacf63f-c07a-4581-8939-e47fc6a5a972.

    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/bcacf63f-c07a-4581-8939-e47fc6a5a972/mcp.

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

    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.2 KBab000344de3ac781
# 飯豊の観光問い合わせ専用窓口
> このウェブサイトは、山形県飯豊町の観光情報を提供しています。外国人パートナー観光案内所にも認定されており、気軽に問い合わせを受け付けています。サイトでは、白川湖の水没林ツアーの造成に関する注意事項、公園設備、宿泊施設、イベント情報などを案内しています。また、飯豊町の美しい散居集落景観や、地域活性化に向けた取り組みについても紹介しています。

## Homepage link
- [home](https://www.iikanjini.info/)

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

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

- [**サイト MCP エンドポイント**](https://www.iikanjini.info/_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-08-25
Checkout ✓ Bound 2026-08-25
Fulfillment Extension ✓ Bound 2026-08-25
Catalog Lookup ✓ Bound 2026-08-25
Catalog Search ✓ Bound 2026-08-25

Technical Vitals

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