UCP Checker

What does a UCP agent find at your store?

We read the UCP profile at /.well-known/ucp, check it against the release it declares, call the services it lists, and show what we found and what to fix.

What you get back

two pages for your store
/status/yourstore.com
Verified yourstore.com HTTP statusUCP releaseMCP, REST, A2A, Embeddedcapabilitieswhen we checked

The status page. The verdict on your store, every finding with the spec rule it comes from, how your store answered under each section of the spec, and your UCP profile exactly as served.

/score/yourstore.com
0–100UCP Score · grade A to F points missing by areafixes that raise itspec breaksevery check

The score page. Your UCP Score and how it is made, the fixes that raise it with copy-ready code, and the spec rules it doesn’t count yet. Only a store whose UCP profile we could read gets a score.

Check trace

What we check at your store

We read the store's UCP profile under the spec's five sections (discovery, identity, payment, transport and capabilities), call what a check can call, and record every request we make. Shown here on an example store; your result shows what your store met.

Requests
6
Connections
6
At the store, summed
310 ms
Network, summed
264 ms
Requests signed
yes
  1. Discovery↗
    Discovery & negotiation
    how agents find the profile
    Found · 1 request
  2. Identity & Auth↗
    Identity & authentication
    how each side proves who it is
    Signed by us · 1 key
  3. Payment↗
    Payment architecture
    how the store takes payment
    1 handler declared
  4. Transport↗
    Transport layer
    how agents call the store
    REST answered · MCP answered · Embedded declared
  5. Capabilities↗
    Standard capabilities
    what agents can do there
    7 declared
UCP CheckerUCPCheckerBot/1.0
  • Signed · Web Bot Auth
  • key example-ke…
  • Discovery & negotiation/.well-known/ucp · 200
  • read from profileIdentity & authenticationsigned · 1 key
  • read from profilePayment architecture1 handler
  • Transport layerREST, MCP · answered
  • read from profileStandard capabilities7 declared
  • Outside UCProbots.txt · homepage · /llms.txt
  • Checked its linksspec · schemas · handlers
Found
Discovery & negotiation1 request
Served at /.well-known/ucp with 200 OK, 4.4 KB. robots.txt allows /.well-known/ucp.
Read
Identity & authenticationread from profile
Every request we made was signed (Web Bot Auth, RFC 9421). The profile publishes 1 key, so the store's own signed messages can be checked.
Read
Payment architectureread from profile
Declares com.example.pay. Payment happens inside checkout, which a check never calls, so it shows only in an agent run.
Answered
Transport layer2 requests
The REST service answered at its address. The MCP service answered tools/list in 140 ms. Embedded is declared; a check doesn't call it, so whether it works shows only in an agent run.
Read
Standard capabilitiesread from profile
7 declared at 2026-08-25. The buyer can sign the agent in to their own account through accounts.yourstore.com. An agent can hand over a ready cart at yourstore.com/buy. Cart, checkout, order change state, so a check never calls them: they show only in an agent run.
Discovery & negotiation1 request · 200 OK120 ms
GET /.well-known/ucp 200 OK 3.0 KB · application/json 120 ms

Answered.

  • DNS 8 ms
  • Connect 14 ms
  • TLS 22 ms
  • Wait 70 ms
  • Download 5 ms
URL
https://yourstore.com/.well-known/ucp
Server
203.0.113.10
Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Sent accept
application/json
Sent signature-agent
"https://ucpchecker.com"
Sent signature
Web Bot Auth (RFC 9421)
Got content-type
application/json
Got cache-control
public, max-age=300
Transport layer2 requests · 2 × 200 OK140 ms
POST /mcp 200 OK 8.0 KB · application/json 140 ms

Answered.

  • DNS 8 ms
  • Connect 14 ms
  • TLS 22 ms
  • Wait 90 ms
  • Download 5 ms
URL
https://yourstore.com/mcp
Server
203.0.113.10
Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Sent accept
application/json
Sent signature-agent
"https://ucpchecker.com"
Sent signature
Web Bot Auth (RFC 9421)
Got content-type
application/json
Got cache-control
public, max-age=300
GET /ucp 200 OK 1.4 KB · application/json 90 ms

Answered.

  • DNS 8 ms
  • Connect 14 ms
  • TLS 22 ms
  • Wait 40 ms
  • Download 5 ms
URL
https://yourstore.com/ucp
Server
203.0.113.10
Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Sent accept
application/json
Sent signature-agent
"https://ucpchecker.com"
Sent signature
Web Bot Auth (RFC 9421)
Got content-type
application/json
Got cache-control
public, max-age=300
Outside UCP · its other files3 requests · 3 × 200 OK460 ms
GET /robots.txt 200 OK 1.1 KB · text/plain 60 ms

Answered.

  • DNS 8 ms
  • Connect 14 ms
  • TLS 22 ms
  • Wait 10 ms
  • Download 5 ms
URL
https://yourstore.com/robots.txt
Server
203.0.113.10
Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Sent accept
text/plain
Sent signature-agent
"https://ucpchecker.com"
Sent signature
Web Bot Auth (RFC 9421)
Got content-type
text/plain
Got cache-control
public, max-age=300
GET / 200 OK 46.9 KB · text/html 110 ms

Answered.

  • DNS 8 ms
  • Connect 14 ms
  • TLS 22 ms
  • Wait 60 ms
  • Download 5 ms
URL
https://yourstore.com/
Server
203.0.113.10
Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Sent accept
text/html
Sent signature-agent
"https://ucpchecker.com"
Sent signature
Web Bot Auth (RFC 9421)
Got content-type
text/html
Got cache-control
public, max-age=300
GET /llms.txt 200 OK 2.2 KB · text/plain 60 ms

Answered.

  • DNS 8 ms
  • Connect 14 ms
  • TLS 22 ms
  • Wait 10 ms
  • Download 5 ms
URL
https://yourstore.com/llms.txt
Server
203.0.113.10
Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Sent accept
text/plain
Sent signature-agent
"https://ucpchecker.com"
Sent signature
Web Bot Auth (RFC 9421)
Got content-type
text/plain
Got cache-control
public, max-age=300
Links in the profile · spec, schemas, handlers3 requests · 3 × 200 OK140 ms
GET ucp.dev/2026-08-25/schemas/shopping/checkout.json 200 OK 8.8 KB · application/json 130 ms

Answered.

  • DNS 8 ms
  • Connect 14 ms
  • TLS 22 ms
  • Wait 80 ms
  • Download 5 ms
URL
https://ucp.dev/2026-08-25/schemas/shopping/checkout.json
Server
203.0.113.10
Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Sent accept
application/json
Sent signature-agent
"https://ucpchecker.com"
Sent signature
Web Bot Auth (RFC 9421)
Got content-type
application/json
Got cache-control
public, max-age=300
GET ucp.dev/2026-08-25/schemas/shopping/catalog_search.json 200 OK 5.9 KB · application/json 120 ms

Answered.

  • DNS 8 ms
  • Connect 14 ms
  • TLS 22 ms
  • Wait 70 ms
  • Download 5 ms
URL
https://ucp.dev/2026-08-25/schemas/shopping/catalog_search.json
Server
203.0.113.10
Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Sent accept
application/json
Sent signature-agent
"https://ucpchecker.com"
Sent signature
Web Bot Auth (RFC 9421)
Got content-type
application/json
Got cache-control
public, max-age=300
GET ucp.dev/2026-08-25/specification/overview/ 200 OK 87.9 KB · text/html 140 ms

Answered.

  • DNS 8 ms
  • Connect 14 ms
  • TLS 22 ms
  • Wait 90 ms
  • Download 5 ms
URL
https://ucp.dev/2026-08-25/specification/overview/
Server
203.0.113.10
Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)
Sent accept
text/html
Sent signature-agent
"https://ucpchecker.com"
Sent signature
Web Bot Auth (RFC 9421)
Got content-type
text/html
Got cache-control
public, max-age=300
  1. DISCOVERYValid against the 2026-08-25 schema; keys published
  2. TRANSPORTEmbedded service declared; not called by this check–

What the result says

Verified
The store publishes a UCP profile that is valid against the release it names. It doesn’t mean every agent purchase works: that shows only when an agent tries.
Invalid
We found a profile, but it breaks the release’s rules, for example a missing field or broken JSON. The result lists what to fix.
Not Detected
Nothing at /.well-known/ucp, usually HTTP 404. The result shows how a UCP profile starts.
Blocked
Our request was refused (HTTP 401 or 403), or robots.txt disallows it. That is what our checker met, not how the store treats other agents.
Unreachable
No answer: a timeout, a DNS or certificate error, or a server error (5xx).
Pending
In our list but not checked yet. Check it here to run it now.

Questions

Is the UCP Checker free?
Yes, with no sign-up. Checks are rate-limited so they stay fast for everyone.
Is the result live?
Pressing Check store runs a new check. A status page you open later shows when the store was last checked.
Does Verified mean UCP agents can buy here?
Not on its own. Verified means the profile is valid against its release and the services we called answered. Whether an agent can find a product and reach checkout shows only when an agent tries: UCP Playground sends one.
How is this different from the Validator?
The Checker reads a live store. The UCP Validator checks profile JSON you paste in, so you can test a profile before you publish it.
What is the UCP Score?
A number from 0 to 100 for a store whose profile we read, with the fixes that raise it. Each store’s score page shows how it is made; the methodology has the weights.