Scan at scaleSites with a broken UCP profile
Sites with a broken UCP profile
A site-wide report: one row per host, over the ucp rows the crawl emitted.
What this report returns
A UCP profile (/.well-known/ucp, the emerging Google/Shopify Universal Commerce Protocol) declares the endpoints and capabilities agents can transact through.
These sites serve a profile agents can't use: invalid JSON, a version that isn't a real YYYY-MM-DD date, a missing services or payment_handlers registry (UCP requires both keys, even when empty), or no connectable transport to reach.
How to fix it. Serve { "ucp": { "version": "2026-01-15", "services": ..., "payment_handlers": {} } } with at least one rest/mcp/a2a service on an https endpoint (or an embedded binding). The Conformance column separates the two kinds of row: it is true where the profile breaks the UCP schema, and false where the profile is valid UCP that simply advertises nothing an agent can connect to.
(A profile with no declared capabilities is shown for context: capabilities are optional in UCP, so their absence doesn't make the profile invalid, but declaring them tells agents what you support.)
The columns it shows
Every defect this technology can carry is a column in the grid, worst first, so nothing is hidden behind a filter you have to know to apply.
- Host
host - UCP Profile Valid
ucpValid - UCP Profile Conformance Issue Detected
ucpConformanceIssueDetected - UCP Findings
ucpFindings - UCP Declared Version
ucpDeclaredVersion - UCP Capability Names
ucpCapabilityNames - UCP Transport Names
ucpTransportNames - UCP Invalid Document
ucpInvalidDocument - UCP Missing Required Registries
ucpMissingRequiredRegistries - UCP Missing Transports
ucpMissingTransports - UCP Missing Capabilities
ucpMissingCapabilities - UCP Invalid Version
ucpInvalidVersion
About UCP profile
Universal Commerce Protocol discovery for agentic shopping.
Read how UCP profile is checked, including the specification it is validated against and a worked correct and broken example.
Running it
This report ships in the Lumar agent-readiness container and appears on any project it is linked to, on every crawl. See the whole set, or check a single URL with the scanner on this site, which runs the same code with no account.