UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
swissclassicworld.ch publishes a conforming profile with broad capability coverage.
Agent Discovery is solid (95/100).
Fix broken spec or schema URLs → Publish the public keys agents use to check your messages → Move to the latest UCP protocol version
One or more spec/schema URLs declared in the profile do not resolve.
Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.
Your profile declares a valid but older protocol version. A newer one is published.
Prioritised recommendations by expected impact and implementation effort
High impact, low effort
High impact, high effort
Medium impact & effort
Lower priority
Response time benchmarked against 7,452 Wixes we monitor.
All improvements ranked by priority, with evidence and actionable fixes.
One or more spec/schema URLs declared in the profile do not resolve.
Spec and schema URLs let agents validate request/response shapes before sending. When they 404 or time out, runtime validation degrades to "best effort" and strict agents reject the integration entirely. Common cause: copy-pasting a placeholder URL during initial profile setup. See the Full Check Breakdown for the specific URLs that failed.
Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.
Agents use these keys to check that checkout messages really came from you. A store that takes payment through the agent needs them. A store that sends the buyer to its own checkout page can manage without them for now.
Create an Ed25519 key pair. Add the public key to a "keys" list at the top level of your UCP profile, as in the example, and keep the private key on your server. Replace the key once a year, giving each new key its own "kid".
{
"keys": [
{
"kty": "OKP",
"crv": "Ed25519",
"x": "<base64url-encoded-public-key>",
"kid": "key-2026-04",
"alg": "EdDSA"
}
],
"ucp": { ... }
}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.
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.
"ucp": {
"version": "2026-08-25",
...
},
"keys": [ ... ] // beside "ucp", not inside itNo 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.
Most ecommerce platforms generate sitemap.xml automatically. If yours does not, generate one and serve it at /sitemap.xml.
<?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>Every signal we evaluate, grouped by category.
Can AI agents find your store and its UCP profile?
Profile served over a secure connection.
Profile URL uses https://
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
Profile fetched OK from /.well-known/ucp.
HTTP 200
Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.
robots.txt allows agent crawlers to fetch the profile.
robots.txt allows /.well-known/ucp
Agents respect robots.txt. Even a published profile gets ignored if the file is disallowed for known agent user-agents.
Hand-written brief at /llms.txt for AI agents.
Found at /llms.txt
Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.
XML sitemap published at /sitemap.xml.
HTTP 404 at /sitemap.xml
Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.
OG meta tags on the homepage.
og:title and og:type/url present
OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.
Schema.org Organization (or OnlineStore) JSON-LD on homepage.
Organization-typed JSON-LD detected
Gives agents a structured representation of your brand identity — used to verify you are who your profile claims you are.
Viewport meta tag for mobile rendering.
<meta name="viewport"> present
Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.
Does your profile meet the published spec?
Profile structure conforms to the published UCP spec.
No structural errors
Strict UCP agents reject profiles with structural errors. The error code in the diagnostic shows which field failed.
ucp.version follows YYYY-MM-DD format.
Version: 2026-04-08
UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.
Root-level keys array (canonical since 2026-07-12; legacy signing_keys also accepted) for response verification.
No signing_keys at root (common for managed/redirect-checkout stores)
Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.
Profile passes structural and field-level rules.
1 warning
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Resolves the 12 spec/schema URLs declared across the profile to confirm agents can fetch each one.
Did not resolve (6 of 12): https://ucp.dev/services/shopping/rest.openapi.json, https://ucp.dev/schemas/shopping/cart.json, https://ucp.dev/schemas/shopping/catalog-lookup.json, https://ucp.dev/schemas/shopping/checkout.json, https://ucp.dev/schemas/shopping/fulfillment.json, …
Spec and schema URLs let agents validate request/response shapes before sending. Broken URLs degrade runtime validation to "best effort" and cause strict agents to refuse the capability entirely.
What operations can agents actually perform?
Number of agent-readable capabilities under ucp.capabilities.
3 of 6 capability families detected: Checkout, Cart Management, Catalog. A family counts once however many namespaces or extensions declare it.
Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.
Store declares a checkout-namespaced capability.
dev.ucp.shopping.checkout detected
Without a checkout capability, agents can browse but can't complete a purchase end-to-end.
Service transports (REST/MCP/A2A/Embedded) declared on services.
REST, MCP
Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.
Tokenized payment handlers registered for in-conversation checkout.
Empty array: checkout-link redirect strategy
Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.
Live reachability check against https://www.wixapis.com/ecom/ucp/eb660baa-fb61-43aa-a037-52be83af3b3a.
Host responded with HTTP 404 — endpoint reachable but path may be method-restricted
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the profile itself looks perfect.
Live reachability check against https://www.wixapis.com/ecom/ucp/eb660baa-fb61-43aa-a037-52be83af3b3a/mcp.
tools/list returned a JSON-RPC response in 189ms
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the profile itself looks perfect.
The plain-text brief this store publishes to AI agents. Captured on the most recent check.
# SWISS CLASSIC WORLD
> Die SWISS CLASSIC WORLD ist eine Oldtimer-Messe, die in Luzern stattfindet und eine Vielzahl von Veranstaltungen und Ausstellungen rund um klassische Fahrzeuge bietet. Die Website enthält Informationen zu Kontaktmöglichkeiten, Akkreditierung für Medien, allgemeinen Geschäftsbedingungen und Datenschutz. Sie wirbt auch für spezielle Events wie "Harder than Steel" und "ACS Forever Young", die Fahrten für Oldtimer und Youngtimer beinhalten. Die Seite bietet zudem Downloads von Pressematerialien und Videos zur Messe.
## Homepage link
- [home](https://www.swissclassicworld.ch/)
## KI-Agenten-Zugriff
Diese Website wird von Wix betrieben und unterstützt das Model Context Protocol (MCP)
für den Zugriff durch KI-Agenten. KI-Agenten können sich direkt verbinden, um Live- und aktuelle Website-Inhalte abzurufen – kein Scraping erforderlich.
- [**MCP-Endpoint der Website**](https://www.swissclassicworld.ch/_api/mcp)
- [**Wix MCP-Docs**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)
## Verfügbare MCP-Tools
### GetBusinessDetails
Ruft Geschäfts- und Website-Details wie Zeitzone, E-Mail-Adresse, Telefonnummer und Adresse ab.
- Keine Parameter erforderlich.
### SearchInSite
Durchsucht die Website nach Informationen.
- **searchTerm** – Der Suchbegriff auf der Website.
### SearchSiteApiDocs
Ruft die API-Dokumentation für die auf dieser Website installierten Wix-Unternehmenslösungen ab und informiert den KI-Client, wie die APIs verwendet werden. Verwende dieses Tool zum
Abfragen von Produkten und Services (anstelle von SearchInSite).
- **searchTerm** – Der Suchbegriff in der API-Dokumentation der Website.
### GenerateVisitorToken
Erstellt eine neue Besucher-Session und ruft ein Besucher-Zugriffstoken für die Website ab.
Muss vor jeder CallWixSiteAPI-Anfrage aufgerufen werden, wenn kein Besucher-Token
im Kontext verfügbar ist.
- Keine Parameter erforderlich.
### CallWixSiteAPI
Ruft API-Methoden auf der Website auf, um Aktionen im Namen eines Besuchers auszuführen,
wie das Abfragen von Website-Daten, das Buchen eines Termins oder das Starten eines Kaufs.
- **visitorToken** – Besucher-Zugriffstoken. Verwende GenerateVisitorToken zuerst, falls nicht verfügbar.
- **url** – Absolute URL der API-Methode, die aufgerufen werden soll (z. B. https://www.wixapis.com/...). Abrufen mit SearchSiteApiDocs.
- **method** – HTTP-Methode, die für den API-Aufruf verwendet werden soll.
- **body** – Anfragetext als gültige JSON-Zeichenfolge.
### ReadFullDocsArticle
Ruft einen vollständigen Artikel aus dem Wix-Entwickler-Dokumentationsportal ab.
- **articleUrl** – URL eines Artikels im Wix-Entwickler-Dokumentationsportal.
### ReadFullDocsMethodSchema
Ruft das vollständige Schema für eine Wix API-Methode ab. Sollte vor dem
Aufruf der eigentlichen Methode über CallWixSiteAPI aufgerufen werden.
- **articleUrl** – URL des Referenzartikels für die Wix API-Methode.
## Was Besucher über KI + MCP tun können
- Unternehmensdetails abrufen (Kontaktangaben, Standort, Öffnungszeiten)
- Produkte und Services im Angebot entdecken
- Services buchen und Reservierungen vornehmen
- Einen Kauf starten und zur Website weitergeleitet werden, um den Checkout abzuschließen
- Fragen stellen und relevante Antworten erhalten, ohne die Website durchsuchen zu müssen
## Hinweise
- Keine Authentifizierung erforderlich, um sich mit dem MCP-Endpoint zu verbinden
- Nur öffentliche Informationen, die auf der Website zugänglich sind, sind verfügbar
- Content ist immer live und aktuell
- Um Tool-Updates zu erhalten, implementiere einen Tools/Listen-Aufruf nach Erhalt einer Tool-Update-Benachrichtigung| Cart ✓ Bound | 2026-04-08 |
| Checkout ✓ Bound | 2026-04-08 |
| Fulfillment Extension ✓ Bound | 2026-04-08 |
| Catalog Lookup ✓ Bound | 2026-04-08 |
| Catalog Search ✓ Bound | 2026-04-08 |
| UCP Status | Verified |
| Endpoint | https://swissclassicworld.ch/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-04-08 |
| Transports | REST, MCP |
| Last Observed | |
| Last Full Index |
Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.
Live preview[](https://ucpchecker.com/score/swissclassicworld.ch)<a href="https://ucpchecker.com/score/swissclassicworld.ch"><img src="https://ucpchecker.com/score/swissclassicworld.ch/badge.svg" alt="UCP Score for swissclassicworld.ch"></a>This score reflects data from the most recent crawl. Run a fresh check to update, or read the methodology to see how each signal is scored.
Track swissclassicworld.ch's UCP score over time. We'll re-run the full check weekly and email you if the score drops, a capability regresses, or status flips.
Free. One email when something changes — no marketing. Privacy.
Track domains and get emailed when their UCP status changes.
By continuing you agree to our Terms & Privacy Policy.