UCP Score
UCP Score for pneusdouglas.com.br
77 out of 100, grade B: nearly there. The missing 23 points are spread across Discovery and Conformance and Capabilities. 2 spec breaks on the status page aren't counted in the score.
Discovery 95Conformance 81Capabilities 53release 2026-08-25
UCP Score
77/100
grade B · nearly there
Points missing→
23
Discovery, Conformance, Capabilities
Fixes→
3
raise the score
Spec breaks→
2
not in the score
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).
95−1.5 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.
81−7.6 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.
53−14.1 pts
A85–100Ready for UCP agents
B70–84Nearly there
C50–69Partly ready
D30–49Hard for UCP agents
F0–29Not ready
part of +8
Conformance · effort low
1Fix broken spec or schema URLs
One or more spec/schema URLs declared in the profile do not resolve.
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 profile setup. See the Full Check Breakdown for the specific URLs that failed.
+2
Discovery · effort medium
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.
<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 +8
Conformance · effort medium
3Cryptographic message signing is not yet enabled
Your UCP profile lists no public keys, so cryptographic message signing is not yet enabled for this store. HTTPS already confirms your store's identity; signing adds a further layer for checkout, payment and webhook messages.
The UCP spec recommends signing checkout completion and payment responses, and requires it for webhooks. A store that sends order updates by webhook needs keys; others can add them later.
{
"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.
Agent Discovery · 7 of 8
7 OK
HTTPS, UCP profile reachable, AI bot access, llms.txt, sitemap.xml, Open Graph tags, 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
- Mobile viewport meta · <meta name="viewport"> present
UCP Conformance · 2 of 5
2 OK
Profile passes schema validation, Protocol version present and well-formedShow
- Profile passes schema validation · No structural errors
- Protocol version present and well-formed · Version: 2026-08-25
To fix
Conformance
No validation warnings
1 warning.
To fix
Conformance
Spec & schema URLs resolve (12)
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, ….
Capability Coverage · 2 of 6
2 OK
Transports declared, MCP transport reachableShow
- Transports declared · MCP
- MCP transport reachable · tools/list returned a JSON-RPC response in 130ms
To fix
Capabilities
Capabilities declared
1 of 6 capability families detected: Catalog. A family counts once however many namespaces or extensions declare it.
Problem
Capabilities
Checkout capability
No checkout capability.
To fix
Capabilities
Payment handlers
Empty array: checkout-link redirect strategy.
To fix
Capabilities
REST transport reachable
Host responded with HTTP 404 — endpoint reachable but path may be method-restricted.
Problem
on the status page
The profile isn't served with the caching the spec requires
Served with Cache-Control "max-age=14400". Spec level: MUST.
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 Tray stores
The profile answered in 18 ms, faster than 55% of the Tray stores we check.
