Facet UCP Shopping
REMOTE · API.FACET.LLC · SCANNED SEP 26
The independent agent-commerce protocol for AI-agent checkout on any online store.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 23 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2824 tokens (~122/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "post_delivery_refund" implies "refund" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Facet UCP Shopping MCP server?
Facet UCP Shopping is a hosted endpoint at https://api.facet.llc/ucp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.facet.llc
claude mcp add --transport http llc-facet-ucp-shopping 'https://api.facet.llc/ucp/mcp'
{
"mcpServers": {
"llc-facet-ucp-shopping": {
"url": "https://api.facet.llc/ucp/mcp"
}
}
} {
"servers": {
"llc-facet-ucp-shopping": {
"type": "http",
"url": "https://api.facet.llc/ucp/mcp"
}
}
} [mcp_servers.llc-facet-ucp-shopping] url = "https://api.facet.llc/ucp/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"llc-facet-ucp-shopping": {
"type": "remote",
"url": "https://api.facet.llc/ucp/mcp",
"enabled": true
}
}
} openclaw mcp add llc-facet-ucp-shopping --url 'https://api.facet.llc/ucp/mcp' --transport streamable-http
mcp_servers:
llc-facet-ucp-shopping:
url: "https://api.facet.llc/ucp/mcp" {
"McpServers": {
"llc-facet-ucp-shopping": {
"Transport": "http",
"Url": "https://api.facet.llc/ucp/mcp"
}
}
} assistant mcp add llc-facet-ucp-shopping -t streamable-http -u 'https://api.facet.llc/ucp/mcp'
{
"mcpServers": {
"llc-facet-ucp-shopping": {
"type": "http",
"url": "https://api.facet.llc/ucp/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Aug 26 0
- Server version: 2026-04-08 → 2026-08-25 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 17 Aug 26 0
- Schema quality: 1093 → 2481 ▼ functional
- Tool coverage: 85% → 93% ▲ functional
- New tool “cancel_cart” functional
- New tool “cancel_checkout” functional
- New tool “complete_checkout” functional
- New tool “create_cart” functional
- New tool “create_checkout” functional
- New tool “discover_products” functional
- New tool “get_cart” functional
- New tool “get_checkout” functional
- New tool “update_cart” functional
- New tool “update_checkout” functional
- New tool “wishlist_add” functional
- New tool “wishlist_list” functional
- New tool “wishlist_remove” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Aug 26 0
- Server version: 2026-06-22 → 2026-04-08 functional
- 6 Aug 26 0
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://api.facet.llc/ucp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=facet.llc | CN=WE1,O=Google Trust Services,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | e90c57a8374bffc90eeda8ef4bda7c43 |
| SANs: facet.llc, *.facet.llc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.facet.llc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| llc. | present | 25591 | 8 | Verified |
| facet.llc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.facet.llc/ucp/mcp | Verified | 200 | |
| http (plaintext) | http://api.facet.llc/ucp/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_cart ~52
Cancel a cart. Idempotent, owner-scoped, and moves no money. REQUIRES IDENTITY plus an Idempotency-Key on a signature-required Terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The cart id. |
No output schema declared.
No examples provided.
cancel_checkout ~67
Cancel a checkout session before completion, releasing its inventory hold. Idempotent, owner-scoped, and moves no money (distinct from an escrow refund). REQUIRES IDENTITY plus an Idempotency-Key on a signature-required Terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The checkout session id. |
No output schema declared.
No examples provided.
complete_checkout ~213
Complete a checkout you created and place the order by submitting the buyer-signed payment credential. This is the MONEY-MOVING leg: funds capture on-chain to the merchant's pay_to (x402) or into escrow (Boson). The amount is re-derived server-side from the reservation, never your request, and the buyer's signature is verified before any capture. A per-buyer refusal (FORBIDDEN, cap-exceeded, FULFILLMENT_REQUIRED) returns as an error result; a missing or invalid identity is a real 401. REQUIRES IDENTITY plus a signed Idempotency-Key on a signature-required Terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | The checkout id from create_checkout. |
| payment | object | yes | The payment container `{ instruments: [{ credential: { type, ... } }] }`, where credential.type is `x402_authorization` or `boson_commit_authorization`. Sign the seller-signed offer LOCALLY with your… |
No output schema declared.
No examples provided.
create_cart ~100
Create a pre-checkout cart from catalog line items. A cart is a mutable scratchpad: it moves no money and holds no inventory, so it carries estimated (server-derived) totals and NO payment_handlers. Assemble it, then create_checkout(cart_id) to convert. REQUIRES IDENTITY on a signature-required Terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| line_items | array | – | Items, each `{ item: { id }, quantity }`. Prices are catalog-derived, never yours. |
No output schema declared.
No examples provided.
create_checkout ~202
Open a checkout session for one or more catalog line items (or promote a cart with `cart_id`). Returns the session plus server-resolved `payment_handlers` (rail, pay_to, exact amount) to satisfy: the price and pay_to are the MERCHANT's, sealed here, never read from your request. Physical goods REQUIRE a `fulfillment` ship-to (else FULFILLMENT_REQUIRED), sealed at create. REQUIRES IDENTITY on a signature-required Terminal: a Facet KYA as `Authorization: Bearer <kya>`.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | – | Promote an existing cart: its stored lines drive the checkout and any line_items are ignored (the business must use the cart contents). |
| fulfillment | object | – | Ship-to destination. REQUIRED for physical products; sealed at create. |
| line_items | array | – | Items to buy, each `{ item: { id }, quantity }`. Omit when using cart_id. |
No output schema declared.
No examples provided.
discover_businesses ~229
Find businesses in the Facet Universal Business Index that an agent can transact with. Returns `featured` (claimed merchants with a live `terminal_url` — point your catalog and checkout calls there) and `results` (the wider directory). Use this first when you do not already know which merchant to talk to. REQUIRES IDENTITY: send a Facet KYA as `Authorization: Bearer <kya>` on the MCP request. A KYA is an ES256 JWT from Facet's default issuer https://issuer.facet.llc (or another issuer this Terminal trusts — see KYA-Issuers in its /.well-known/agents.txt). Calling without one returns 401 with a signup link.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max matches to return. Default 10, cap 50. |
| near | object | – | Optional geographic center to rank by proximity. |
| query | string | – | Free-text query, e.g. "flowers" or "makeup brushes". |
| radius_km | number | – | Search radius around `near`, km. Default 25. |
No output schema declared.
No examples provided.
discover_products ~251
Search products ACROSS every merchant in the Facet network that has opted into cross-merchant discovery. Returns matches each carrying the selling merchant's `terminal_url` (point your catalog and checkout calls there). Filter by free-text `query` (product name + description), exact `category`, and/or `tags` (all must be present); at least one filter is required. Use this when you know WHAT you want but not WHICH merchant sells it. REQUIRES IDENTITY: send a Facet KYA as `Authorization: Bearer <kya>` on the MCP request. A KYA is an ES256 JWT from Facet's default issuer https://issuer.facet.llc (or another issuer this Terminal trusts; see KYA-Issuers in its /.well-known/agents.txt). Calling without one returns 401 with a signup link.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Exact product category to match. |
| limit | integer | – | Max matches to return. Default 10, cap 50. |
| query | string | – | Free-text over product name + description, e.g. "lavender soap". |
| tags | array | – | Tags that must ALL be present on a matching product. |
No output schema declared.
No examples provided.
get_cart ~57
Read back one of YOUR carts by id: line items and estimated totals. Owner-scoped, so another agent's id returns not_found. REQUIRES IDENTITY on a signature-required Terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The cart id. |
No output schema declared.
No examples provided.
get_checkout ~63
Read back one of YOUR checkout sessions by id: status, totals, line items, payment_handlers. Owner-scoped, so another agent's id returns not_found. REQUIRES IDENTITY on a signature-required Terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The checkout session id. |
No output schema declared.
No examples provided.
get_order ~89
Read back one of YOUR orders on this merchant: status, amount, settlement state. Use the order_id returned when you paid. You can only read orders your own agent identity placed — another agent's order returns FORBIDDEN. REQUIRES IDENTITY: Facet KYA as `Authorization: Bearer <kya>`.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id returned at payment. |
No output schema declared.
No examples provided.
get_payment_capabilities ~74
Which settlement rails this merchant actually accepts (e.g. coin/boson-escrow for escrowed funds that release on fulfilment, coin/usdc-base for direct). Call before get_payment_requirements so you pass a rail_id this merchant registers, rather than guessing. No identity required — this is discovery data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_payment_requirements ~316
Turn a `quote_token` from get_quote into a seller-signed payment offer to authorize. Returns `requirements` (escrow address, asset, exact atomic amount, network) — sign it LOCALLY with your own wallet (e.g. @bosonprotocol/x402-client handle402 for `coin/boson-escrow`, producing an X-PAYMENT string). Facet never holds your key and cannot sign for you, which is why paying is two steps and not one. The offer binds to the quote_token's sealed landed total and ship-to, so the amount is the merchant's, not one you name. REQUIRES IDENTITY: same Facet KYA as get_quote, and the SAME `aid` — the offer path rejects a quote_token issued to a different agent than the caller.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | object | yes | The landed total in ATOMIC units. Must equal the quote_token's sealed total. |
| product_id | string | yes | Must match the product the quote_token sealed. |
| qty | integer | – | Must match the quote_token. Default 1. |
| quote_token | string | yes | The signed token from get_quote. |
| rail_id | string | yes | Settlement rail, e.g. "coin/boson-escrow" (escrow: funds release on fulfilment) or "coin/usdc-base". See /v1/payments/capabilities for what this merchant registers. |
| site_id | string | – | Usually omitted — this Terminal's bound site is used. |
No output schema declared.
No examples provided.
get_product ~25
Get full product detail by product or variant identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | object | yes | – |
No output schema declared.
No examples provided.
get_quote ~225
Get the real landed cost of a product from this merchant: goods + shipping + tax for a specific destination, plus a signed `quote_token` the payment path binds to. Call this before paying — the token is what makes the price the MERCHANT's, not one you name. Physical products REQUIRE a `fulfillment` ship-to; without one you get FULFILLMENT_REQUIRED. An unserviceable destination returns UNDELIVERABLE (the merchant's own shipping zones, which Facet cannot waive). REQUIRES IDENTITY: send a Facet KYA as `Authorization: Bearer <kya>` (ES256 JWT from https://issuer.facet.llc, or another issuer in this Terminal's agents.txt KYA-Issuers).
| Name | Type | Req | Description |
|---|---|---|---|
| fulfillment | object | – | Ship-to destination. REQUIRED for physical products. |
| product_id | string | yes | Product or variant id, e.g. from search_catalog. |
| qty | integer | – | Quantity. Default 1. |
| site_id | string | – | Usually omitted — this Terminal's bound site is used. |
No output schema declared.
No examples provided.
list_orders ~80
List YOUR order history on this merchant, newest first. Scoped to your own agent identity — you never see another agent's orders. REQUIRES IDENTITY: Facet KYA as `Authorization: Bearer <kya>`.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from a previous page. |
| limit | integer | – | Max orders to return. |
No output schema declared.
No examples provided.
lookup_catalog ~28
Look up one or more products or variants by identifier (batch).
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | object | yes | – |
No output schema declared.
No examples provided.
post_delivery_refund ~343
Request a refund or return on a DELIVERED order you placed on this merchant. Opens a merchant-approved refund ticket (status `requested`); it moves NO money on its own. The merchant reviews and approves it, and only then does the send-back sign from the merchant's OWN wallet (non-custodial). Amount and recipient are NOT inputs: the refund amount is derived and capped server-side, and the recipient is the order's stamped payer, never one you name. Pass `refund_line_items` to refund only part of the order; omit for the whole order. Owner-scoped: another agent's order returns FORBIDDEN. REQUIRES IDENTITY: a Facet KYA as `Authorization: Bearer <kya>` (an ES256 JWT from https://issuer.facet.llc, or another issuer in this Terminal's agents.txt KYA-Issuers). A wallet-bound KYA also authorizes a platform-originated order by its stamped payer.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id returned at payment (settle / checkout complete). A reservation id is not an order id. |
| reason | string | yes | Why the refund or return is requested. Required. |
| receipt | object | – | Optional Ed25519-signed settlement receipt (the signed settle response you received). When valid and bound to this order it records receipt_verified on the ticket; it never gates the refund. |
| refund_line_items | array | – | Optional PARTIAL selection: refund only these lines instead of the whole order. Advisory at request time; the merchant is authoritative and may adjust it at decide. Omit for a full-order refund. |
No output schema declared.
No examples provided.
search_catalog ~27
Search the merchant catalog for products matching a free-text query.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | object | yes | – |
No output schema declared.
No examples provided.
update_cart ~72
Replace a cart's line items (full replacement), re-priced server-side. Owner-scoped. REQUIRES IDENTITY on a signature-required Terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The cart id. |
| line_items | array | – | The new full set of items, each `{ item: { id }, quantity }`. |
No output schema declared.
No examples provided.
update_checkout ~73
Return a checkout's CURRENT sealed snapshot. Facet seals price and items at create, so this is a no-op that reports the session plus a note: to change line items, update the cart and start a new checkout with create_checkout(cart_id). Owner-scoped.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The checkout session id. |
No output schema declared.
No examples provided.
wishlist_add ~94
Save a product to YOUR wishlist on this merchant for later. Idempotent: saving the same product again updates its note and keeps the original save time. Scoped to your own agent identity. REQUIRES IDENTITY: Facet KYA as `Authorization: Bearer <kya>`.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional short note. No personal data. |
| product_id | string | yes | The product id to save. |
No output schema declared.
No examples provided.
wishlist_list ~70
List YOUR saved items (wishlist) on this merchant, newest first. Scoped to your own agent identity, so you never see another agent's list. REQUIRES IDENTITY: Facet KYA as `Authorization: Bearer <kya>`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return. |
No output schema declared.
No examples provided.
wishlist_remove ~74
Remove a product from YOUR wishlist on this merchant. Idempotent: removing something not on your list succeeds with removed:false. Scoped to your own agent identity. REQUIRES IDENTITY: Facet KYA as `Authorization: Bearer <kya>`.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | The product id to remove. |
No output schema declared.
No examples provided.
What is the Facet UCP Shopping MCP server?
Facet UCP Shopping is an MCP server listed in the public MCP registry as llc.facet/ucp-shopping. The independent agent-commerce protocol for AI-agent checkout on any online store. This page covers its hosted endpoint (https://api.facet.llc/ucp/mcp).
Is the Facet UCP Shopping MCP server safe to use?
Facet UCP Shopping scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Facet UCP Shopping MCP server expose?
Facet UCP Shopping exposes 23 tools: search_catalog, lookup_catalog, get_product, discover_businesses, discover_products, and 18 more. Their descriptions and schemas cost roughly 2,824 tokens of context every time the server is loaded.
Does the Facet UCP Shopping MCP server require authentication?
No. We connected to Facet UCP Shopping without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Facet UCP Shopping MCP server still maintained?
Facet UCP Shopping is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.