UCP Checker
Check a store
UCP status report

alafary.com

Verified

alafary.com publishes a valid UCP profile. The checks below list what is still worth adding.

ZidHTTP 200 in 373 msrelease 2026-04-08

UCP Score 76/100 grade B · nearly there To fix 9 2 break the spec
Passed 11 checks
Checked 21 Oct 06:24 UTC · public requests

Findings

11 passed · 9 to fix
Discovery
Problem
The profile isn't served with the caching the spec requires
Served without a Cache-Control header. Spec level: MUST. Not part of the UCP Score. 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
Profile URL uses https://
https
OK
UCP profile reachable
/.well-known/ucp
HTTP 200
/.well-known/ucp
OK
AI bot access
robots.txt
robots.txt allows /.well-known/ucp
robots.txt
UCP profile
To fix
supported_versions isn't laid out the way the spec says
Spec level: SHOULD. Not part of the UCP Score. How to fix →
Problem
Declare a transport on the service
Service entry has no "transport" field and no legacy nested transport. How to fix →
To fix
Name services the way the spec does
ucp.shopping
A service is not named in the spec's dotted form (e.g. dev.ucp.shopping). How to fix →
ucp.shopping
To fix
Name payment handlers the way the spec does
A payment handler is not named in the spec's dotted form (e.g. com.google.pay). How to fix →
To fix
Add version to each payment handler
A payment handler is missing the required "version" field. How to fix →
To fix
Move to the latest UCP protocol version
ucp.version
Your profile declares a valid but older protocol version. A newer one is published. How to fix →
ucp.version
OK
Profile passes schema validation
ucp
No structural errors
ucp
OK
Protocol version present and well-formed
ucp.version
Version: 2026-04-08
ucp.version
OK
Public keys published
keys
Keys published at the top level
keys
OK
Spec/schema URL resolves
spec, schema
All 1 URLs resolved.
spec, schema
Outside UCP
To fix
Publish a /llms.txt brand brief
/llms.txt
No /llms.txt file detected at the root of your domain. How to fix →
/llms.txt
OK
sitemap.xml
/sitemap.xml
Found at /sitemap.xml
/sitemap.xml
OK
Open Graph tags
og: meta
og:title and og:type/url present
og: meta
OK
Organization schema (JSON-LD)
JSON-LD
Organization-typed JSON-LD detected
JSON-LD
OK
Mobile viewport meta
meta viewport
<meta name="viewport"> present
meta viewport
Check trace

How alafary.com answered our check

The five ways an agent can reach this store, what each one met, and every request we made.

1 of 5 open
4 requests · 373 ms at the store · public requests only
  1. 01Hosting ↗
    Finding the profile
    Open
  2. 02Identity Linking ↗
    Acting for the buyer
    Not offered
  3. 03Embedded ↗
    In the buyer's browser
    Not offered
  4. 04Services ↗
    Calling its services
    None
  5. 05continue_url ↗
    Sending the buyer to the website
    Not declared
UCP Checkerpublic requests
  • 2 requestsFinding the profile/.well-known/ucp · 200
  • read from profileActing for the buyernot declared
  • read from profileIn the buyer's browsernot declared
  • not calledCalling its servicesnone declared
  • read from profileSending to the websitenot declared
  • 2 requestsOutside UCPhomepage · /llms.txt
Open
01 · Finding the profile2 requests
Served at /.well-known/ucp with 200 OK, 1.3 KB. robots.txt allows /.well-known/ucp.
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.
None
04 · Calling its servicesnot called
No services are declared.
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.
  1. 01 PROFILEGET /.well-known/ucp → 200, 1.3 KB of JSON373 ms
  2. 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
  3. 01 PROFILEValid against the 2026-04-08 schema; no keys publishedlocal
  4. 01 PROFILE1 of 1 spec and schema URLs in the profile resolvespec hosts
  5. OUTSIDE UCPGET / → 200, Organization schema found–
  6. OUTSIDE UCPGET /llms.txt → 404, not found–

MCP tools

0 listed

The tools alafary.com's MCP service listed when we asked (tools/list), grouped by the capability in its profile that calls for them.

Capabilities

2 declared, all at 2026-04-08
Search shopping.search
Catalog shopping.catalog

Payment handlers

1 declared
tamara tamara
UCP profile as served 2.0 KB · 58 lines 
{
    "ucp": {
        "version": "2026-04-08",
        "services": [
            {
                "binding": {
                    "type": "rest",
                    "endpoint": "https://alafary.com/api/v1/ucp"
                },
                "version": "2026-04-08",
                "spec_url": "https://ucp.dev/latest/specification/overview/"
            }
        ],
        "capabilities": {
            "dev.ucp.shopping.search": {
                "spec": "https://ucp.dev/latest/specification/reference/",
                "version": "2026-04-08"
            },
            "dev.ucp.shopping.catalog": {
                "spec": "https://ucp.dev/latest/specification/reference/",
                "version": "2026-04-08"
            }
        },
        "payment_handlers": [
            {
                "id": "tamara",
                "name": "tamara",
                "type": "external_redirect",
                "icon_url": "https://media.zid.store/static/tamara2.svg",
                "instruments": [
                    {
                        "name": "Buy Now Pay Later",
                        "type": "bnpl"
                    }
                ],
                "supported_currencies": [
                    "SAR"
                ]
            }
        ],
        "supported_versions": [
            "2026-04-08"
        ],
        "default_payment_handler_id": "tamara"
    },
    "merchant": {
        "name": "العفاري | Alafary",
        "logo_url": "https://media.zid.store/cdn-cgi/image/fit=scale-down,width=200/https://media.zid.store/cb45e009-ecf2-4e6a-b45b-e9affc2afa3a/a9236ede-5aa2-43f7-9408-a521474a2003.png",
        "description": "",
        "website_url": "https://alafary.com/?utm_source=ucp&utm_medium=ai&utm_campaign=ucp"
    },
    "legal_links": {
        "return_policy": "https://alafary.com/pages/refund-exchange-policy",
        "privacy_policy": "https://alafary.com/pages/privacy-policy",
        "terms_of_service": "https://alafary.com/pages/terms-and-conditions"
    },
    "signing_keys": []
}
What goes in a UCP profile →Check your JSON in the Validator →Guides by store platform →
Is alafary.com your store?
Claim it with one DNS record.
Claim this store Send an agent to shop here ↗

Status badge

Markdown · 
[![UCP Status](https://ucpchecker.com/badge/alafary.com)](https://ucpchecker.com/status/alafary.com)

Questions

Can UCP agents buy from alafary.com?
alafary.com's profile declares no service an agent can call directly. This is what the store declares and what our check reached; an observed agent run shows how far an agent actually gets.
Is alafary.com ready for UCP agents?
alafary.com publishes a valid UCP profile and scores 76/100 (grade B). 9 things to fix: the profile isn't served with the caching the spec requires, supported_versions isn't laid out the way the spec says, the profile has no ETag or Last-Modified header and declare a transport on the service.
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. alafary.com's is 1.3 KB, written for UCP 2026-04-08. What goes in a UCP profile.
How was alafary.com checked?
With public requests on 21 Oct 2026: we read /.well-known/ucp and robots.txt, validated the profile against UCP 2026-04-08, checked that its spec and schema links resolve. No sign-in and no purchase. How we check.