Facet UCP Shopping
REMOTE · API.FACET.LLC · SCANNED AUG 3
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 →
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 9 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 not yet verified: we couldn't determine whether a plaintext access path exists. 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 Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1093 tokens (~121/item across 9 items; 9 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.facet.llc
claude mcp add --transport http llc-facet-ucp-shopping 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 58
First indexed and scored.
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 3 Aug 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 | 4 Jul 2026 | 2 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 15c137083d94f2970ee8981523b67db8 |
| 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 |
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=() |
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 | 404 |
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.
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.
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.
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.