UCP Checker
Back to status
thermaoasi.com icon
UCP Score

UCP Score for thermaoasi.com

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

✓Verified
A90/100
Analyzed Oct 11, 2026 · 2 recommendations ·Wix · v2026-04-08 upgrade
90
/ 100
UCP Score
A

thermaoasi.com publishes a conforming profile with broad capability coverage.

Agent Discovery100
UCP Conformance88
Capability Coverage81
Working

Agent Discovery is solid (100/100).

Start Here

Publish the public keys agents use to check your messages → Move to the latest UCP protocol version

Verified

thermaoasi.com publishes a valid UCP profile, with minor schema warnings.

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

Top Priorities

1
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
2
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(1)

Medium impact & effort

  • 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,457 Wixes we monitor.

fastWix median 398msslow
Your store
396ms
Wix percentile
Above median
Faster than 51% of Wix stores
Cohort range
359–461ms
p25 to p75 (middle half)

Recommendations

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

1

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
2

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.

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/4 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.

Capability Coverage3/4 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.

/llms.txt content

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

3.7 KBaafb4298625f8b46
# Therma Oasi Viterbo
> Il sito web fornisce informazioni dettagliate sulla "Terme Naturali di Viterbo Oasi", una Natural SPA situata a Viterbo. La pagina include un'informativa sulla privacy che descrive le tipologie di dati trattati, le finalità del trattamento, le modalità di conservazione e i diritti degli utenti. Vengono inoltre presentati i benefici terapeutici delle acque termali sulfuree, le certificazioni ottenute dal Ministero della Salute e dall'Università di Napoli Federico II, e i dettagli sui prezzi e gli orari di apertura. Il sito promuove le proprietà curative e rilassanti delle terme, evidenziando l'efficacia delle acque per diverse patologie.

## Homepage link
- [home](https://www.thermaoasi.com/)

## Accesso Assistente AI

Questo sito è powered by Wix e supporta il Model Context Protocol (MCP)
per l'accesso dell'AI assistiva. Gli assistenti AI possono collegarsi direttamente per recuperare contenuti del sito in tempo reale e aggiornati, senza bisogno di scraping.

- [**Endpoint MCP del sito**](https://www.thermaoasi.com/_api/mcp)
- [**Documenti MCP di Wix**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)

## Strumenti MCP disponvili

### GetBusinessDetails
Recupera i dettagli dell'attività e del sito come fuso orario, email, telefono e indirizzo.
- Nessun parametro richiesto.

### SearchInSite
Cerca informazioni sul sito.
- **searchTerm** - Il termine da cercare nel sito.

### SearchSiteApiDocs
Recupera la documentazione API per le soluzioni aziendali Wix installate su
questo sito, e informa il client AI su come utilizzare le API. Usa questo strumento per
intercettazione di prodotti e servizi (invece di SearchInSite).
- **searchTerm** - Il termine da cercare nella documentazione API del sito.

### GenerateVisitorToken
Crea una nuova sessione visitatore e ottiene un token di accesso visitatore per il sito.
Deve essere richiamato prima di effettuare qualsiasi richiesta CallWixSiteAPI se non c'è un token visitatore
è già disponibile nel contesto.
- Nessun parametro richiesto.

### CallWixSiteAPI
Chiama metodi API sul sito per eseguire azioni per conto di un visitatore, 
Ad esempio, consultare i dati del sito, fissare un appuntamento o avviare un acquisto.
- **visitorToken** - Token di accesso del visitatore. Usa prima GenerateVisitorToken se non è disponibile.
- \'url\' - URL assoluto del metodo API da chiamare (ad esempio https://www.wixapis.com/...). Recupera usando SearchSiteApiDocs.
- **method** - Metodo HTTP da usare per la chiamata API.
- **body** - Corpo della richiesta come stringa JSON valida.

### ReadFullDocsArticle
Recupera un articolo completo dal portale di documentazione per sviluppatori Wix.
- **articleUrl** -  URL di un articolo nel portale di documentazione per sviluppatori Wix.

### ReadFullDocsMethodSchema
Recupera lo schema completo per un metodo Wix API. Deve essere richiamato prima
chiamando il metodo effettivo tramite CallWixSiteAPI.
- \'articleUrl\' - URL dell'articolo di riferimento per il metodo Wix API.

## Cosa possono fare i visitatori tramite AI + MCP

- Ottenere i dati aziendali (informazioni di contatto, posizione, orari)
- Scoprire prodotti e servizi offerti
- Prenotare i servizi e effettuare prenotazioni
- Avviare un acquisto e essere indirizzati al sito per completare il checkout
- Fare domande e ottenere risposte rilevanti senza dover navigare sul sito

## Note

- Nessuna autenticazione necessaria per connettersi all'endpoint MCP
- Sono disponibili solo informazioni pubbliche accessibili sul sito
- I contenuti sono sempre in tempo reale e aggiornati
- Per ricevere aggiornamenti degli strumenti, implementare una chiamata di strumenti/lista al ricevimento di una notifica di aggiornamento degli strumenti
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://thermaoasi.com/.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 thermaoasi.com badge for https://ucpchecker.com/score/thermaoasi.comLive preview
Markdown
[![UCP Score for thermaoasi.com](https://ucpchecker.com/score/thermaoasi.com/badge.svg)](https://ucpchecker.com/score/thermaoasi.com)
HTML
<a href="https://ucpchecker.com/score/thermaoasi.com"><img src="https://ucpchecker.com/score/thermaoasi.com/badge.svg" alt="UCP Score for thermaoasi.com"></a>
New · Early access open
Is thermaoasi.com 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 thermaoasi.com'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.