UCP Checker
Check a store
UCP Score

UCP Score for mirasvit.com

Ready for UCP agents

86 out of 100, grade A: ready for UCP agents. The missing 14 points are spread across Discovery and Conformance and Capabilities. 2 spec breaks on the status page aren't counted in the score.

Discovery 95Conformance 97Capabilities 62release 2026-04-08

UCP Score 86/100 grade A · ready for UCP agents
Points missing 14 Discovery, Conformance, Capabilities Fixes 2 raise the score Spec breaks 2 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).
95−1.5 pts
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.
62−11.4 pts
A85–100Ready for UCP agents
B70–84Nearly there
C50–69Partly ready
D30–49Hard for UCP agents
F0–29Not ready

Raise the score

fixes that move the number
+1
1Move to the latest UCP protocol version
Your profile declares a valid but older protocol version. A newer one is published.
Older versions stay valid (agents use the version you declare), but newer abilities (embedded checkout, agent payment mandates, linked customer accounts, card authentication, payment terms and store location lookup) only work against the latest version. The profile itself barely changes: the signing keys move to a root-level "keys" list, and the rest of the update is in what capabilities can say.
Conformance · effort low 
"ucp": {
  "version": "2026-08-25",
  ...
},
"keys": [ ... ]   // beside "ucp", not inside it

Set the version to 2026-08-25 and publish your public keys as a root-level "keys" list. The older "signing_keys" field is still accepted, but "keys" is the one every verifier reads.

+2
2Publish a sitemap.xml
No sitemap.xml detected at the root of your domain.
Sitemaps tell agents and crawlers which pages on your store are canonical and how often they change. Without one, agents fall back to following internal links, which is slower and less complete, especially for catalog pages buried behind faceted nav.
Discovery · effort low 
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yourstore.com/</loc>
    <changefreq>daily</changefreq>
  </url>
  <url>
    <loc>https://yourstore.com/products</loc>
    <changefreq>daily</changefreq>
  </url>
  <!-- one <url> entry per indexable page -->
</urlset>

Most ecommerce platforms generate sitemap.xml automatically. If yours does not, generate one and serve it at /sitemap.xml.

Every check

13 passed · 5 to fix
Agent Discovery · 7 of 8
7 OK
HTTPS, UCP profile reachable, AI bot access, llms.txt, 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
  • 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
Problem
sitemap.xml
HTTP 404 at /sitemap.xml. Fix 2 above.
Discovery
UCP Conformance · 4 of 5
4 OK
Profile passes schema validation, Protocol version present and well-formed, Public keys published, Spec & schema URLs resolve (7)Show
  • Profile passes schema validation · No structural errors
  • Protocol version present and well-formed · Version: 2026-04-08
  • Public keys published · Keys published at the top level
  • Spec & schema URLs resolve (7) · All 7 URLs resolved.
To fix
No validation warnings
1 warning.
Conformance
Capability Coverage · 2 of 5
2 OK
Transports declared, MCP transport reachableShow
  • Transports declared · MCP
  • MCP transport reachable · tools/list returned a JSON-RPC response in 417ms
To fix
Capabilities declared
2 of 6 capability families detected: Cart Management, 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
Problem
The profile isn't served with the caching the spec requires
Served with Cache-Control "no-store, no-cache, must-revalidate, max-age=0". Spec level: MUST. Not part of the UCP Score.
on the status page
To fix
The profile has no ETag or Last-Modified header
Spec level: SHOULD. Not part of the UCP Score.
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.

Files for agents

outside UCP · not part of the UCP Score

Files mirasvit.com publishes for agents beyond its UCP profile, from our weekly look. Only what we found is listed.

Found
agents.md /agents.md
Instructions for agents that visit the store.
13 Oct
/agents.md as served 1.8 KB 
# Agent Instructions — Mirasvit Magento Extensions Store

This store supports AI-driven catalogue discovery over the Universal Commerce Protocol (UCP).

## Commerce Protocol (UCP)
- [UCP Discovery](https://mirasvit.com/.well-known/ucp) — GET, merchant profile: versions, capabilities
- [MCP endpoint](https://mirasvit.com/agent/mcp) — POST, Content-Type: application/json

### Typical agent flow (v1)
1. Discover  — GET /.well-known/ucp
2. Search    — search_catalog
3. Inspect   — get_product / lookup_catalog
4. Cart      — create_cart, then give the shopper the returned continue_url to review and complete
(The agent builds the cart; the shopper completes checkout in the browser — checkout requires human approval.)

### Supported UCP versions
- 2026-04-08 (latest stable)
- 2026-01-23

### Rules
- Pass context.address_country and context.currency for accurate pricing/availability.
- Respect rate limits; back off on 429.
- Checkout requires human approval. Do not complete payment without explicit buyer consent.

## Read-Only Browsing (No Authentication Required)
The store serves these JSON endpoints itself (no auth, no GraphQL dependency):
- [Products / search](https://mirasvit.com/agent/products.json?q={query}&page={n}) — GET
- [Single product](https://mirasvit.com/agent/products/{url_key}.json) — GET
- [Category products](https://mirasvit.com/agent/collections/{url_key}/products.json) — GET
- [Sitemap](https://mirasvit.com/sitemap.xml) — GET
- Agent discovery — /agents.md (canonical) and /llms.txt (mirror), plus /.well-known/ucp

## Store Policies

- [License Agreement](https://mirasvit.com/license-agreement.html)

- [Privacy Policy](https://mirasvit.com/privacy-policy.html)

- [Rewards Policy](https://mirasvit.com/rewards-policy.html)

- [Terms & Conditions](https://mirasvit.com/terms-conditions.html)
Speed among Magento stores
The profile answered in 395 ms, faster than 100% of the Magento stores we check.