UCP Checker
Back to status
invitrocare.com.tr icon
UCP Score

UCP Score for invitrocare.com.tr

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

✓Verified
A86/100
Analyzed Sep 26, 2026 · 3 recommendations ·Wix · v2026-08-25 latest
86
/ 100
UCP Conformance Score
A

invitrocare.com.tr publishes a conforming manifest 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 keys at the manifest root → Publish a schema URL for the service

Verified

invitrocare.com.tr publishes a valid UCP manifest, with minor schema warnings.

Latency
428ms
Version
2026-08-25
Robots.txt
Allowed ✅

Top Priorities

1
Fix broken spec or schema URLs

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

Medium impact Low effort
2
Publish keys at the manifest root

Agents have nothing to verify your responses against.

Medium impact Medium effort
3
Publish a schema URL for the service

Service is missing its "schema" URL.

Low impact Medium 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 keys at the manifest root
Consider Later(1)

Lower priority

  • Publish a schema URL for the service

How you compare on Wix

Response time benchmarked against 7,233 Wixes we monitor.

fastWix median 442msslow
Your store
428ms
Wix percentile
Above median
Faster than 58% of Wix stores
Cohort range
400–508ms
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 manifest 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 manifest setup. See the Full Check Breakdown for the specific URLs that failed.

UCP_PROBE_URL_BROKEN
2

Publish keys at the manifest root

Medium impact Medium effort

Agents have nothing to verify your responses against.

Why it matters

Signing keys let agents check that checkout responses really came from you. Tokenized payment flows in v2026-04-08+ require them. Since 2026-07-12 the spec expects a root-level "keys" list (the older "signing_keys" field is still accepted while stores move). Stores that hand the buyer a checkout link instead of taking payment through the agent can go without them for now.

Show fix

Generate an Ed25519 keypair, publish the public key as a JWK in a root-level "keys" array (the canonical field since spec PR #566; "signing_keys" is legacy). Rotate annually; keep "kid" stable across rotations of the same key.

{
  "keys": [
    {
      "kty": "OKP",
      "crv": "Ed25519",
      "x": "<base64url-encoded-public-key>",
      "kid": "key-2026-04",
      "alg": "EdDSA"
    }
  ],
  "ucp": { ... }
}
UCP_MISSING_SIGNING_KEYS
3

Publish a schema URL for the service

Low impact Medium effort

Service is missing its "schema" URL.

Why it matters

The schema lets agents validate request/response shapes before sending. Highly recommended for any non-trivial endpoint.

Show fix
"schema": "https://yourstore.com/.well-known/ucp/schemas/shopping.json"
UCP_SERVICE_MISSING_SCHEMA

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 manifest?

  • HTTPSCore

    Manifest served over a secure connection.

    Manifest 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 manifest reachableCore

    Manifest 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 manifest.

    robots.txt allows /.well-known/ucp

    Why it matters

    Agents respect robots.txt. Even a published manifest 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 manifest 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 manifest meet the published spec?

  • Manifest passes schema validationCore

    Manifest structure conforms to the published UCP spec.

    No structural errors

    Why it matters

    Strict UCP agents reject manifests 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-08-25

    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

    Manifest passes structural and field-level rules.

    2 warnings

    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 manifest 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 capabilities detected

    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/62db5404-8a93-4ca3-a1ab-d9cb5497ea3a.

    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 manifest itself looks perfect.

  • MCP transport reachableInterop

    Live reachability check against https://www.wixapis.com/ecom/ucp/62db5404-8a93-4ca3-a1ab-d9cb5497ea3a/mcp.

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

    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 manifest itself looks perfect.

/llms.txt content

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

4.0 KBe70d3b9add09ed1d
# Invitrocare
> İnvitrocare, İstanbul genelinde evde sağlık ve bakım hizmetleri sunmaktadır. Kolajen IV terapi, evde görüntüleme, evde IV terapi, evde EKG, evde kan alma, evde Holter, evde hasta bakıcı, evde pansuman, evde ultrason, evde röntgen, evde banyo, evde üroloji doktoru, evde hemşirelik, glutatyon IV terapi, evde yara bakımı, NAD IV terapi, evde tıbbi işlem, evde EKO, evde kulak yıkama, evde hastane refakati, evde lavman, evde nörolojik muayene, evde göğüs hastalıkları doktoru, evde nörolojik rehabilitasyon, evde ortopedik rehabilitasyon, evde geriatrik rehabilitasyon, evde KBB doktoru, evde dahiliye doktoru, evde dermatoloji doktoru, evde kardiyoloji doktoru, evde bakım doktoru, evde uyku testi, evde NG değişimi, evde trakeostomi bakımı, evde idrar sonda değişimi, evde EEG-EMG testi, evde Doppler ultrason, evde serum hizmeti, multivitamin IV terapi ve evde fizik tedavi gibi geniş bir hizmet yelpazesi sunmaktadır. Tüm bu hizmetler, hastaların konforunu ve güvenliğini ön planda tutarak ev ortamında profesyonelce sunulmaktadır.

## Homepage link
- [home](https://invitrocare.com.tr/)

## Yapay Zeka Temsilcisi Erişimi

Bu site, Wix altyapısıyla güçlendirilmiştir ve temsilci tabanlı yapay zeka erişimi için Model Bağlam Protokolü'nü (MCP) destekler. AI temsilcileri direkt olarak bağlanarak canlı, güncel site içeriğini alabilirler; veri kazıma gerekmez.

- [**Site MCP Uç Noktası**](https://invitrocare.com.tr/_api/mcp)
- [**Wix MCP Dokümanları**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)

## Mevcut MCP Araçları

### GetBusinessDetails
Saat dilimi, e-posta, telefon ve adres gibi işletme ve site bilgilerini alır.
- Parametre gerekmez.

### SearchInSite
Sitede bilgi arar.
- **searchTerm** - Sitede aranacak terim.

### SearchSiteApiDocs
Bu siteye yüklenen Wix işletme çözümlerinin API belgelerini alır ve yapay zeka istemcisini API'ları nasıl kullanacağı konusunda bilgilendirir. Ürünleri ve hizmetleri sorgulamak için bu aracı kullanın (SearchInSite yerine).
- **searchTerm** - Site API belgelerinde aranacak terim.

### GenerateVisitorToken
Yeni bir ziyaretçi oturumu oluşturur ve site için bir ziyaretçi erişim belirteci alır.
Bağlamda zaten bir ziyaretçi belirteci mevcut değilse herhangi bir CallWixSiteAPI isteği yapmadan önce çağrılmalıdır.
- Parametre gerekmez.

### CallWixSiteAPI
Bir ziyaretçi adına site verilerini sorgulama, randevu alma veya bir satın alma işlemi başlatma gibi eylemleri gerçekleştirmek için sitedeki API metotlarını çağırır.
- **visitorToken** - Ziyaretçi erişim belirteci. Mevcut değilse önce GenerateVisitorToken kullanın.
- **url** - Çağrılacak API metotunun mutlak URL'si (Ör. https://www.wixapis.com/...). SearchSiteApiDocs kullanarak alın.
- **method** - API çağrısı için kullanılacak HTTP metodu.
- **body** - Geçerli bir JSON dizesi olarak istek gövdesi.

### ReadFullDocsArticle
Wix geliştirici dokümantasyon portalından makalenin tamamını getirir.
- **articleUrl** - Wix geliştirici dokümantasyon portalındaki bir makalenin URL'si.

### ReadFullDocsMethodSchema
Bir Wix API metodunun tam şemasını getirir. CallWixSiteAPI aracılığıyla asıl metodu çağırmadan önce çağrılmalıdır.
- **articleUrl** - Wix API metodu için referans makalenin URL'si.

## Ziyaretçiler Yapay Zeka + MCP Aracılığıyla Ne Yapabilir

- İşletme bilgilerini (iletişim bilgileri, konum, çalışma saatleri) alma
- Sunulan ürün ve hizmetleri keşfetme
- Hizmet randevusu alma ve rezervasyon yapma
- Bir satın alma işlemi başlatma ve ödemeyi tamamlamak için siteye yönlendirilme
- Sorular sorma ve siteyi taramak zorunda kalmadan ilgili yanıtları alma

## Notlar

- MCP uç noktasına bağlanmak için kimlik doğrulama gerekmez
- Yalnızca sitede erişilebilir olan herkese açık bilgiler kullanılabilir
- İçerik her zaman canlı ve günceldir
- Araç güncellemelerini almak için, bir araç güncelleme bildirimi alınca bir tools/list çağrısı uygulayın
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Cart ✓ Bound 2026-08-25
Checkout ✓ Bound 2026-08-25
Fulfillment Extension ✓ Bound 2026-08-25
Catalog Lookup ✓ Bound 2026-08-25
Catalog Search ✓ Bound 2026-08-25

Technical Vitals

Technical details for this UCP endpoint
UCP Status Verified
Endpoint https://invitrocare.com.tr/.well-known/ucp
HTTP Status 200
UCP Version 2026-08-25
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 invitrocare.com.tr badge for https://ucpchecker.com/score/invitrocare.com.trLive preview
Markdown
[![UCP Score for invitrocare.com.tr](https://ucpchecker.com/score/invitrocare.com.tr/badge.svg)](https://ucpchecker.com/score/invitrocare.com.tr)
HTML
<a href="https://ucpchecker.com/score/invitrocare.com.tr"><img src="https://ucpchecker.com/score/invitrocare.com.tr/badge.svg" alt="UCP Score for invitrocare.com.tr"></a>
New · Early access open
Is invitrocare.com.tr 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 invitrocare.com.tr'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.