Brand Design Ltd.
REMOTE · BRANDDESIGN.LTD · SCANNED SEP 20
Order and pay for branding, design and web services with no human on the seller side.
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 Security63
- 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 3 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 821 tokens (~117/item across 7 items; 7 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Brand Design Ltd. MCP server?
Brand Design Ltd. is a hosted endpoint at https://branddesign.ltd/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 · branddesign.ltd
claude mcp add --transport http ltd-branddesign-commerce 'https://branddesign.ltd/mcp'
{
"mcpServers": {
"ltd-branddesign-commerce": {
"url": "https://branddesign.ltd/mcp"
}
}
} {
"servers": {
"ltd-branddesign-commerce": {
"type": "http",
"url": "https://branddesign.ltd/mcp"
}
}
} [mcp_servers.ltd-branddesign-commerce] url = "https://branddesign.ltd/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ltd-branddesign-commerce": {
"type": "remote",
"url": "https://branddesign.ltd/mcp",
"enabled": true
}
}
} openclaw mcp add ltd-branddesign-commerce --url 'https://branddesign.ltd/mcp' --transport streamable-http
mcp_servers:
ltd-branddesign-commerce:
url: "https://branddesign.ltd/mcp" {
"McpServers": {
"ltd-branddesign-commerce": {
"Transport": "http",
"Url": "https://branddesign.ltd/mcp"
}
}
} assistant mcp add ltd-branddesign-commerce -t streamable-http -u 'https://branddesign.ltd/mcp'
{
"mcpServers": {
"ltd-branddesign-commerce": {
"type": "http",
"url": "https://branddesign.ltd/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.
- 19 Sept 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.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 64
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 20 Sept 2026 · Probed https://branddesign.ltd/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=branddesign.ltd | CN=YE2,O=Let's Encrypt,C=US | 11 Aug 2026 | 9 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6a74388d64193a3e847c45a4ec8d812a337 |
| SANs: branddesign.ltd, www.branddesign.ltd | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of branddesign.ltd. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ltd. | present | 54 | 8 | Verified |
| branddesign.ltd. | 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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://ajax.googleapis.com https://www.googletagmanager.com https://www.googleadservices.com https://www.google.com https://pagead2.googlesyndication.com https://googleads.g.doubleclick.net https://www.google-analytics.com https://connect.facebook.net https://bzrcdn.openai.com https://*.nitrocdn.com blob:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com https://*.nitrocdn.com; img-src 'self' data: blob: https://www.facebook.com https://www.google-analytics.com https://region1.google-analytics.com https://www.googletagmanager.com https://googleads.g.doubleclick.net https://pagead2.googlesyndication.com https://www.googleadservices.com https://www.google.com https://google.com https://www.google.bg https://stats.g.doubleclick.net https://bzr.openai.com https://*.nitrocdn.com https://cdn-ilelpfg.nitrocdn.com; connect-src 'self' data: blob: https://www.google-analytics.com https |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://branddesign.ltd/mcp | Verified | 200 | |
| http (plaintext) | http://branddesign.ltd/mcp | HTTPS enforced | 301 | https://branddesign.ltd/mcp |
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 →
accept_offer ~149
Accept the offer on behalf of the buyer. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | – |
| billing | object | yes | type (person or company), fullName or company with eik, email, country, city, address, phone. |
| clientId | string | – | Your client identifier, if not sent in the Authorization header. |
| offerVersion | string | yes | – |
| order | string | yes | – |
| secret | string | – | Your secret, if not sent in the Authorization header. |
| termsHash | string | yes | – |
No output schema declared.
No examples provided.
catalog ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_order ~164
Place an order for a service. Returns the order, an offer pinned to the hash of the service page, and an access token you must keep for the following calls. Services without a catalogue price return an offer with no total and wait for a person.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | object | yes | The fields the catalogue declares for this service. |
| clientId | string | – | Your client identifier, if not sent in the Authorization header. |
| idempotencyKey | string | – | Your own key, so a repeated call does not create a second order. |
| language | string | – | Language of the offer and the documents. Defaults to en. |
| secret | string | – | Your secret, if not sent in the Authorization header. |
| service | string | yes | Service identifier from the catalogue. |
No output schema declared.
No examples provided.
manifest ~28
Read the commerce manifest: protocol, endpoints, authentication scheme, payment instrument and limits. No credentials needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
order_status ~80
Read the current state of the order and its payments, including the invoice number once one has been issued.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | – |
| clientId | string | – | Your client identifier, if not sent in the Authorization header. |
| order | string | yes | – |
| secret | string | – | Your secret, if not sent in the Authorization header. |
No output schema declared.
No examples provided.
register_agent ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | A https:// or mailto: URL at which a human can reach whoever runs you. |
| name | string | yes | Your name, 2 to 80 characters. |
No output schema declared.
No examples provided.
start_payment ~150
Start payment for a stage. Without a token 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.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | – |
| clientId | string | – | Your client identifier, if not sent in the Authorization header. |
| order | string | yes | – |
| secret | string | – | Your secret, if not sent in the Authorization header. |
| sharedPaymentToken | string | – | Optional. A Stripe shared payment token granted to the seller profile named in the manifest. |
| stage | string | – | Defaults to advance. |
No output schema declared.
No examples provided.
What is the Brand Design Ltd. MCP server?
Brand Design Ltd. is an MCP server listed in the public MCP registry as ltd.branddesign/commerce. Order and pay for branding, design and web services with no human on the seller side. This page covers its hosted endpoint (https://branddesign.ltd/mcp).
Is the Brand Design Ltd. MCP server safe to use?
Brand Design Ltd. scores 65 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 Brand Design Ltd. MCP server expose?
Brand Design Ltd. exposes 7 tools: catalog, manifest, register_agent, create_order, accept_offer, and 2 more. Their descriptions and schemas cost roughly 712 tokens of context every time the server is loaded.
Does the Brand Design Ltd. MCP server require authentication?
No. We connected to Brand Design Ltd. without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Brand Design Ltd. MCP server still maintained?
Brand Design Ltd. is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.