UCP Checker
Back to status
tierheim-eupen.be icon
UCP Score

UCP Score for tierheim-eupen.be

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

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

tierheim-eupen.be 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

tierheim-eupen.be publishes a valid UCP profile, with minor schema warnings.

Latency
346ms
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,459 Wixes we monitor.

fastWix median 410msslow
Your store
346ms
Wix percentile
Top quartile
Faster than 86% 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

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 KB0b1f4ee73f3e3352
# Tierheim Eupen
> Das Tierheim Eupen bietet Tieren in Not ein sicheres Zuhause und setzt sich für deren Versorgung, medizinische Betreuung und Vermittlung ein. Die Website informiert über den Adoptionsablauf für Hunde und Katzen, die Notwendigkeit einer Haltegenehmigung für Haustiere in der Wallonie und bietet verschiedene Möglichkeiten zur Unterstützung, wie Spenden, Patenschaften oder ehrenamtliches Engagement. Darüber hinaus werden Ausbildungs- und Praktikumsmöglichkeiten im Tierheim vorgestellt, um jungen Menschen praktische Erfahrungen in der Tierpflege zu ermöglichen.

## Homepage link
- [home](https://www.tierheim-eupen.be/)

## 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.tierheim-eupen.be/_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
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://tierheim-eupen.be/.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 tierheim-eupen.be badge for https://ucpchecker.com/score/tierheim-eupen.beLive preview
Markdown
[![UCP Score for tierheim-eupen.be](https://ucpchecker.com/score/tierheim-eupen.be/badge.svg)](https://ucpchecker.com/score/tierheim-eupen.be)
HTML
<a href="https://ucpchecker.com/score/tierheim-eupen.be"><img src="https://ucpchecker.com/score/tierheim-eupen.be/badge.svg" alt="UCP Score for tierheim-eupen.be"></a>
New · Early access open
Is tierheim-eupen.be 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 tierheim-eupen.be'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.