# Brand Design Ltd. > Branding, design and web services you can order and pay for without a human on the seller side. - name: ltd.branddesign/commerce - version: 1.1.0 - connection class: R0 (autonomous) - trust: 79/100 flags: no-repository - quality: 92/100 (strong) - owner: not claimed - descriptor: https://api.protogrid.dev/v1/servers/ltd.branddesign%2Fcommerce - tools: https://api.protogrid.dev/v1/servers/ltd.branddesign%2Fcommerce/tools **An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe. ## Connection (mcpServers) ```json { "mcpServers": { "commerce": { "type": "http", "url": "https://branddesign.ltd/mcp" } } } ``` ## Trust - hygiene: 80 - liveness: 99 - freshness: 100 - provenance: 45 - drivers: +dns-namespace +reachable +uptime-98% +updated-5d-ago -no-repository - Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. ## Quality 92/100 (strong) ### protocol: 100 (weight 25) - pass `protocol.modern`: supports 2026-07-28 (server/discover) - pass `protocol.stateless`: answers without a session - pass `protocol.transport`: streamable HTTP - pass `protocol.list_ttl`: tool list is cacheable (ttlMs 3600000) ### authorization: n/a (weight 15) - n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth - n/a `auth.secret_in_url`: no templated URL ### tool hygiene: 93 (weight 30) - pass `tools.descriptions`: every tool has a description - pass `tools.description_length`: descriptions are concise - pass `tools.schemas`: every tool has an object input schema - pass `tools.annotations`: 10 of 10 tools declare readOnlyHint or destructiveHint - warn `tools.directory_hints`: 6 of 10 tools declare all four hints; missing: catalog (destructiveHint, idempotentHint); manifest (destructiveHint, idempotentHint); kya_status (destructiveHint, idempotentHint); … - pass `tools.token_cost`: about 3,601 tokens to load every tool - pass `tools.api_dump`: tools are not a one-to-one API dump ### stability: 75 (weight 15) - warn `stability.changes`: 8 tool changes in 30 days - pass `stability.rug_pull`: no tool changed its meaning under the same name ### dependencies: n/a (weight 15) - n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package - tools: 10, about 3,601 tokens to load them all - tool set hash: 13b44765aeb4b421eb0c790eb6204be2 - tools last changed: 2026-10-09T21:12:17.870Z - badge: [![protogrid quality](https://protogrid.dev/badge/ltd.branddesign/commerce.svg)](https://protogrid.dev/servers/ltd.branddesign/commerce) - Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. ### Tool changes - 2026-10-09 `accept_offer` changed (inputSchema) - 2026-10-05 `start_payment` changed (description) - before: Start payment for a stage. Needs credentials. Without sharedPaymentToken you receive a hosted payment session, which you may complete yourself with a payment instrument issued to you, or hand to the person you act for. With a delegated shared payment token the payment settles directly. A self-registered agent must first have current DNS domain-control KYA for its HTTPS contact domain; read the manifest for challenge, verification and status endpoints. KYA does not grant buyer payment authority. On-chain payment is not accepted. Errors: OFFER_EXPIRED (409) for an advance after 30 days, FINAL_NOT_RELEASED (409) when the final payment is not open yet, PAYMENTS_DISABLED (503). - after: Start payment for a stage. Needs credentials. Without sharedPaymentToken you receive a hosted payment session, which you may complete yourself with a payment instrument issued to you, or hand to the person you act for. With a delegated shared payment token the payment settles directly. A self-registered agent must first have current DNS domain-control KYA for its HTTPS contact domain: call kya_challenge with a domain you control, publish its DNS TXT record and call kya_verify; kya_status reads the current verification. KYA does not grant buyer payment authority. On-chain payment is not accepted. Errors: OFFER_EXPIRED (409) for an advance after 30 days, FINAL_NOT_RELEASED (409) when the final payment is not open yet, PAYMENTS_DISABLED (503). - 2026-10-05 `create_order` changed (inputSchema) - 2026-10-05 `kya_status` added - Read DNS domain-control verification for your currently authenticated agent. Needs commerce.read for OAuth. Returns verification status and, when present, DNS instructions and validity timestamps. This does not change the contact, challenge or verification. - 2026-10-05 `kya_verify` added - Check the DNS TXT challenge for your currently authenticated agent and record domain-control verification. Needs commerce.order for OAuth. First call kya_challenge and publish its exact DNS TXT record. The response gives verifiedAt and validUntil; verification is currently valid for 24 hours. This does not authorize a purchase or a payment. - 2026-10-05 `kya_challenge` added - Issue a fresh DNS TXT challenge for your currently authenticated agent identity. Needs commerce.order for OAuth. Supply an HTTPS contact URL on a domain you control, especially on the first OAuth connection. Omitting contact reuses the current contact. This replaces the previous challenge and clears its verification. Publish the returned txtValue at dnsName, then call kya_verify. Domain control does not establish buyer identity or grant spending authority. Do not publish secrets in DNS. - 2026-09-29 `start_payment` changed (description, annotations) - before: Start payment for a stage. Needs credentials. Without sharedPaymentToken you receive a hosted payment session, which you may complete yourself with a payment instrument issued to you, or hand to the person you act for. With a delegated shared payment token the payment settles directly. On-chain payment is not accepted. Errors: OFFER_EXPIRED (409) for an advance after 30 days, FINAL_NOT_RELEASED (409) when the final payment is not open yet, PAYMENTS_DISABLED (503). - after: Start payment for a stage. Needs credentials. Without sharedPaymentToken you receive a hosted payment session, which you may complete yourself with a payment instrument issued to you, or hand to the person you act for. With a delegated shared payment token the payment settles directly. A self-registered agent must first have current DNS domain-control KYA for its HTTPS contact domain; read the manifest for challenge, verification and status endpoints. KYA does not grant buyer payment authority. On-chain payment is not accepted. Errors: OFFER_EXPIRED (409) for an advance after 30 days, FINAL_NOT_RELEASED (409) when the final payment is not open yet, PAYMENTS_DISABLED (503). - 2026-09-26 `create_order` changed (inputSchema) Full history: https://api.protogrid.dev/v1/servers/ltd.branddesign%2Fcommerce/changes ## Remotes - https://branddesign.ltd/mcp (streamable-http, auth none, reachable true, uptime30d 0.9831933) ## Packages _none_ ## Tools (10) - `accept_offer`: Accept the offer on behalf of the buyer. Needs credentials. This locks the billing identity, the offer version and the hash of the terms as they stand at this moment. A later change to the website cannot pass for what was agreed. Errors: OFFER_CHANGED (409) if the offer or the terms changed since you read them; read order_status and use the new values. OFFER_EXPIRED (409) 30 days after the order. MANUAL_OFFER_REQUIRED (409) while a person has not priced the service yet. - `catalog`: Read the service catalogue: names, prices, currency and terms. No credentials needed. All amounts are integers in the minor unit; 100000 means 1000.00 EUR. - `create_order`: Place an order for a service. Needs credentials. Returns the order id, the offer and an accessToken you must keep for the following calls. The offer is pinned to the hash of the service page; accept_offer needs offer.version and offer.terms..hash from it. Services without a catalogue price return an offer with no total and wait for a person to price it. Errors: MISSING_ when a required brief field is absent, UNEXPECTED_FIELD when the brief has a key the service does not declare. - `kya_challenge`: Issue a fresh DNS TXT challenge for your currently authenticated agent identity. Needs commerce.order for OAuth. Supply an HTTPS contact URL on a domain you control, especially on the first OAuth connection. Omitting contact reuses the current contact. This replaces the previous challenge and clears its verification. Publish the returned txtValue at dnsName, then call kya_verify. Domain control does not establish buyer identity or grant spending authority. Do not publish secrets in DNS. - `kya_status`: Read DNS domain-control verification for your currently authenticated agent. Needs commerce.read for OAuth. Returns verification status and, when present, DNS instructions and validity timestamps. This does not change the contact, challenge or verification. - `kya_verify`: Check the DNS TXT challenge for your currently authenticated agent and record domain-control verification. Needs commerce.order for OAuth. First call kya_challenge and publish its exact DNS TXT record. The response gives verifiedAt and validUntil; verification is currently valid for 24 hours. This does not authorize a purchase or a payment. - `manifest`: Read the commerce manifest: protocol, endpoints, authentication scheme, payment instrument and limits. No credentials needed. - `order_status`: Read the current state of the order, its offer and its payments, including the invoice number once one has been issued. Needs credentials. - `register_agent`: Register yourself and receive a client identifier and a secret. No approval and no prior arrangement. The secret is returned once and cannot be recovered. Put them in the Authorization header as "Bearer :" for the other tools. - `start_payment`: Start payment for a stage. Needs credentials. Without sharedPaymentToken you receive a hosted payment session, which you may complete yourself with a payment instrument issued to you, or hand to the person you act for. With a delegated shared payment token the payment settles directly. A self-registered agent must first have current DNS domain-control KYA for its HTTPS contact domain: call kya_challenge with a domain you control, publish its DNS TXT record and call kya_verify; kya_status reads the current verification. KYA does not grant buyer payment authority. On-chain payment is not accepted. Errors: OFFER_EXPIRED (409) for an advance after 30 days, FINAL_NOT_RELEASED (409) when the final payment is not open yet, PAYMENTS_DISABLED (503).