PatchDesign.AI
REMOTE · PATCHDESIGN.AI
Design custom embroidered, woven, chenille, printed and PVC patches, price them, and link to order.
Available components
Last scanned (1 hour ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
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.
- 4 Nov 26 +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.
- 3 Nov 26 0
- Tool “quote_patch” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 27 Oct 26 0
- Resource “design-card” now points somewhere else: ui://patchdesign/design-card-4900213d.html → ui://patchdesign/design-card-15089e42.html security
- 26 Oct 26 +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.
- 23 Oct 26 +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.
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 5 Nov 2026 · Probed https://patchdesign.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=patchdesign.ai | CN=YE2,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6508ba9845fabe8e28b22e1ed23b0a52c2b |
| SANs: *.patchdesign.ai, patchdesign.ai | ||||||
| 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 patchdesign.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| patchdesign.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://patchdesign.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://patchdesign.ai/api/mcp | HTTPS enforced | 301 | https://patchdesign.ai/api/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 →
design_patch Design a custom patch ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | 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. |
No output schema declared.
No examples provided.
edit_patch Change a design ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| designId | string | yes | 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 | yes | The change, in plain words. 2 to 800 characters. |
No output schema declared.
No examples provided.
order_link Order a design ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| designId | string | yes | 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. |
No output schema declared.
No examples provided.
quote_patch Price a custom patch ~259
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
sign_in_link Sign in to PatchDesign.AI ~79
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · patchdesign.ai
claude mcp add --transport http ai-patchdesign-patch-designer 'https://patchdesign.ai/api/mcp'
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.