UCP Checker
Back to status
familyshop.cl icon
UCP Score

UCP Score for familyshop.cl

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

Verified
B80/100
Analyzed Sep 22, 2026 · 2 recommendations ·Jumpseller · v2026-08-25 latest
80
/ 100
UCP Conformance Score
B

Solid UCP setup on familyshop.cl with a few gaps left to close.

Agent Discovery95
UCP Conformance88
Capability Coverage53
Working

Agent Discovery is solid (95/100).

Start Here

Publish keys at the manifest root → Publish Organization schema (JSON-LD) on the homepage

Verified

familyshop.cl publishes a valid UCP manifest, with minor schema warnings.

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

Top Priorities

1
Publish keys at the manifest root

Agents have nothing to verify your responses against.

Medium impact Medium effort
2
Publish Organization schema (JSON-LD) on the homepage

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

Medium 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

  • Publish keys at the manifest root
  • Publish Organization schema (JSON-LD) on the homepage
Consider Later(0)

Lower priority

  • No items

How you compare on Jumpseller

Response time benchmarked against 5 Jumpsellers we monitor.

fastJumpseller median 280msslow
Your store
280ms
Jumpseller percentile
Below median
Faster than 40% of Jumpseller stores
Cohort range
274–303ms
p25 to p75 (middle half)

Recommendations

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

1

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
2

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

Full Check Breakdown

Every signal we evaluate, grouped by category.

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

    1 warning

    Why it matters

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

Capability Coverage1/4 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.

    No checkout capability

    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

    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.

4.1 KBd2407d8f49a4c8e2
mentions UCPdeclares checkout flow
# Familyshop

> Moda y calidad para toda la familia sin pagar de más. Encuentra ropa para Mujer, Hombre, Juvenil e Infantil a los mejores precios en nuestras 86 tiendas y en familyshop.cl This is a Jumpseller-powered online store. Agents can browse its public content via the sitemap or access structured product and category data through the MCP (Model Context Protocol) endpoint. No authentication required.

This document is also available at [https://familyshop.cl/agents.md](https://familyshop.cl/agents.md).

## MCP (Model Context Protocol)

- [MCP endpoint](https://familyshop.cl/api/mcp): send JSON-RPC 2.0 requests via POST (Streamable HTTP)
- [MCP discovery](https://familyshop.cl/.well-known/mcp.json): server metadata and capabilities

### Available Tools

- get_store_info: Get public store information including name, URL, country, currency, description, and logo.
- search_policies: Search the store's own pages - returns, terms, privacy, shipping, FAQ - and return the ones that answer a question, with their text. Called with no query it returns the store's legal pages. Results are ordered with those first: a page marked "legal": true is the store's own terms and can be quoted as policy, and anything else is a page the merchant wrote, which may answer the question but is not a policy.
- list_products: List available products in the store. Returns name, price, images, variants, and categories. Supports pagination and filtering by category permalink.
- get_product: Get a product by the id this server returns, or by its permalink (URL slug). Returns name, price, description, images, variants, and categories.
- search_products: Search products by query string. Searches in name, description, and SKU. Only returns available products.
- list_categories: List product categories visible in the store navigation.
- get_category: Get a category by permalink (URL slug). Returns name, description, SEO fields, and images.

The MCP endpoint is the recommended way to access structured product and category data.

## Universal Commerce Protocol (UCP)

- [UCP profile](https://familyshop.cl/.well-known/ucp): advertised capabilities and their endpoints
- [Shopping endpoint](https://familyshop.cl/api/ucp/mcp): the Catalog and Cart capabilities over UCP's MCP binding

### UCP Tools

- search_catalog: UCP Catalog search. Returns products matching a query, in the UCP Product shape.
- lookup_catalog: UCP Catalog lookup. Returns the products with the given ids, in the UCP Product shape.
- get_product: UCP Catalog detail. Returns one product by id, in the UCP Product shape.
- create_cart: UCP Cart create. Builds a cart from variant ids returned by the catalog and returns it with estimated totals and a continue_url the shopper can be handed to finish the purchase. Prices are integers in the currency's ISO 4217 minor unit: 9500 EUR is 95.00.
- get_cart: UCP Cart read. Returns the cart's current line items, estimated totals and continue_url. Prices are integers in the currency's ISO 4217 minor unit: 9500 EUR is 95.00.
- update_cart: UCP Cart update. Replaces the cart's line items with the ones sent: send every line the cart should hold afterwards, not only the ones that changed. An empty list empties the cart.
- cancel_cart: UCP Cart cancel. Empties and closes the cart, and returns the state it was in before that. Later calls for the same id report it as not found.

## Read-Only Browsing (No Authentication Required)

For agents that only need to read public store data without using the MCP endpoint:

- [Sitemap](https://familyshop.cl/sitemap.xml): all public product, category, and content pages ([robots.txt](https://familyshop.cl/robots.txt) lists the paginated sitemap files)
- [Search](https://familyshop.cl/search?q={query}): full-text product search (HTML)
- Product, category, and content pages are served as HTML at https://familyshop.cl/{permalink}

## Platform

This store is built on [Jumpseller](https://jumpseller.com), an e-commerce platform. All Jumpseller stores expose the same MCP endpoint and tools. See the [Jumpseller AI Toolkit](https://jumpseller.com/support/ai-toolkit/) for more information.
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Cart ✓ 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://familyshop.cl/.well-known/ucp
HTTP Status 200
UCP Version 2026-08-25
Transports 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 familyshop.cl badge for https://ucpchecker.com/score/familyshop.clLive preview
Markdown
[![UCP Score for familyshop.cl](https://ucpchecker.com/score/familyshop.cl/badge.svg)](https://ucpchecker.com/score/familyshop.cl)
HTML
<a href="https://ucpchecker.com/score/familyshop.cl"><img src="https://ucpchecker.com/score/familyshop.cl/badge.svg" alt="UCP Score for familyshop.cl"></a>
New · Early access open
Is familyshop.cl 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 familyshop.cl'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.