Brand Design Ltd. MCP server
ltd.branddesign/commercebranddesign.ltdstreamable-httpv1.2.1Scanned
AI representative of a brand, web and AI-visibility agency: ask, send an enquiry, order and pay.
12 tools: 1 can delete or cancel things, 1 do something that can't be undone, 6 change things and 4 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 1
- 9 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Brand Design Ltd. MCP server can do
The Brand Design Ltd. MCP server is published by branddesign.ltd, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (1 tool: start_payment), do things that cannot be undone, such as sending, paying or publishing (register_agent) and create or change data (6 tools: concierge, introduce, kya_challenge, kya_verify and 2 more). 4 tools only read.
2 tools read private data (kya_status and order_status); 2 tools bring in text other people can write (kya_verify and start_payment); 1 tool can send data out of your system (accept_offer). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 9 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 1.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 1Claude Code: deny
start_paymentStart payment for a stage.Reads text others write1 finding
Why it is in this group
- The name "start_payment" says "start": a word for a change.
- The name "start_payment" also says "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Start payment for a stage. Needs credentials. Without sharedPaymentToken you receive..."
Description, as the server wrote it Start payment for a stage. Needs credentials. Without sharedPaymentToken you receive the link to our payment page (form.redirect), which you may complete yourself with a card issued to you, or hand to the person you act for; on that page the card must be in the name on the invoice (for a company: its representative or the company name) and the cardholder address must be in the invoice country, and every order placed by an AI agent needs the cardholder to confirm with the bank (3-D Secure). With a delegated shared payment token the payment settles directly. The request must come from a verified robot: signed by its maker (Web Bot Auth) or from the published addresses of its maker. If the owner of the agent verified a DNS record with kya_challenge and kya_verify, the record is read again at payment and its limit applies; kya_status reads it. 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, OWNER_APPROVAL_REQUIRED (409) for a first order above EUR 1000 from a new e-mail or card until the merchant approves it, BUYER_BLOCKED (403), PAYMENTS_DISABLED (503).
Annotations the server declares
- title: Start payment
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Can't be undone 1Claude Code: ask
register_agentRegister yourself and receive a client identifier and a secret.No findings
Why it is in this group
- The description says "cannot be recovered".
Description, as the server wrote it 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 clientId:secret" for the other tools.
Annotations the server declares
- title: Register as an agent
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 6Claude Code: ask
accept_offerAccept the offer on behalf of the buyer.Can send data out1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a destination (input.billing.phone): what the tool writes goes there.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...the offer on behalf of the buyer. Needs credentials. This locks the billing identity, the o..."
Description, as the server wrote it 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. The request must come from a verified robot. Errors: KYA_VERIFICATION_REQUIRED or KYA_REVOKED (403) without it, 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.
Annotations the server declares
- title: Accept the offer
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
conciergeStart here: the information desk of Brand Design Ltd.1 finding
Why it is in this group
- The description's first verb is "start": a word for a change.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...pts an offer or pays. Questions need no credentials. An offer is prepared only for a verifi..."
Description, as the server wrote it Start here: the information desk of Brand Design Ltd. Without a question: who Brand Design Ltd. is, what it does, its clients and results and who confirms them, with links to check, and the next steps. With a question: an answer about the agency, its services, prices and how to order, from verified company knowledge, in the language of the question, with sources. When your principal wants to order, it can also prepare the offer with a checkout link, beside catalog and create_order here; it never accepts an offer or pays. Questions need no credentials. An offer is prepared only for a verified robot (signed by its maker or from the published addresses of its maker), as for create_order; credentials are optional. If your principal asks to be contacted, it can pass the enquiry to the founder. Pass the returned session to continue.
Annotations the server declares
- title: Information desk: the AI representative of Brand Design Ltd.
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_orderPlace an order for a service.1 finding
Why it is in this group
- The name "create_order" says "create": a word for a change.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Place an order for a service. Needs credentials. Returns the order id, the offer and an..."
Description, as the server wrote it 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[language].hash from it. Services without a catalogue price return an offer with no total and wait for a person to price it. The request must come from a verified robot: signed by its maker (Web Bot Auth) or from the published addresses of its maker. Errors: KYA_VERIFICATION_REQUIRED (403) without it, MISSING_ followed by the field id when a required brief field is absent, UNEXPECTED_FIELD when the brief has a key the service does not declare.
Annotations the server declares
- title: Place an order
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
introduceIntroduce yourself and the person or company you act for, and pass their enquiry to Nikola Mishev, the founder of Brand Design Ltd., by e-mail.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...our principal wants to be contacted. No credentials needed."
Description, as the server wrote it Introduce yourself and the person or company you act for, and pass their enquiry to Nikola Mishev, the founder of Brand Design Ltd., by e-mail. He replies to the contact you give. Use it only when your principal wants to be contacted. No credentials needed.
Annotations the server declares
- title: Pass an enquiry to the founder
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
kya_challengeAdds the owner limit: a verified DNS record on your own domain lets your owner cap the amount per order and withdraw your right to pay by removing it.1 finding
Why it is in this group
- The description's first verb is "add": a word for a change.
Findings
- Info
The input schema at properties.contact.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.contact.description: "...your own public domain. No IP address, credentials, custom port or URL fragment."
Description, as the server wrote it Adds the owner limit: a verified DNS record on your own domain lets your owner cap the amount per order and withdraw your right to pay by removing it. The mandatory domain verification is against the domain of your maker. 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.
Annotations the server declares
- title: Prepare domain-control verification
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
kya_verifyCheck the DNS TXT challenge for your currently authenticated agent and record domain-control verification.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 and is read again from DNS at every create_order, accept_offer and start_payment, which all require it. It does not grant buyer payment authority.
Annotations the server declares
- title: Verify domain control
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 4Show 4 read-only tools
catalogRead the service catalogue: names, prices, currency and terms.1 finding
Why it is in this group
- The description's first verb is "read": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...: names, prices, currency and terms. No credentials needed. All amounts are integers in the..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Read the catalogue
- readOnlyHint: true
- openWorldHint: false
kya_statusRead DNS domain-control verification for your currently authenticated agent.Reads private dataNo findings
Why it is in this group
- The name "kya_status" says "status": a word for reading.
What it can reach
- private-dataThe input names a secret (input.secret), and the tool reads: it reads secrets.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read domain-control verification
- readOnlyHint: true
- openWorldHint: false
manifestRead the commerce manifest: protocol, endpoints, authentication scheme, payment instrument and limits.1 finding
Why it is in this group
- The description's first verb is "read": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...heme, payment instrument and limits. No credentials needed."
Description, as the server wrote it Read the commerce manifest: protocol, endpoints, authentication scheme, payment instrument and limits. No credentials needed.
Annotations the server declares
- title: Read the commerce manifest
- readOnlyHint: true
- openWorldHint: false
order_statusRead the current state of the order, its offer and its payments, including the invoice number once one has been issued.Reads private data1 finding
Why it is in this group
- The name "order_status" says "status": a word for reading.
What it can reach
- private-dataThe input names a secret (input.secret), and the tool reads: it reads secrets.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...number once one has been issued. Needs credentials."
Description, as the server wrote it Read the current state of the order, its offer and its payments, including the invoice number once one has been issued. Needs credentials.
Annotations the server declares
- title: Read order status
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__commerce__accept_offer"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://branddesign.ltd/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://branddesignltd.eu.auth0.com/
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 destructive, 1 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://branddesign.ltd/mcp: tools/list returned 12 tools to an anonymous client, including start_payment (destructive), register_agent (irreversible), concierge (write), introduce (write), kya_challenge (write) and 3 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 6 to 8
Findings
Matches of fixed checks, with the text they matched.
- Infoconcierge
The description mentions "credentials".
What this check looks forMatched text
description: "...pts an offer or pays. Questions need no credentials. An offer is prepared only for a verifi..."
- Infointroduce
The description mentions "credentials".
What this check looks forMatched text
description: "...our principal wants to be contacted. No credentials needed."
- Infocatalog
The description mentions "credentials".
What this check looks forMatched text
description: "...: names, prices, currency and terms. No credentials needed. All amounts are integers in the..."
- Infomanifest
The description mentions "credentials".
What this check looks forMatched text
description: "...heme, payment instrument and limits. No credentials needed."
- Infokya_challenge
The input schema at properties.contact.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.contact.description: "...your own public domain. No IP address, credentials, custom port or URL fragment."
- Infocreate_order
The description mentions "credentials".
What this check looks forMatched text
description: "Place an order for a service. Needs credentials. Returns the order id, the offer and an..."
Show 3 more findingsShow fewer
- Infoaccept_offer
The description mentions "credentials".
What this check looks forMatched text
description: "...the offer on behalf of the buyer. Needs credentials. This locks the billing identity, the o..."
- Infostart_payment
The description mentions "credentials".
What this check looks forMatched text
description: "Start payment for a stage. Needs credentials. Without sharedPaymentToken you receive..."
- Infoorder_status
The description mentions "credentials".
What this check looks forMatched text
description: "...number once one has been issued. Needs credentials."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools8 changed.~8 changedView diff
- Changed:accept_offerChanges thingsinputSchema
- Changed:create_orderChanges thingsdescriptioninputSchema
- Changed:kya_challengeChanges thingsinputSchema
- Changed:kya_statusOnly readsinputSchema
- Changed:kya_verifyChanges thingsinputSchema
- Changed:order_statusOnly readsinputSchema
- Changed:register_agentCan't be undonedescription
- Changed:start_paymentDeletes or cancelsinputSchema
Tools6 changed.~6 changedView diff
- Changed:accept_offerChanges thingsdescription
- Changed:conciergeChanges thingsdescriptioninputSchema
- Changed:create_orderChanges thingsdescription
- Changed:kya_challengeChanges thingsdescription
- Changed:kya_verifyChanges thingsdescription
- Changed:start_paymentDeletes or cancelsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 8.View diff
- Tools that change things, listed without credentials: 6 to 8
Install
Pinned to version 1.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http commerce https://branddesign.ltd/mcpclaude mcp add --transport http commerce https://branddesign.ltd/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__commerce__catalog",
"mcp__commerce__manifest",
"mcp__commerce__kya_status",
"mcp__commerce__order_status"
],
"ask": [
"mcp__commerce__concierge",
"mcp__commerce__introduce",
"mcp__commerce__register_agent",
"mcp__commerce__kya_challenge",
"mcp__commerce__kya_verify",
"mcp__commerce__create_order",
"mcp__commerce__accept_offer"
],
"deny": [
"mcp__commerce__start_payment"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as commerce. Review it before you use it.
Capability tags behind 5 rules
- mcp__commerce__kya_verify untrusted-input
- mcp__commerce__kya_status private-data
- mcp__commerce__accept_offer outbound
- mcp__commerce__start_payment untrusted-input
- mcp__commerce__order_status private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ltd.branddesign/commerce/verify?hash=81bf297dabb6fc21576c7b5ada758a8e234e546e36f82c63fcf7cd97147cc58e" | jq -e '.changed == false'Pinned hash 81bf297dabb6, from Nov 21, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ltd.branddesign/commerce/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ltd.branddesign/commerce)Source: MCP Registry. Synced Nov 7, 2026, 08:17 UTC.
Brand Design Ltd. MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Brand Design Ltd. MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 8 of which can change, send or delete something, and 9 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Brand Design Ltd. MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: start_payment.
Can the Brand Design Ltd. MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: register_agent.
What tools does the Brand Design Ltd. MCP server have?
- 12 tools: 1 destructive, 1 irreversible, 6 write, 4 read. start_payment, register_agent, concierge, introduce, kya_challenge, kya_verify, create_order, accept_offer and 4 more.
Does the Brand Design Ltd. MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Brand Design Ltd. MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): accept_offer.
Has the Brand Design Ltd. MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.