# PatchDesign.AI (remote · patchdesign.ai)

Design custom embroidered, woven, chenille, printed and PVC patches, price them, and link to order.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `patchdesign.ai`: 82/100 (this document), [markdown](https://verifymcp.io/servers/ai-patchdesign-patch-designer/api-mcp.md), [page](https://verifymcp.io/servers/ai-patchdesign-patch-designer/api-mcp)

## Channel facts

- Endpoint: `https://patchdesign.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1405 tokens (~234/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 73/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the PatchDesign.AI MCP server?

PatchDesign.AI is a hosted endpoint at https://patchdesign.ai/api/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 ai-patchdesign-patch-designer 'https://patchdesign.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-patchdesign-patch-designer": {
      "url": "https://patchdesign.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-patchdesign-patch-designer": {
      "type": "http",
      "url": "https://patchdesign.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-patchdesign-patch-designer]
url = "https://patchdesign.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-patchdesign-patch-designer": {
      "type": "remote",
      "url": "https://patchdesign.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-patchdesign-patch-designer --url 'https://patchdesign.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-patchdesign-patch-designer:
    url: "https://patchdesign.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-patchdesign-patch-designer": {
      "Transport": "http",
      "Url": "https://patchdesign.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-patchdesign-patch-designer -t streamable-http -u 'https://patchdesign.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-patchdesign-patch-designer": {
      "type": "http",
      "url": "https://patchdesign.ai/api/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-11-04 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 81, 0)

- [security] Tool “quote_patch” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good

### 2026-11-01 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 78, 0)

- [security] Resource “design-card” now points somewhere else: ui://patchdesign/design-card-4900213d.html → ui://patchdesign/design-card-15089e42.html

### 2026-10-26 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `quote_patch` (~259 tokens)

Price a custom patch

Price a custom patch from the live PatchDesign.AI production price table: type, size and quantity in, the per-patch and total price in USD out, with the next quantity breaks and what the price already includes (artwork, a pre-production sample, worldwide shipping). The price returned is the customer's price, not a starting figure. No quote is needed unless they choose a backing or border with no set price; then that price is confirmed within 2 business hours. There is no minimum: quantity 1 returns the sample prices, and by default quote the price breaks. Use it when the user asks about a price or a minimum.

Input parameters:

- `heightIn` (number): Height in inches, 1 to 12.5. Default 3.
- `patchType` (string): Patch type: embroidered (default), woven, chenille, printed, pvc-2d or pvc-3d. Iron-on, velcro and sew-on are backings on an embroidered patch, so use embroidered for those.
- `quantity` (integer): How many patches. Default 100. Use 1 for a single patch.
- `widthIn` (number): Width in inches, 1 to 12.5. Default 3.

### `design_patch` (~314 tokens)

Design a custom patch

Generate a production-ready custom patch design from a description (and optionally a reference image URL). Takes about 15 to 30 seconds and returns the design as an image plus a design id for edits and an order link. Previews carry a light PatchDesign.AI watermark; the clean file comes with an order. Say what the patch shows and any text on it, spelled exactly. To change a design already made in this chat, use edit_patch with its id. A chat gets 10 free designs, then the user signs in with the link from sign_in_link. If the result says the service was busy, call it once more with the same input.

Input parameters:

- `description` (string, required): What the patch should show: subject, colors, mood, and any lettering spelled exactly as it should appear. 3 to 1500 characters.
- `heightIn` (number): Height in inches, 1 to 12.5. Default 3.
- `patchType` (string): Patch type: embroidered (default), woven, chenille, printed, pvc-2d or pvc-3d. Iron-on, velcro and sew-on are backings on an embroidered patch, so use embroidered for those.
- `referenceImageUrl` (string): Optional https URL of a logo, sketch or photo to base the patch on. With a reference, the description is guidance about how to adapt it.
- `widthIn` (number): Width in inches, 1 to 12.5. Default 3.

### `edit_patch` (~170 tokens)

Change a design

Make a change to a design from this chat: pass its design id (d_...) and the change in plain words ("make the border gold", "change TROOP 42 to TROOP 24"). Use it for a change the user asks for later in the chat too, so the original artwork is kept. Returns a new design with its own id; the original stays. Counts as one design.

Input parameters:

- `designId` (string, required): The design id from the design_patch or edit_patch result for that design, e.g. d_1a2b3c4d5e6f7a8b, not its D- number. It works in any later turn of the chat.
- `instruction` (string, required): The change, in plain words. 2 to 800 characters.

### `order_link` (~134 tokens)

Order a design

The link where the user orders a design from this chat, with the type, size and quantity set, plus the price for that quantity. Nothing is ordered or charged by this call; the user reviews and pays on patchdesign.ai. Use it when the user wants to buy, get a quote by email, or adjust size and quantity on the site.

Input parameters:

- `designId` (string, required): The design id (d_...) from the result of that design, not its D- number.
- `quantity` (integer): How many patches they want. There is no minimum order. Default: the first price break for the type.

### `sign_in_link` (~79 tokens)

Sign in to PatchDesign.AI

A link that connects this chat to the user's PatchDesign.AI account (free), lifting the 10-design limit to the account allowance of 50 designs a day and 250 a month, and saving the designs to their account. The link expires in 15 minutes. Give it to the user, then continue once they say they have connected.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-patchdesign-patch-designer/api-mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 78
- 2026-10-26: 78
- 2026-10-25: 77
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73

## Common questions

### What is the PatchDesign.AI MCP server?

PatchDesign.AI is an MCP server listed in the public MCP registry as ai.patchdesign/patch-designer. Design custom embroidered, woven, chenille, printed and PVC patches, price them, and link to order. This page covers its hosted endpoint (https://patchdesign.ai/api/mcp).

### Is the PatchDesign.AI MCP server safe to use?

PatchDesign.AI scores 82 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 PatchDesign.AI MCP server expose?

PatchDesign.AI exposes 5 tools: quote_patch, design_patch, edit_patch, order_link, sign_in_link. Their descriptions and schemas cost roughly 956 tokens of context every time the server is loaded.

### Does the PatchDesign.AI MCP server require authentication?

No. We connected to PatchDesign.AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PatchDesign.AI MCP server still maintained?

PatchDesign.AI is still listed as active in the MCP registry. We last reached this channel on 5 November 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://patchdesign.ai/api/mcp
- Repository: https://github.com/KinorPartners/patchdesign-mcp
- Website: https://patchdesign.ai/connect
- Changelog RSS feed: https://verifymcp.io/servers/ai-patchdesign-patch-designer/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-patchdesign-patch-designer/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-patchdesign-patch-designer/api-mcp