Facet UCP Shopping
Server Details
The independent agent-commerce protocol for AI-agent checkout on any online store.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
9 toolsdiscover_businessesInspect
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 | Required | Description | Default |
|---|---|---|---|
| near | No | Optional geographic center to rank by proximity. | |
| limit | No | Max matches to return. Default 10, cap 50. | |
| query | No | Free-text query, e.g. "flowers" or "makeup brushes". | |
| radius_km | No | Search radius around `near`, km. Default 25. |
get_orderInspect
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 | Required | Description | Default |
|---|---|---|---|
| order_id | Yes | The order id returned at payment. |
get_payment_capabilitiesInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_payment_requirementsInspect
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 | Required | Description | Default |
|---|---|---|---|
| qty | No | Must match the quote_token. Default 1. | |
| amount | Yes | The landed total in ATOMIC units. Must equal the quote_token's sealed total. | |
| rail_id | 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 | No | Usually omitted — this Terminal's bound site is used. | |
| product_id | Yes | Must match the product the quote_token sealed. | |
| quote_token | Yes | The signed token from get_quote. |
get_productInspect
Get full product detail by product or variant identifier.
| Name | Required | Description | Default |
|---|---|---|---|
| catalog | Yes |
get_quoteInspect
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 | Required | Description | Default |
|---|---|---|---|
| qty | No | Quantity. Default 1. | |
| site_id | No | Usually omitted — this Terminal's bound site is used. | |
| product_id | Yes | Product or variant id, e.g. from search_catalog. | |
| fulfillment | No | Ship-to destination. REQUIRED for physical products. |
list_ordersInspect
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 | Required | Description | Default |
|---|---|---|---|
| limit | No | Max orders to return. | |
| cursor | No | Opaque cursor from a previous page. |
lookup_catalogInspect
Look up one or more products or variants by identifier (batch).
| Name | Required | Description | Default |
|---|---|---|---|
| catalog | Yes |
search_catalogInspect
Search the merchant catalog for products matching a free-text query.
| Name | Required | Description | Default |
|---|---|---|---|
| catalog | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!