UCP status report
laskakit.cz
laskakit.cz publishes a valid UCP profile, but one thing in it breaks the spec: an agent that follows the rules won't find it at laskakit.cz.
ShoptetRESTHTTP 200 in 679 msrelease 2026-08-25
UCP Score→
87/100
grade A · ready for UCP agents
To fix→
5
1 breaks the spec
Passed
11
checks
Checked
25 Oct
03:14 UTC · public requests
Discovery
Problem
/.well-known/ucp
The profile sits behind a redirect
/.well-known/ucp
laskakit.cz/.well-known/ucp answers 301 redirect. The spec forbids redirects on the profile, so an agent that asks laskakit.cz stops there. Serve it directly on every host agents use. How to fix →
To fix
The profile has no ETag or Last-Modified header
Spec level: SHOULD. Not part of the UCP Score. How to fix →
OK
https
HTTPS
https
Profile URL uses https://
OK
/.well-known/ucp
UCP profile reachable
/.well-known/ucp
HTTP 200
OK
robots.txt
AI bot access
robots.txt
robots.txt allows /.well-known/ucp
UCP profile
To fix
keys
Publish the public keys agents use to check your messages
keys
Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store. How to fix →
OK
ucp
Profile passes schema validation
ucp
No structural errors
OK
ucp.version
Protocol version present and well-formed
ucp.version
Version: 2026-08-25
Services
Note
Confirm checkout-link redirect strategy
payment_handlers is present but empty — agents will not be able to complete purchases via tokenized payment flow. If this store uses checkout-link redirects, this is expected.
OK
capabilities
Capabilities declared
capabilities
3 of 6 capability families detected: Checkout, Cart Management, Catalog. A family counts once however many namespaces or extensions declare it.
OK
shopping.checkout
Checkout capability
shopping.checkout
dev.ucp.shopping.checkout detected
OK
services
Transports declared
services
REST
Outside UCP
To fix
JSON-LD
Publish Organization schema (JSON-LD) on the homepage
JSON-LD
No Organization-typed JSON-LD detected on your homepage. How to fix →
To fix
/llms.txt
Publish a /llms.txt brand brief
/llms.txt
No /llms.txt file detected at the root of your domain. How to fix →
OK
/sitemap.xml
sitemap.xml
/sitemap.xml
Found at /sitemap.xml
OK
og: meta
Open Graph tags
og: meta
og:title and og:type/url present
OK
meta viewport
Mobile viewport meta
meta viewport
<meta name="viewport"> present
Check trace
How laskakit.cz answered our check
The five ways an agent can reach this store, what each one met, and every request we made.
0 of 5 open · 1 breaks the spec
5 requests · 679 ms at the store · public requests only
5 requests · 679 ms at the store · public requests only
-
Finding the profileRedirect
-
Acting for the buyerNot offered
-
In the buyer's browserNot offered
-
Calling its servicesDeclared
-
Sending the buyer to the websiteNot declared
UCP Checkerpublic requests
- 3 requestsFinding the profile301 → 200
- read from profileActing for the buyernot declared
- read from profileIn the buyer's browsernot declared
- not calledCalling its servicesREST · declared · 0 tools
- read from profileSending to the websitenot declared
- 2 requestsOutside UCPhomepage · /llms.txt
Redirect
01 · Finding the profile3 requests
Only served after a redirect. An agent that follows the spec asks laskakit.cz, gets the redirect and stops: the spec forbids redirects on the profile.
laskakit.cz301 redirect
after the redirect200
Not offered
02 · Acting for the buyerread from profile
The profile doesn't declare identity linking, so an agent can't act for a signed-in buyer.
Not offered
03 · In the buyer's browserread from profile
No Embedded service is declared.
Declared
04 · Calling its servicesnot called
The REST service is declared; not called by this check.
Not declared
05 · Sending the buyer to the websiteread from profile
No permalink declared. Whether error replies carry a continue_url shows only in an agent run.
- 01 PROFILEGET laskakit.cz/.well-known/ucp → 301 redirect–
- 01 PROFILEAfter the redirect, GET /.well-known/ucp → 200, 1.6 KB of JSON679 ms
- 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
- 01 PROFILEValid against the 2026-08-25 schema; no keys publishedlocal
- OUTSIDE UCPGET / → 200, no Organization schema found–
- OUTSIDE UCPGET /llms.txt → 200, not found–
The tools laskakit.cz's MCP service listed when we asked (tools/list), grouped by the capability in its profile that calls for them. Struck through: expected but not listed.
Catalog searchdev.ucp.shopping.catalog.search
search_catalog Catalog lookupdev.ucp.shopping.catalog.lookup
lookup_catalogget_product Cartdev.ucp.shopping.cart
create_cartget_cartupdate_cartcancel_cart Checkoutdev.ucp.shopping.checkout
create_checkoutget_checkoutupdate_checkoutcomplete_checkoutcancel_checkout Capabilities
5 declared, all at 2026-08-25
Cart
shopping.cart
Checkout
shopping.checkout
Fulfillmentextension
shopping.fulfillment
Catalog Lookup
shopping.catalog.lookup
Catalog Search
shopping.catalog.search
UCP profile as served 2.5 KB · 66 lines
{
"ucp": {
"version": "2026-08-25",
"business": {
"url": "https://www.laskakit.cz",
"name": "LaskaKit",
"contact": "[email protected]",
"supported_currencies": [
"CZK",
"EUR",
"PLN",
"USD"
]
},
"services": {
"dev.ucp.shopping": [
{
"spec": "https://ucp.dev/2026-08-25/specification/overview",
"schema": "https://ucp.dev/2026-08-25/services/shopping/rest.openapi.json",
"version": "2026-08-25",
"endpoint": "https://www.laskakit.cz/ucp/v1",
"transport": "rest"
}
]
},
"capabilities": {
"dev.ucp.shopping.cart": [
{
"spec": "https://ucp.dev/2026-08-25/specification/shopping/cart",
"schema": "https://ucp.dev/2026-08-25/schemas/shopping/cart.json",
"version": "2026-08-25"
}
],
"dev.ucp.shopping.checkout": [
{
"spec": "https://ucp.dev/2026-08-25/specification/shopping/checkout",
"schema": "https://ucp.dev/2026-08-25/schemas/shopping/checkout.json",
"version": "2026-08-25"
}
],
"dev.ucp.shopping.fulfillment": [
{
"spec": "https://ucp.dev/2026-08-25/specification/shopping/extensions/fulfillment",
"schema": "https://ucp.dev/2026-08-25/schemas/shopping/fulfillment.json",
"extends": "dev.ucp.shopping.checkout",
"version": "2026-08-25"
}
],
"dev.ucp.shopping.catalog.lookup": [
{
"spec": "https://ucp.dev/2026-08-25/specification/shopping/catalog/lookup",
"schema": "https://ucp.dev/2026-08-25/schemas/shopping/catalog_lookup.json",
"version": "2026-08-25"
}
],
"dev.ucp.shopping.catalog.search": [
{
"spec": "https://ucp.dev/2026-08-25/specification/shopping/catalog/search",
"schema": "https://ucp.dev/2026-08-25/schemas/shopping/catalog_search.json",
"version": "2026-08-25"
}
]
},
"payment_handlers": []
}
}
Is laskakit.cz your store?
Claim it with one DNS record.
[](https://ucpchecker.com/status/laskakit.cz)
Can UCP agents buy from laskakit.cz?
Through its REST service, an agent can search the catalogue, build a cart and start a checkout. But the profile is only served after a redirect from laskakit.cz, and the spec forbids that, so an agent that follows the rules stops before it starts. This is what the store declares and what our check reached; an observed agent run shows how far an agent actually gets.
Is laskakit.cz ready for UCP agents?
laskakit.cz publishes a valid UCP profile and scores 87/100 (grade A). 5 things to fix: the profile sits behind a redirect, the profile has no ETag or Last-Modified header, publish the public keys agents use to check your messages and publish Organization schema (JSON-LD) on the homepage.
What is a UCP profile?
The JSON file a store publishes at
/.well-known/ucp to tell UCP agents which services it offers, how to call them and how it takes payment. The spec calls it the business profile. laskakit.cz's is 1.6 KB, written for UCP 2026-08-25. What goes in a UCP profile.How was laskakit.cz checked?
With public requests on 25 Oct 2026: we read
/.well-known/ucp and robots.txt, validated the profile against UCP 2026-08-25, checked that its spec and schema links resolve. No sign-in and no purchase. How we check.