Free UCP visibility test
This free UCP Checker tests how clearly your products, prices, variants, and checkout paths are exposed through public UCP and MCP endpoints. One domain, one live technical test, no account required.
The test follows the same public path an agent would use.
Public endpoints · no sign-in
No permanent storage
Discover
/.well-known/ucpConnect
MCP tools/listRead
search_catalogAct
variant checkout_urlWhat the score measures
A protocol file can exist while product values are missing. The score totals 100 transparent points. Live values from up to three public products receive full credit; declared schema fields without a live sample receive partial credit.
Can an agent locate a public UCP profile or agents.md without prior configuration?
Does the declared service answer and expose recognizable UCP commerce tools? A generic MCP endpoint alone receives only partial credit.
Does a public UCP catalog request return a readable response?
Are description, brand, media, price, availability, product URL, SKU, and GTIN populated across the live sample?
Does each sampled product expose a variant-level, merchant-owned checkout URL?
MCP and UCP
The Model Context Protocol standardizes how an AI client discovers and calls tools. A working generic MCP endpoint is a useful signal, but it does not by itself describe a complete commerce journey.
MCP documentationThe Universal Commerce Protocol adds commerce-specific discovery, capabilities, catalog structures, and checkout handoffs. The test reports MCP and UCP separately so a generic server is never mistaken for a shopping-ready implementation.
UCP specificationWhat happens during a test
Heartly requests only the storefront and documented public discovery paths, caps response sizes, follows safe HTTPS redirects, and samples at most three catalog products when a public search tool is available. Results are not added to the Heartly Deals Hub; a technical cache may retain a scan for up to one hour.
It checks the public signals an AI shopping agent can discover and call, then verifies actual field completeness across up to three sample products. The result covers the UCP profile, MCP tool access, catalog readability, product data, and checkout handoff.
No. A strong result means the technical path is available and useful. Every assistant still decides which sources and tools it uses, so the score is not a ranking guarantee or certification.
No. This public test does not import or publish catalog products. When a public catalog is available, up to three examples are read to verify the response and may remain in a technical cache for up to one hour.
MCP is a general tool transport. A store can expose a generic MCP server without publishing a UCP profile, commerce capabilities, a searchable catalog, or variant-level checkout URLs.
Yes. Enter any public HTTPS storefront. The platform signal is informational; the visibility score is based on the public agent and commerce interfaces the store actually exposes.
Turn a readable catalog into active demand.
Heartly connects storefront signals with campaign automation, a public Deals Hub, Competitor Intelligence, and an AI Assistant built for commerce teams.