# Brand Design Ltd. (remote · branddesign.ltd)

Order and pay for branding, design and web services with no human on the seller side.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `branddesign.ltd`: 65/100 (this document), [markdown](https://verifymcp.io/servers/ltd-branddesign-commerce/branddesign.md), [page](https://verifymcp.io/servers/ltd-branddesign-commerce/branddesign)

## Channel facts

- Endpoint: `https://branddesign.ltd/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 68% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ltd-branddesign-commerce 'https://branddesign.ltd/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ltd-branddesign-commerce": {
      "url": "https://branddesign.ltd/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ltd-branddesign-commerce": {
      "type": "http",
      "url": "https://branddesign.ltd/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ltd-branddesign-commerce]
url = "https://branddesign.ltd/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ltd-branddesign-commerce": {
      "type": "remote",
      "url": "https://branddesign.ltd/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ltd-branddesign-commerce --url 'https://branddesign.ltd/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ltd-branddesign-commerce:
    url: "https://branddesign.ltd/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ltd-branddesign-commerce": {
      "Transport": "http",
      "Url": "https://branddesign.ltd/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ltd-branddesign-commerce -t streamable-http -u 'https://branddesign.ltd/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 65, +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.

### 2026-09-18 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 64)

First indexed and scored.

## MCP tools (7)

### `catalog` (~44 tokens)

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.

### `manifest` (~28 tokens)

Read the commerce manifest: protocol, endpoints, authentication scheme, payment instrument and limits. No credentials needed.

### `register_agent` (~97 tokens)

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.

Input parameters:

- `contact` (string, required): A https:// or mailto: URL at which a human can reach whoever runs you.
- `name` (string, required): Your name, 2 to 80 characters.

### `create_order` (~164 tokens)

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.

Input parameters:

- `brief` (object, required): 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, required): Service identifier from the catalogue.

### `accept_offer` (~149 tokens)

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.

Input parameters:

- `accessToken` (string, required)
- `billing` (object, required): 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, required)
- `order` (string, required)
- `secret` (string): Your secret, if not sent in the Authorization header.
- `termsHash` (string, required)

### `start_payment` (~150 tokens)

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.

Input parameters:

- `accessToken` (string, required)
- `clientId` (string): Your client identifier, if not sent in the Authorization header.
- `order` (string, required)
- `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.

### `order_status` (~80 tokens)

Read the current state of the order and its payments, including the invoice number once one has been issued.

Input parameters:

- `accessToken` (string, required)
- `clientId` (string): Your client identifier, if not sent in the Authorization header.
- `order` (string, required)
- `secret` (string): Your secret, if not sent in the Authorization header.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ltd-branddesign-commerce/branddesign#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 65
- 2026-09-18: 64
- 2026-09-17: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://branddesign.ltd/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ltd-branddesign-commerce/branddesign.xml
- Changelog JSON feed: https://verifymcp.io/servers/ltd-branddesign-commerce/branddesign.json
- HTML version of this page: https://verifymcp.io/servers/ltd-branddesign-commerce/branddesign