UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
singon.com.np publishes a conforming profile with broad capability coverage.
Agent Discovery is solid (100/100).
Name payment handlers the way the spec does → Move to the latest UCP protocol version
A payment handler is not named in the spec's dotted form (e.g. com.google.pay).
Your profile declares a valid but older protocol version. A newer one is published.
Prioritised recommendations by expected impact and implementation effort
High impact, low effort
High impact, high effort
Medium impact & effort
Lower priority
All improvements ranked by priority, with evidence and actionable fixes.
A payment handler is not named in the spec's dotted form (e.g. com.google.pay).
Handlers are named like reversed web addresses (com.google.pay, com.stripe.terminal) so every store declaring the same payment method names it the same way, and an agent can recognise it.
"payment_handlers": {
"com.google.pay": [...]
}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.
Organization-typed JSON-LD detected
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.
signing_keys present
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 10 spec/schema URLs declared across the profile to confirm agents can fetch each one.
All 10 URLs resolved.
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.
6 capabilities detected
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.
1 handler declared, not named the way the spec expects (e.g. com.google.pay), so agents cannot look it up
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://singon.com.np/ucp/products.
Reachable in 1505ms (HTTP 200)
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://singon.com.np/api/mcp.
tools/list returned a JSON-RPC response in 1179ms
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://singon.com.np/ucp/categories.
Reachable in 1186ms (HTTP 200)
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://singon.com.np/ucp/inventory.
Reachable in 1194ms (HTTP 200)
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://singon.com.np/ucp/cart.
Reachable in 1200ms (HTTP 200)
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://singon.com.np/ucp/checkout.
Reachable in 1213ms (HTTP 200)
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://singon.com.np/ucp/orders.
Reachable in 1226ms (HTTP 200)
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://singon.com.np/ucp/customers/me.
Reachable in 1268ms (HTTP 200)
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://singon.com.np/ucp/shipping-methods.
Reachable in 1365ms (HTTP 200)
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://singon.com.np/ucp/payment/providers.
Reachable in 1138ms (HTTP 200)
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://singon.com.np/ucp/webhooks.
Reachable in 1140ms (HTTP 200)
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.
# SingOn
## Brand Brief
SingOn is an ecommerce storefront powered by Odoo and exposed through Universal Commerce Protocol APIs.
## Storefront
- Website: https://singon.com.np
- Currency: NPR
- Locale: en_US
- Timezone: Asia/Kathmandu
## Machine-Readable Endpoints
- UCP discovery: https://singon.com.np/.well-known/ucp
- MCP endpoint: https://singon.com.np/api/mcp
- Product catalog: https://singon.com.np/ucp/products
- Categories: https://singon.com.np/ucp/categories
- Inventory: https://singon.com.np/ucp/inventory
## Product Query Guidance
Use the MCP tool `ucp.search_products` or the UCP product catalog endpoint for product discovery.
Product images are returned as absolute URLs.| Cart | 2026-04-08 |
| Dev Ucp Commerce Orders | 2026-04-08 |
| Dev Ucp System Webhooks | 2026-04-08 |
| Dev Ucp Catalog Products | 2026-04-08 |
| Dev Ucp Commerce Payment | 2026-04-08 |
| Dev Ucp Catalog Inventory | 2026-04-08 |
| Checkout | 2026-04-08 |
| Dev Ucp Catalog Categories | 2026-04-08 |
| Dev Ucp Identity Customers | 2026-04-08 |
| Dev Ucp Logistics Shipping | 2026-04-08 |
| UCP Status | Verified |
| Endpoint | https://singon.com.np/.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/singon.com.np)<a href="https://ucpchecker.com/score/singon.com.np"><img src="https://ucpchecker.com/score/singon.com.np/badge.svg" alt="UCP Score for singon.com.np"></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 singon.com.np'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.