UCP Checker
Sign in Start monitoring
Back to status
tcgame.fr icon
UCP Score

UCP Score for tcgame.fr

UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.

✓Verified
A86/100
Analyzed Oct 10, 2026 · 3 recommendations ·Wix · v2026-04-08 upgrade
86
/ 100
UCP Score
A

tcgame.fr publishes a conforming profile with broad capability coverage.

Agent Discovery100
UCP Conformance81
Capability Coverage80
Working

Agent Discovery is solid (100/100).

Start Here

Fix broken spec or schema URLs → Publish the public keys agents use to check your messages → Move to the latest UCP protocol version

Verified

tcgame.fr publishes a valid UCP profile, with minor schema warnings.

Latency
372ms
Version
2026-04-08
Robots.txt
Allowed ✅

Top Priorities

1
Fix broken spec or schema URLs

One or more spec/schema URLs declared in the profile do not resolve.

Medium impact Low effort
2
Publish the public keys agents use to check your messages

Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.

Medium impact Medium effort
3
Move to the latest UCP protocol version

Your profile declares a valid but older protocol version. A newer one is published.

Low impact Low effort

Impact & Effort Matrix

Prioritised recommendations by expected impact and implementation effort

Quick Wins(0)

High impact, low effort

  • No items
Strategic Investments(0)

High impact, high effort

  • No items
Incremental Gains(2)

Medium impact & effort

  • Fix broken spec or schema URLs
  • Publish the public keys agents use to check your messages
Consider Later(1)

Lower priority

  • Move to the latest UCP protocol version

How you compare on Wix

Response time benchmarked against 7,459 Wixes we monitor.

fastWix median 410msslow
Your store
372ms
Wix percentile
Above median
Faster than 70% of Wix stores
Cohort range
365–479ms
p25 to p75 (middle half)

Recommendations

All improvements ranked by priority, with evidence and actionable fixes.

1

Fix broken spec or schema URLs

Medium impact Low effort ×6

One or more spec/schema URLs declared in the profile do not resolve.

Why it matters

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.

UCP_PROBE_URL_BROKEN
2

Publish the public keys agents use to check your messages

Medium impact Medium effort

Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.

Why it matters

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.

Show fix

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": { ... }
}
UCP_MISSING_SIGNING_KEYS
3

Move to the latest UCP protocol version

Low impact Low effort

Your profile declares a valid but older protocol version. A newer one is published.

Why it matters

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.

Show fix

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 it
UCP_VERSION_OUTDATED

Full Check Breakdown

Every signal we evaluate, grouped by category.

Functional probes ran .
Agent Discovery8/8 passed

Can AI agents find your store and its UCP profile?

  • HTTPSCore

    Profile served over a secure connection.

    Profile URL uses https://

    Why it matters

    Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.

  • UCP profile reachableCore

    Profile fetched OK from /.well-known/ucp.

    HTTP 200

    Why it matters

    Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.

  • AI bot accessCore

    robots.txt allows agent crawlers to fetch the profile.

    robots.txt allows /.well-known/ucp

    Why it matters

    Agents respect robots.txt. Even a published profile gets ignored if the file is disallowed for known agent user-agents.

  • llms.txtExperimental

    Hand-written brief at /llms.txt for AI agents.

    Found at /llms.txt

    Why it matters

    Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.

  • sitemap.xmlCore

    XML sitemap published at /sitemap.xml.

    Found at /sitemap.xml

    Why it matters

    Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.

  • Open Graph tagsCore

    OG meta tags on the homepage.

    og:title and og:type/url present

    Why it matters

    OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.

  • Organization schema (JSON-LD)Core

    Schema.org Organization (or OnlineStore) JSON-LD on homepage.

    Organization-typed JSON-LD detected

    Why it matters

    Gives agents a structured representation of your brand identity — used to verify you are who your profile claims you are.

  • Mobile viewport metaCore

    Viewport meta tag for mobile rendering.

    <meta name="viewport"> present

    Why it matters

    Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.

UCP Conformance2/5 passed

Does your profile meet the published spec?

  • Profile passes schema validationCore

    Profile structure conforms to the published UCP spec.

    No structural errors

    Why it matters

    Strict UCP agents reject profiles with structural errors. The error code in the diagnostic shows which field failed.

  • Protocol version present and well-formedCore

    ucp.version follows YYYY-MM-DD format.

    Version: 2026-04-08

    Why it matters

    UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.

  • Signing keys publishedCore

    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)

    Why it matters

    Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.

  • No validation warningsCore

    Profile passes structural and field-level rules.

    1 warning

    Why it matters

    Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.

  • Spec & schema URLs resolve (12)Core

    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, …

    Why it matters

    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.

Capability Coverage4/6 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    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.

    Why it matters

    Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.

  • Checkout capabilityCore

    Store declares a checkout-namespaced capability.

    dev.ucp.shopping.checkout detected

    Why it matters

    Without a checkout capability, agents can browse but can't complete a purchase end-to-end.

  • Transports declaredInterop

    Service transports (REST/MCP/A2A/Embedded) declared on services.

    REST, MCP

    Why it matters

    Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.

  • Payment handlersCore

    Tokenized payment handlers registered for in-conversation checkout.

    Empty array: checkout-link redirect strategy

    Why it matters

    Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.

  • REST transport reachableInterop

    Live reachability check against https://www.wixapis.com/ecom/ucp/2e4ff851-a163-4bdc-979c-20b749fe768f.

    Host responded with HTTP 404 — endpoint reachable but path may be method-restricted

    Why it matters

    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.

  • MCP transport reachableInterop

    Live reachability check against https://www.wixapis.com/ecom/ucp/2e4ff851-a163-4bdc-979c-20b749fe768f/mcp.

    tools/list returned a JSON-RPC response in 504ms

    Why it matters

    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.

/llms.txt content

The plain-text brief this store publishes to AI agents. Captured on the most recent check.

3.8 KBb392be8822b66faf
# www.tcgame.fr
> TCGame.fr est une boutique en ligne dédiée aux passionnés de jeux de cartes à collectionner (TCG), offrant une large sélection de produits populaires comme Pokémon et Lorcana, ainsi que des accessoires. Le site s'engage à construire une communauté active grâce à des événements en direct et des interactions régulières. Il détaille également ses politiques de confidentialité et ses conditions générales de vente pour assurer une expérience d'achat transparente et sécurisée. TCGame met l'accent sur la qualité, le service client et la satisfaction de sa communauté.

## Homepage link
- [home](https://www.tcgame.fr/)

## Accès des agents IA

Ce site est proposé par Wix et prend en charge le protocole MCP
pour l'accès de l'IA agentive. Les agents IA peuvent se connecter directement pour récupérer le contenu du site en ligne et à jour, sans avoir besoin d'extraire les données.

- [**Point de terminaison MCP du site**](https://www.tcgame.fr/_api/mcp)
- [**Documentation MCP de Wix**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)

## Outils MCP disponibles

### GetBusinessDetails
Récupère les détails de l'entreprise et du site tels que le fuseau horaire, l'e-mail, le téléphone et l'adresse.
- Aucun paramètre n'est requis.

### SearchInSite
Recherche des informations sur le site.
- **searchTerm** - Le terme à rechercher dans le site.

### SearchSiteApiDocs
Récupère la documentation de l'API pour les solutions professionnelles Wix installées sur ce site et informe le client IA sur la manière d'utiliser les API. Utilisez cet outil pour interroger les articles et les services (au lieu de SearchInSite).
- **searchTerm** - Le terme à rechercher dans la documentation de l'API du site.

### GenerateVisitorToken
Crée une nouvelle session de visiteur et obtient un jeton d'accès visiteur pour le site.
Doit être appelé avant d'effectuer toute requête CallWixSiteAPI si aucun jeton de visiteur n'est déjà disponible dans le contexte.
- Aucun paramètre n'est requis.

### CallWixSiteAPI
Appelle les méthodes d'API sur le site pour effectuer des actions au nom d'un visiteur, telles que l'interrogation des données du site, la réservation d'un rendez-vous ou le commencement d'un achat.
- **visitorToken** - Jeton d'accès visiteur. Utilisez GenerateVisitorToken en premier si non disponible.
- **url** - URL absolue de la méthode d'API à appeler (ex. https://www.wixapis.com/...). Récupérez en utilisant SearchSiteApiDocs.
- **method** - Méthode HTTP à utiliser pour l'appel d'API.
- **body** - Corps de la requête sous forme de chaîne JSON valide.

### ReadFullDocsArticle
Récupère un article complet du portail de documentation pour développeurs Wix.
- **articleUrl** - URL d'un article dans le portail de documentation pour développeurs Wix.

### ReadFullDocsMethodSchema
Récupère le schéma complet d'une méthode d'API Wix. Doit être appelé avant d'appeler la méthode réelle via CallWixSiteAPI.
- **articleUrl** - URL de l'article de référence pour la méthode d'API Wix.

## Ce que les visiteurs peuvent faire via l'IA + le MCP

- Obtenir les détails de l'entreprise (informations de contact, emplacement, horaires)
- Découvrir les articles et services proposés
- Effectuer des réservations
- Démarrer un achat et être redirigés vers le site pour finaliser le paiement
- Poser des questions et obtenir des réponses pertinentes sans avoir à parcourir le site

## Remarques

- Aucune authentification n'est requise pour se connecter au point de terminaison MCP
- Seules les informations publiques accessibles sur le site sont disponibles
- Le contenu est toujours en ligne et à jour
- Pour recevoir des mises à jour des outils, implémentez un appel tools/list dès réception d'une notification de mise à jour d'outil
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
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

Technical Vitals

Technical details for this UCP endpoint
UCP Status Verified
Endpoint https://tcgame.fr/.well-known/ucp
HTTP Status 200
UCP Version 2026-04-08
Transports REST, MCP
Last Observed
Last Full Index

Embed your UCP Score

Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.

UCP Score for tcgame.fr badge for https://ucpchecker.com/score/tcgame.frLive preview
Markdown
[![UCP Score for tcgame.fr](https://ucpchecker.com/score/tcgame.fr/badge.svg)](https://ucpchecker.com/score/tcgame.fr)
HTML
<a href="https://ucpchecker.com/score/tcgame.fr"><img src="https://ucpchecker.com/score/tcgame.fr/badge.svg" alt="UCP Score for tcgame.fr"></a>
New · Early access open
Is tcgame.fr yours? Claim it & monitor it daily

Prove ownership with one DNS record and the new monitoring dashboard watches it every day — score trends, break alerts, staging drift and a watchlist that benchmarks you against the field. Free while in beta.

Start monitoring →

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.

Save this report

Track tcgame.fr'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.