UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
sexshopadultsstoreelsalvador.com 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 → Publish Organization schema (JSON-LD) on the homepage
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.
No Organization-typed JSON-LD detected on your homepage.
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": { ... }
}No Organization-typed JSON-LD detected on your homepage.
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.
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>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 itEvery 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.
Found 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.
Missing or incomplete on homepage
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/582b8dbd-1057-479d-bff5-e9e6a3db680e.
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/582b8dbd-1057-479d-bff5-e9e6a3db680e/mcp.
tools/list returned a JSON-RPC response in 172ms
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.
# Adults Store SV
> Este sitio web te invita a conocer su historia y lo que ofrece. Se anima a los usuarios a compartir detalles personales y profesionales para conectar con los visitantes. El sitio también proporciona información de contacto, horarios de atención al cliente, dirección física y detalles sobre ofertas y ubicación, animando a los usuarios a explorar sus más de 700 alternativas.
## Homepage link
- [home](https://www.sexshopadultsstoreelsalvador.com/)
## 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://www.sexshopadultsstoreelsalvador.com/_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| 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://sexshopadultsstoreelsalvador.com/.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/sexshopadultsstoreelsalvador.com)<a href="https://ucpchecker.com/score/sexshopadultsstoreelsalvador.com"><img src="https://ucpchecker.com/score/sexshopadultsstoreelsalvador.com/badge.svg" alt="UCP Score for sexshopadultsstoreelsalvador.com"></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 sexshopadultsstoreelsalvador.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.
Track domains and get emailed when their UCP status changes.
By continuing you agree to our Terms & Privacy Policy.