UCP Checker
Check a store
UCP Score

UCP Score for shop.bulletproof.com

Ready for UCP agents

91 out of 100, grade A: ready for UCP agents. The missing 9 points are spread across Discovery and Conformance. One spec break on the status page isn't counted in the score.

Discovery 80Conformance 93Capabilities 100release 2026-08-25

UCP Score 91/100 grade A · ready for UCP agents
Points missing 9 Discovery, Conformance Fixes 5 raise the score Spec breaks 1 not in the score

How the score is made

three areas, weighted
Discovery 30%
Can a UCP agent find and read the profile: HTTPS, an answer at /.well-known/ucp, robots.txt allowing it, and five files outside UCP (llms.txt, sitemap, Open Graph, Organization schema, viewport).
80−6 pts
Conformance 40%
Does the profile follow the spec: valid against its release (counted three times), a dated release, keys published, few warnings, spec and schema links that resolve.
93−2.8 pts
Capabilities 30%
What an agent can do here: how many capabilities, checkout, at least one service, payment handlers, and services that answer our check.
100full marks
A85–100Ready for UCP agents
B70–84Nearly there
C50–69Partly ready
D30–49Hard for UCP agents
F0–29Not ready

Raise the score

fixes that move the number
+3
1Publish 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.
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.
Conformance · effort medium 
{
  "keys": [
    {
      "kty": "EC",
      "crv": "P-256",
      "x": "<base64url x>",
      "y": "<base64url y>",
      "kid": "store-2026-10",
      "use": "sig",
      "alg": "ES256"
    }
  ],
  "ucp": { ... }
}

Create a P-256 (ES256) key pair: ES256 is the one algorithm every UCP agent must be able to check. Add the public key to a "keys" list at the top level of your UCP profile, as in the example, with its own "kid", and keep the private key on your server. The spec recommends a new key every 90 days: publish the new one next to the old, sign with it, and remove the old key a week later.

part of +6
2Publish Organization schema (JSON-LD) on the homepage
No Organization-typed JSON-LD detected on your homepage.
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 profile data to a recognizable entity.
Discovery · effort medium 
<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>

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

part of +6
3Publish a sitemap.xml
No sitemap.xml detected at the root of your domain.
Sitemaps tell agents and crawlers which pages on your store are canonical and how often they change. Without one, agents fall back to following internal links, which is slower and less complete, especially for catalog pages buried behind faceted nav.
Discovery · effort low 
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yourstore.com/</loc>
    <changefreq>daily</changefreq>
  </url>
  <url>
    <loc>https://yourstore.com/products</loc>
    <changefreq>daily</changefreq>
  </url>
  <!-- one <url> entry per indexable page -->
</urlset>

Most ecommerce platforms generate sitemap.xml automatically. If yours does not, generate one and serve it at /sitemap.xml.

part of +6
4Add Open Graph meta tags to the homepage
OG tags missing or incomplete on your homepage.
OG tags give agents and link unfurlers (Slack, iMessage, ChatGPT) a clean title, description, and image to represent your store. Without them, shares show garbled fallback text.
Discovery · effort low 
<meta property="og:title" content="Yourstore | short tagline">
<meta property="og:type" content="website">
<meta property="og:url" content="https://yourstore.com/">
<meta property="og:description" content="One-sentence description of what you sell.">
<meta property="og:image" content="https://yourstore.com/og-cover.jpg">
<meta property="og:site_name" content="Yourstore">

Add inside <head>. og:title and og:type are the minimum; og:url, og:description, and og:image are strongly recommended.

part of +6
5Add a mobile viewport meta tag
No viewport meta tag detected on your homepage.
Mobile-originating agent sessions (ChatGPT iOS, Apple Intelligence) render store pages in browser sandboxes that respect the viewport tag. Without it, the page renders at desktop width and pinch-to-zoom UX kicks in, and agents that take screenshots of pages get unreadable images.
Discovery · effort low 
<meta name="viewport" content="width=device-width, initial-scale=1">

One line inside <head>. Modern frontend frameworks add this automatically; its absence usually means a hand-rolled or legacy template.

Every check

13 passed · 5 to fix
Agent Discovery · 4 of 8
4 OK
HTTPS, UCP profile reachable, AI bot access, llms.txtShow
  • HTTPS · Profile URL uses https://
  • UCP profile reachable · HTTP 200
  • AI bot access · robots.txt allows /.well-known/ucp
  • llms.txt · Found at /llms.txt
Problem
sitemap.xml
HTTP 403 at /sitemap.xml. Fix 3 above.
Discovery
Problem
Open Graph tags
Missing or incomplete on homepage. Fix 4 above.
Discovery
Problem
Organization schema (JSON-LD)
Missing or incomplete on homepage. Fix 2 above.
Discovery
Problem
Mobile viewport meta
Missing or incomplete on homepage. Fix 5 above.
Discovery
UCP Conformance · 4 of 5
4 OK
Profile passes schema validation, Protocol version present and well-formed, No validation warnings, Spec & schema URLs resolve (29)Show
  • Profile passes schema validation · No structural errors
  • Protocol version present and well-formed · Version: 2026-08-25
  • No validation warnings · No outstanding validation issues
  • Spec & schema URLs resolve (29) · All 29 URLs resolved.
To fix
Public keys published
No keys list at the top level of the profile. Fix 1 above.
Conformance
Capability Coverage · 5 of 5
5 OK
Capabilities declared, Checkout capability, Transports declared, Payment handlers, MCP transport reachableShow
  • Capabilities declared · 5 of 6 capability families detected: Checkout, Identity Linking, Cart Management, Order Management, Catalog. A family counts once however many namespaces or extensions declare it.
  • Checkout capability · dev.ucp.shopping.checkout detected
  • Transports declared · MCP, Embedded
  • Payment handlers · 3 handlers registered
  • MCP transport reachable · tools/list returned a JSON-RPC response in 178ms

Not in the score, but worth fixing first

spec breaks
Problem
One entry is at a different version, so agents ignore it
This profile declares 2026-08-25, but dev.ucp.shopping (Embedded) is at 2026-04-08. The spec says every dev.ucp.* service, capability and extension must carry the profile's version, and an agent on 2026-08-25 must reject any entry that doesn't. Declare it at 2026-08-25, and describe older versions in a supported_versions profile. Not part of the UCP Score.
on the status page

The score measures what the profile declares across the three areas above. These break a rule in the spec that agents follow, so they can stop an agent before the score matters.

Speed among Shopify stores
The profile answered in 167 ms, faster than 86% of the Shopify stores we check.