UCP Checker
Check a store
UCP Score

UCP Score for aliancascs.com.br

Ready for UCP agents

97 out of 100, grade A: ready for UCP agents. All 3 missing points are in Conformance, and one fix there takes it to 100. One spec break on the status page isn't counted in the score.

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

UCP Score 97/100 grade A · ready for UCP agents
Points missing 3 Conformance Fixes 1 takes it to 100 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).
100full marks
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.

Every check

17 passed · 1 to fix
Agent Discovery · 8 of 8
8 OK
HTTPS, UCP profile reachable, AI bot access, llms.txt, sitemap.xml, Open Graph tags, Organization schema (JSON-LD), Mobile viewport metaShow
  • 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
  • sitemap.xml · Found at /sitemap.xml
  • Open Graph tags · og:title and og:type/url present
  • Organization schema (JSON-LD) · Organization-typed JSON-LD detected
  • Mobile viewport meta · <meta name="viewport"> present
UCP Conformance · 4 of 5
4 OK
Profile passes schema validation, Protocol version present and well-formed, No validation warnings, Spec & schema URLs resolve (5)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 (5) · All 5 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 678ms

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 163 ms, faster than 69% of the Shopify stores we check.