UCP Checker
Sign in Start monitoring
Back to status
gerstore2.mitiendanube.com icon
UCP Score

UCP Score for gerstore2.mitiendanube.com

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

✓Verified
A95/100
Analyzed Sep 15, 2026 · 2 recommendations ·Custom · v2026-08-25 latest
95
/ 100
UCP Conformance Score
A

gerstore2.mitiendanube.com is conforming and ready for agent discovery and checkout.

Agent Discovery100
UCP Conformance93
Capability Coverage92
Biggest blockers
Publish keys at the manifest rootRepair declared transport endpoints
Working

Agent Discovery is solid (100/100).

Blocking

Publish keys at the manifest root — Agents have nothing to verify your responses against.

Start Here

Publish keys at the manifest root → Repair declared transport endpoints

Verified

gerstore2.mitiendanube.com is agent-ready but has minor schema warnings.

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

Top Priorities

1
Publish keys at the manifest root

Agents have nothing to verify your responses against.

High impact Medium effort
2
Repair declared transport endpoints

One or more declared transport endpoints did not respond when probed.

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

High impact, high effort

  • Publish keys at the manifest root
  • Repair declared transport endpoints
Incremental Gains(0)

Medium impact & effort

  • No items
Consider Later(0)

Lower priority

  • No items

How you compare on Custom

Response time benchmarked against 127 Customs we monitor.

fastCustom median 372msslow
Your store
559ms
Custom percentile
Below median
Faster than 33% of Custom stores
Cohort range
234–636ms
p25 to p75 (middle half)
Headless / custom stackCustom-built storefronts have the most flexibility but also the most surface area for inconsistency between environments. Run the score in staging before each deploy that touches manifest, schemas, or transports.

Recommendations

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

1

Publish keys at the manifest root

High impact Medium effort

Agents have nothing to verify your responses against.

Why it matters

Signing keys let agents cryptographically verify checkout responses came from you, not a man-in-the-middle. Tokenized payment flows in v2026-04-08+ require them. Since 2026-07-12 the spec's canonical field is a root-level RFC 7517 "keys" array (the legacy "signing_keys" field was removed from the profile schema; we accept both during the migration). Stores using checkout-link redirects (e.g. WooCommerce) often skip this safely.

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
2

Repair declared transport endpoints

High impact Medium effort

One or more declared transport endpoints did not respond when probed.

Why it matters

A manifest that declares transports without working endpoints is the worst kind of broken — it looks perfect to static validators but agents hit a dead end the moment they try to use the capability. Connection refused, DNS failure, TLS errors, and 5xx responses all fall here. See the Full Check Breakdown below for the specific endpoints that failed.

UCP_PROBE_TRANSPORT_FAILED

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

  • Spec 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.

  • Validation warnings clearCore

    Manifest passes structural and field-level rules.

    No outstanding validation issues

    Why it matters

    Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.

  • Spec & schema URLs resolve (16)Core

    Resolves the 16 spec/schema URLs declared across the manifest to confirm agents can fetch each one.

    All 16 URLs resolved.

    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 Coverage5/6 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

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

    1 handler registered

    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://ucp.tiendanube.com/stores/5111033.

    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://ucp.tiendanube.com/stores/5111033/mcp.

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

    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.

2.3 KB2d2d8dca10bd35b6
mentions UCP
# Agent Instructions — Ger Store

This document describes how AI agents can interact with Ger Store's online store at https://gerstore2.mitiendanube.com.

## Commerce Protocol (UCP)

This store implements the [Universal Commerce Protocol](https://ucp.dev) for agent-driven commerce.

### Discovery

```
GET https://gerstore2.mitiendanube.com/.well-known/ucp
```

Returns the store's UCP merchant profile: supported versions, service endpoints, capabilities, and payment handlers.

### MCP Endpoint

```
POST https://gerstore2.mitiendanube.com/api/ucp/mcp
Content-Type: application/json
```

Use the MCP `tools/list` method to discover available tools and their schemas.

### Typical Agent Flow

1. **Discover** — `GET /.well-known/ucp` to confirm capabilities
2. **Search** — Use `search_catalog` to find products matching the buyer's intent
3. **Cart** — Use `create_cart` to add desired items
4. **Checkout** — Use `create_checkout` to start the purchase flow
5. **Fulfill** — Use `update_checkout` to set shipping address and method
6. **Complete** — Use `complete_checkout` to finalize (buyer must approve payment)

### Supported UCP Versions
- `2026-04-08` (latest stable)
- `2026-01-23`

### Important Rules

- **Checkout requires human approval.** Agents must not complete payment without explicit buyer consent.
- **Respect rate limits.** The MCP endpoint is rate-limited per IP. Back off on 429 responses.
- **Use buyer context.** Pass `context.address_country` and `context.currency` for accurate pricing and availability.


## Read-Only Browsing (No Authentication Required)

For agents that only need to read store data without transacting:

### Product Data
- Browse all products: `GET /productos`
- Product page: `GET /productos/{handle}`
- Category page: `GET /{handle}`
- Search: `GET /search?q={query}`

### Store Metadata
- Sitemap: `GET /sitemap.xml`
- Agent discovery: this document (`/agents.md`) is the canonical agent-facing description of the store.

## Contact
- Contact: 
- Phone: 

## Platform

This store is built on [Tiendanube](https://www.tiendanube.com), the leading commerce platform powering hundreds of thousands of stores in LATAM. Tiendanube stores support UCP natively, enabling seamless agent-driven commerce.
- Start your own store: https://www.tiendanube.com
- UCP specification: https://ucp.dev
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Cart ✓ Bound 2026-08-25
Order Management ✓ 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://gerstore2.mitiendanube.com/.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 gerstore2.mitiendanube.com badge for https://ucpchecker.com/score/gerstore2.mitiendanube.comLive preview
Markdown
[![UCP Score for gerstore2.mitiendanube.com](https://ucpchecker.com/score/gerstore2.mitiendanube.com/badge.svg)](https://ucpchecker.com/score/gerstore2.mitiendanube.com)
HTML
<a href="https://ucpchecker.com/score/gerstore2.mitiendanube.com"><img src="https://ucpchecker.com/score/gerstore2.mitiendanube.com/badge.svg" alt="UCP Score for gerstore2.mitiendanube.com"></a>
New · Early access open
Is gerstore2.mitiendanube.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 gerstore2.mitiendanube.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.