What does it mean that mangayo.it is verified for UCP?

It means mangayo.it publishes a valid UCP profile at /.well-known/ucp, the profile passes schema validation against 2026-08-25, and UCP agents can read what it offers from that file instead of from its web pages. That is what the store declares. Whether an agent actually completes a purchase is a separate question — where an observed agent run is shown on this page, it answers that one.

Can I trust mangayo.it for AI agent purchases?

Verified means the store publishes a UCP profile at /.well-known/ucp that passes schema validation, with its services and payment handlers declared. Where we call a service, such as asking an MCP service for its tools, this page shows the answer; services we did not call are marked as declared only. It doesn't grade business reputation or fulfilment quality. For trust on the commerce side itself, check the store's own reviews. For the agent integration side, this page shows what the store's UCP profile declares and whether it validates.

What platform does mangayo.it use for UCP?

Our detection identifies mangayo.it as running on Prestashop. The transports listed above show how its profile says agents reach it (REST, MCP, A2A or Embedded).

How was this UCP report for mangayo.it generated?

With public requests on 3 November 2026: we asked for mangayo.it/.well-known/ucp and read its robots.txt, then validated the profile against the UCP release it declares and checked that its spec and schema links resolve. No sign-in, no purchase and no manual review. How we check.

How do I get a newer result for mangayo.it?

This page shows the stored result of our last check (3 November 2026). To run a new one, enter mangayo.it on the Check page.

Why does this status matter?

Universal Commerce Protocol is an open standard that lets a UCP agent find out what a store sells, build a cart and check out through a published contract instead of reading web pages. A valid UCP profile is how a store declares that support.

UCP Score

UCP Score for mangayo.it

Nearly there

83 out of 100, grade B: nearly there. The missing 17 points are spread across Conformance and Capabilities. One spec break on the status page isn't counted in the score.

Discovery 100Conformance 97Capabilities 48release 2026-08-25

UCP Score 83/100 grade B · nearly there

Points missing 17 Conformance, Capabilities Fixes 0 raise the score 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.

97−1.2 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.

48−15.6 pts

A85–100Ready for UCP agents

B70–84Nearly there

C50–69Partly ready

D30–49Hard for UCP agents

F0–29Not ready

Raise the score

nothing left to fix in the score

Every scored check passed.

Every check

12 passed · 4 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 · 3 of 4

3 OK

Profile passes schema validation, Protocol version present and well-formed, Public keys publishedShow

Profile passes schema validation · No structural errors
Protocol version present and well-formed · Version: 2026-08-25
Public keys published · Keys published at the top level

To fix

No validation warnings

1 warning.

Conformance

Capability Coverage · 1 of 4

1 OK

Transports declaredShow

Transports declared · REST

To fix

Capabilities declared

1 of 6 capability families detected: Catalog. A family counts once however many namespaces or extensions declare it.

Capabilities

Problem

Checkout capability

No checkout capability.

Capabilities

To fix

Payment handlers

Empty array: checkout-link redirect strategy.

Capabilities

Not in the score, but worth fixing first

spec breaks

To fix

The profile has no ETag or Last-Modified header

Spec level: SHOULD.

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.