UCP Checker
Back to status
lalcec.org.ar icon
UCP Score

UCP Score for lalcec.org.ar

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

✓Verified
A88/100
Analyzed Oct 9, 2026 · 3 recommendations ·Wix · v2026-04-08 upgrade
88
/ 100
UCP Score
A

lalcec.org.ar publishes a conforming profile with broad capability coverage.

Agent Discovery95
UCP Conformance88
Capability Coverage81
Working

Agent Discovery is solid (95/100).

Start Here

Publish the public keys agents use to check your messages → Publish Organization schema (JSON-LD) on the homepage → Move to the latest UCP protocol version

Verified

lalcec.org.ar publishes a valid UCP profile, with minor schema warnings.

Latency
359ms
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
Publish Organization schema (JSON-LD) on the homepage

No Organization-typed JSON-LD detected on your homepage.

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

  • Publish the public keys agents use to check your messages
  • Publish Organization schema (JSON-LD) on the homepage
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
359ms
Wix percentile
Top quartile
Faster than 79% of Wix stores
Cohort range
365–479ms
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

Publish Organization schema (JSON-LD) on the homepage

Medium impact Medium effort

No Organization-typed JSON-LD detected on your homepage.

Why it matters

Organization schema gives agents a structured representation of your brand identity: name, logo, social profiles, contact info, founding date. Agents use this to verify you are who you claim to be and to link your profile data to a recognizable entity.

Show fix

Drop into <head> or end of <body>. Use OnlineStore (more specific) when the entire site is an ecommerce store; Organization is the generic fallback.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "name": "Yourstore",
  "url": "https://yourstore.com",
  "logo": "https://yourstore.com/logo.png",
  "sameAs": [
    "https://twitter.com/yourstore",
    "https://www.instagram.com/yourstore"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-800-000-0000",
    "contactType": "Customer Service"
  }
}
</script>
UCP_MISSING_ORG_SCHEMA
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.

Agent Discovery7/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.

    Missing or incomplete on homepage

    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 KB66ea1e7062dc1c93
# LALCEC
> La Liga Argentina de Lucha Contra el Cáncer (LALCEC) es una organización dedicada a reducir la incidencia y mortalidad del cáncer en Argentina. A través de su Centro Médico y campañas a nivel nacional, LALCEC promueve la prevención, la detección temprana y el acompañamiento integral a pacientes oncológicos y sus familias. La organización ofrece estudios gratuitos para personas sin cobertura médica y brinda apoyo emocional y orientación social, trabajando para que nadie se quede atrás en la lucha contra el cáncer.

## Homepage link
- [home](https://lalcec.org.ar/)

## Acceso de agentes de IA

Este sitio está desarrollado por Wix y es compatible con el
protocolo de contexto de modelo (MCP) para el acceso de IA basada en agentes.
Los agentes de IA pueden conectarse directamente y obtener contenido del sitio
en tiempo real y actualizado, sin necesidad de scraping.

- [**Punto de conexión MCP del sitio**](https://lalcec.org.ar/_api/mcp)
- [**Documentación del MCP de Wix**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)

## Herramientas MCP disponibles

### GetBusinessDetails
Recupera información del negocio y del sitio, como zona horaria, email, teléfono y dirección.
No se requieren parámetros.

### SearchInSite
Busca información en el sitio.
- **searchTerm**: El término a buscar en el sitio.

### SearchSiteApiDocs
Recupera la documentación de API para las soluciones de negocios de Wix instaladas en
este sitio e informa al cliente de IA cómo usar las API. Usa esta herramienta para
consultar productos y servicios (en lugar de SearchInSite).
- **searchTerm**: El término a buscar en la documentación de la API del sitio.

### GenerateVisitorToken
Crea una nueva sesión de visitante y obtiene un token de acceso de visitante para el sitio.
Debe llamarse antes de realizar cualquier solicitud a CallWixSiteAPI
si no hay un token de visitante disponible en el contexto.
No se requieren parámetros.

### CallWixSiteAPI
Llama a los métodos de la API en el sitio para realizar acciones en nombre de un visitante,
 como consultar datos del sitio, reservar una cita o iniciar una compra.
- **visitorToken**: Token de acceso de visitante. Usa GenerateVisitorToken primero si no está disponible.
- **url**: URL absoluta del método de API que se va a llamar (p. ej., https://www.wixapis.com/...). Recupérala usando SearchSiteApiDocs.
- **method**: Método HTTP que se usará para la llamada a la API.
- **body**: Cuerpo de la solicitud como una cadena JSON válida.

### ReadFullDocsArticle
Recupera un artículo completo del portal de documentación para desarrolladores de Wix.
- **articleUrl**: URL de un artículo en el portal de documentación para desarrolladores de Wix.

### ReadFullDocsMethodSchema
Recupera el esquema completo para un método de API de Wix. Debe llamarse antes de usar
CallWixSiteAPI para llamar al método real.
- **articleUrl**: URL del artículo de referencia para el método de la API de Wix.

## Qué pueden hacer los visitantes con IA + MCP

- Obtener información del negocio (datos de contacto, ubicación, horarios)
- Descubrir productos y servicios en oferta
- Reservar servicios y hacer reservas
- Iniciar una compra y ser redirigidos al sitio para completar el proceso de pago
- Hacer preguntas y obtener respuestas relevantes sin tener que navegar por el sitio

## Notas

- No se requiere autenticación para conectarse al punto de conexión MCP
- Solo está disponible la información pública accesible en el sitio.
- El contenido está siempre online y actualizado.
- Para recibir actualizaciones de herramientas, implementa una llamada tools/list al recibir una notificación de actualización de herramientas
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://lalcec.org.ar/.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 lalcec.org.ar badge for https://ucpchecker.com/score/lalcec.org.arLive preview
Markdown
[![UCP Score for lalcec.org.ar](https://ucpchecker.com/score/lalcec.org.ar/badge.svg)](https://ucpchecker.com/score/lalcec.org.ar)
HTML
<a href="https://ucpchecker.com/score/lalcec.org.ar"><img src="https://ucpchecker.com/score/lalcec.org.ar/badge.svg" alt="UCP Score for lalcec.org.ar"></a>
New · Early access open
Is lalcec.org.ar 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 lalcec.org.ar'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.