UCP Vendors & Extensions
Every UCP capability is governed by a domain, encoded in its reverse-DNS namespace. Grouping the live crawl by that namespace authority shows the shape of the ecosystem: the core protocol (ucp.dev) and the third-party vendors publishing their own capabilities and extensions on top of it.
Core protocol
The dev.ucp.* namespace, reserved for capabilities governed by the UCP Tech Council. Everything else extends these.
Vendors
Third parties publishing capabilities under their own reverse-DNS namespace. Per the spec, a vendor's declared schema URL must be served from its own authority domain — the badge shows whether that binding holds.
Virtocommerce
Ucpchecker
Usp Protocol
Cervicaltractions
Jobstcompressionstocking
Elastogels
Epromo
Real Ease
Appointedd
Telnyx
Protherapysupplies
Shopify
Andyhoang
Klarna
Netsgroup
Dellasale
Artos
Shiptime
Ticketfairy
Usebaci
Example
Grooveshop
Ptpge
Shopware
Trewe
A2Cn
Scvd
Hawkshift
Authority binding is a normative MUST in the UCP spec (Namespace Governance, still normative in v2026-08-25): an entity's schema URL must originate from its namespace authority domain, so a name can be proven to belong to the party that claims it. UCP Checker runs that check across the whole crawled fleet — deterministic, and neutral.
Methodology note (2026-07-28): verdicts now implement the spec's host-derived rule as refined by spec PR #627 (merged 2026-07-24): a binding passes when the entity name equals the reversed schema host exactly, or begins with it as a label-aligned prefix. This accepts the exact-match case #627 legalized and — stricter than our previous check — rejects schemas served from unaligned subdomains (e.g. a shared CDN host). Some verdicts changed on this date due to the rule change, not to any change in what merchants publish.