Custom Blinds Shop
REMOTE · SHOP.CUSTOMBLINDS.CO.ZA
South Africa's first AI-transactable blinds, shutters and awnings catalogue with live ZAR pricing.
Available components
Last scanned (10 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
Recent critical change
Authorization (29 Oct 2026). See the changelog before you install this server.
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_order). See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3903 tokens (~150/item across 26 items; 26 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 Management96
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage91
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “request_swatch” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 68% ▼ functional
- Schema quality: excellent → good functional
- “cancel_cart” reworded the description of “cart_id” cosmetic
- “cancel_checkout” reworded the description of “checkout_id” cosmetic
- “check_colour_stock” reworded the description of “colour_name” cosmetic
- “check_colour_stock” reworded the description of “product_id” cosmetic
- “complete_checkout” reworded the description of “checkout_id” cosmetic
- “create_cart” reworded the description of “customer” cosmetic
- “create_checkout” reworded the description of “customer” cosmetic
- “create_checkout” reworded the description of “items” cosmetic
- “get_cart” reworded the description of “cart_id” cosmetic
- “get_checkout” reworded the description of “checkout_id” cosmetic
- “get_order” reworded the description of “customer_email” cosmetic
- “get_order” reworded the description of “order_id” cosmetic
- “get_product” reworded the description of “product_id” cosmetic
- “get_product_recommendation” reworded the description of “aesthetic” cosmetic
- “get_product_recommendation” reworded the description of “location” cosmetic
- “get_product_recommendation” reworded the description of “max_budget_zar” cosmetic
- “get_product_recommendation” reworded the description of “primary_concern” cosmetic
- “get_product_recommendation” reworded the description of “room” cosmetic
- “get_whatsapp_handoff” reworded the description of “customer_name” cosmetic
- “lookup_catalog” reworded the description of “colour” cosmetic
- “lookup_catalog” reworded the description of “max_height_mm” cosmetic
- “lookup_catalog” reworded the description of “max_width_mm” cosmetic
- “update_cart” reworded the description of “cart_id” cosmetic
- “update_cart” reworded the description of “customer” cosmetic
- “update_cart” reworded the description of “items” cosmetic
- “update_cart” reworded the description of “op” cosmetic
- “update_checkout” reworded the description of “checkout_id” cosmetic
- “update_checkout” reworded the description of “customer” cosmetic
- “update_checkout” reworded the description of “payment_method” cosmetic
- 2 Nov 26 0
- “configure_product” added an optional parameter “no_drill” cosmetic
- “get_price” added an optional parameter “no_drill” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_ar_visualizer_url” rewrote its description, which is the text the model reads security
- 29 Oct 26 +3
- Authorization: unverified → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cancel_cart” is now declared destructive security
- Tool “cancel_checkout” is now declared destructive security
- Tool “complete_checkout” is now declared destructive security
- Tool “create_checkout” is now declared destructive security
- Tool “create_order” is now declared destructive security
- Tool “update_cart” is now declared destructive security
- Tool “update_checkout” is now declared destructive security
- Schema quality: 127 → 156 ▼ functional
- Tool coverage: 66% → 100% ▲ functional
- Schema quality: good → excellent functional
- MCP protocol version: 2024-11-05 → 2025-06-18 functional
- “cancel_cart” reworded the description of “cart_id” cosmetic
- “cancel_checkout” reworded the description of “checkout_id” cosmetic
- “check_colour_stock” reworded the description of “colour_name” cosmetic
- “check_colour_stock” reworded the description of “product_id” cosmetic
- “complete_checkout” reworded the description of “checkout_id” cosmetic
- “create_cart” reworded the description of “customer” cosmetic
- “create_checkout” reworded the description of “customer” cosmetic
- “create_checkout” reworded the description of “items” cosmetic
- “get_cart” reworded the description of “cart_id” cosmetic
- “get_checkout” reworded the description of “checkout_id” cosmetic
- “get_order” reworded the description of “customer_email” cosmetic
- “get_order” reworded the description of “order_id” cosmetic
- “get_product” reworded the description of “product_id” cosmetic
- “get_product_recommendation” reworded the description of “aesthetic” cosmetic
- “get_product_recommendation” reworded the description of “location” cosmetic
- “get_product_recommendation” reworded the description of “max_budget_zar” cosmetic
- “get_product_recommendation” reworded the description of “primary_concern” cosmetic
- “get_product_recommendation” reworded the description of “room” cosmetic
- “get_whatsapp_handoff” reworded the description of “customer_name” cosmetic
- “lookup_catalog” reworded the description of “colour” cosmetic
- “lookup_catalog” reworded the description of “max_height_mm” cosmetic
- “lookup_catalog” reworded the description of “max_width_mm” cosmetic
- “request_swatch” reworded the description of “customer_email” cosmetic
- “request_swatch” reworded the description of “customer_name” cosmetic
- “update_cart” reworded the description of “cart_id” cosmetic
- “update_cart” reworded the description of “customer” cosmetic
- “update_cart” reworded the description of “items” cosmetic
- “update_cart” reworded the description of “op” cosmetic
- “update_checkout” reworded the description of “checkout_id” cosmetic
- “update_checkout” reworded the description of “customer” cosmetic
- “update_checkout” reworded the description of “payment_method” cosmetic
- 27 Oct 26 0
- Tool “create_checkout” rewrote its description, which is the text the model reads security
- Tool “get_ar_visualizer_url” rewrote its description, which is the text the model reads security
- Tool “get_delivery_estimate” rewrote its description, which is the text the model reads security
- Tool “request_price_match” rewrote its description, which is the text the model reads security
- “get_ar_visualizer_url” reworded the description of “mode” cosmetic
- “get_ar_visualizer_url” reworded the description of “product_id” cosmetic
- 24 Oct 26 0
- Tool “request_price_match” rewrote its description, which is the text the model reads security
- 23 Oct 26 +2
- HSTS header: fail → pass ▲ security
- Tool “create_checkout” rewrote its description, which is the text the model reads security
- 21 Oct 26 −3
- HSTS header: pass → fail ▼ security
- Tool “cancel_cart” rewrote its description, which is the text the model reads security
- Tool “create_cart” rewrote its description, which is the text the model reads security
- Tool “create_checkout” rewrote its description, which is the text the model reads security
- Tool “create_order” rewrote its description, which is the text the model reads security
- Tool “get_ar_visualizer_url” rewrote its description, which is the text the model reads security
- Tool “get_delivery_estimate” rewrote its description, which is the text the model reads security
- Tool “get_order” rewrote its description, which is the text the model reads security
- Tool “get_product_recommendation” rewrote its description, which is the text the model reads security
- Tool “get_whatsapp_handoff” rewrote its description, which is the text the model reads security
- Tool “request_price_match” rewrote its description, which is the text the model reads security
- Tool “request_swatch” rewrote its description, which is the text the model reads security
- Tool “submit_enquiry” rewrote its description, which is the text the model reads security
- “request_swatch” added a required parameter “order_ref”, so existing callers break ▼ functional
- Schema quality: excellent → good functional
- Server version: 1.0.0 → 2.0.0 functional
- “request_swatch” reworded the description of “swatch_codes” cosmetic
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://shop.customblinds.co.za/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=customblinds.co.za | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d8fba3a17964571d1363bd9ccda04e00 |
| SANs: customblinds.co.za, shop.customblinds.co.za, *.shop.customblinds.co.za | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of shop.customblinds.co.za. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| za. | DS published | 45749 | 8 | Verified |
| co.za. | DS published | 41369 | 8 | Verified |
| customblinds.co.za. | No DS | 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 |
| content-security-policy | frame-ancestors 'self' https://customblinds.co.za https://*.customblinds.co.za; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shop.customblinds.co.za/mcp | Verified | 200 | |
| http (plaintext) | http://shop.customblinds.co.za/mcp | HTTPS enforced | 301 | https://shop.customblinds.co.za/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 →
cancel_cart ~65
Permanently delete a cart by cart_id. Use when the customer abandons the session or wants to start over. Has no effect on any checkout or paid order already created from this cart. Irreversible, create a new cart to restart.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cancelled | boolean | yes | – |
| cart_id | string | yes | – |
No examples provided.
cancel_checkout ~63
Abort an unpaid checkout and release its checkout_id. Use if the customer changes their mind after create_checkout but before completing payment. Has no effect on orders already confirmed by webhook. To restart, create a new cart and checkout from scratch.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | – |
| status | string | yes | – |
No examples provided.
check_colour_stock ~90
Verify whether a specific colour is available before configure_product. Returns in_stock boolean, expected_restock_date if out of stock, and up to 5 alternative in-stock colours ordered by similarity. Call this when a customer requests a named colour or when you want to prevent a configure_product failure due to an out-of-stock selection.
| Name | Type | Req | Description |
|---|---|---|---|
| colour_name | string | yes | – |
| product_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| available_colours | array | – | – |
| colour | string | – | – |
| exact_colour_match | boolean | – | – |
| expected_restock | – | – | – |
| found | boolean | – | – |
| in_stock | boolean | yes | – |
| matching_colours | array | – | – |
| message | string | – | – |
| product_id | string | – | – |
| requires_exact_colour_selection | boolean | – | – |
No examples provided.
complete_checkout ~136
Generate a Yoco card or Ozow instant-EFT payment link; this does NOT complete payment. Rejects cancelled checkouts and rechecks stock and totals first. An atomic claim prevents competing gateway calls. Returns payment_url or null plus status and message; cloud callers may be held. Retain a successful URL: repeat calls return payment_pending with no URL. Gateway failures raise an error, send no payment-link email and require team review rather than an automatic retry. Poll get_order with customer_email for payment status.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | – |
| payment_method | string | – | Overrides any value set in create_checkout/update_checkout |
| Name | Type | Req | Description |
|---|---|---|---|
| ap2 | object | – | – |
| checkout_id | string | yes | – |
| currency | string | – | – |
| customer | object | – | – |
| item_count | number | – | – |
| items | – | – | – |
| message | string | yes | – |
| next_step | string | – | – |
| payment_method | – | – | – |
| payment_url | – | yes | – |
| provider_reference | – | – | – |
| status | – | yes | – |
| total_zar | number | – | – |
No examples provided.
configure_product ~303
Lock in a full blind specification: product, dimensions, colour, and mount type (inside recess or outside face-fix). Validates that the colour exists and is in stock, then prices the blind. Returns a configuration summary to pass directly into create_cart. Call check_colour_stock first if availability is uncertain.
| Name | Type | Req | Description |
|---|---|---|---|
| colour | string | yes | Colour name (must match available colours) |
| finish | string | – | Optional finish for aluminium venetians |
| height_mm | number | yes | Height/drop in millimetres |
| mount_type | string | yes | Use inside (recess) or outside (face-fix); handler requires a nonempty value |
| no_drill | boolean | – | Optional. true for the no-drill option (tension brackets, inside the frame, max 2000mm wide; 1500mm on 25mm venetians). Adds the R65 no-drill kit per blind. Offered on indoor roller blinds, including… |
| product_id | string | yes | product_id from search_catalog or lookup_catalog |
| province | string | – | Optional. Customer's South African province or city. Garden Route locations get Duncan's direct contact; other locations get the online shop contact. |
| quantity | number | – | Number of blinds (default 1) |
| width_mm | number | yes | Width in millimetres |
| Name | Type | Req | Description |
|---|---|---|---|
| colour | string | yes | – |
| contact | object | – | – |
| currency | string | yes | – |
| delivery | string | – | – |
| effective_height_mm | number | – | – |
| effective_width_mm | number | – | – |
| finish | – | – | – |
| height_mm | number | yes | – |
| in_stock | boolean | – | – |
| lead_time | string | – | – |
| limits | object | – | – |
| minimum_charge_applied | boolean | – | – |
| mount_type | string | yes | – |
| next_step | string | – | – |
| price_zar | number | – | – |
| product_id | string | yes | – |
| product_name | string | – | – |
| quantity | number | yes | – |
| summary | string | – | – |
| total_price_zar | number | yes | – |
| unit_price_zar | number | yes | – |
| vat_included | boolean | – | – |
| width_mm | number | yes | – |
No examples provided.
create_cart ~91
Start the open UCP purchase flow, no auth needed. Creates a cart session and returns a cart_id (24-hour TTL). Optionally seed with pre-configured blind items and customer details. Next step: update_cart to add items, then create_checkout → complete_checkout to mint the payment link.
| Name | Type | Req | Description |
|---|---|---|---|
| customer | object | – | – |
| items | array | – | Optional configured items; all submitted prices are ignored |
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | – |
| created_at | string | yes | – |
| currency | string | yes | – |
| customer | – | yes | – |
| expires_at | string | yes | – |
| item_count | number | yes | – |
| items | array | yes | – |
| total_zar | number | yes | – |
| updated_at | string | yes | – |
No examples provided.
create_checkout ~111
Phase 1 of 2 in the purchase flow. Convert a cart (or inline items + customer) into a checkout. Customer name, email, and phone are required. Returns checkout_id. No payment link is minted yet, call complete_checkout for that. Use update_checkout to correct customer details before finalising.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | – | Either cart_id or items required |
| customer | object | – | – |
| items | array | – | – |
| payment_method | string | – | Default 'yoco' |
| Name | Type | Req | Description |
|---|---|---|---|
| ap2 | object | – | – |
| checkout_id | string | yes | – |
| currency | string | yes | – |
| customer | object | – | – |
| item_count | number | – | – |
| items | – | – | – |
| message | string | – | – |
| next_step | string | – | – |
| payment_method | – | – | – |
| payment_url | – | – | – |
| provider_reference | – | – | – |
| status | – | yes | – |
| total_zar | number | yes | – |
No examples provided.
create_order ~170
Legacy auth-required tool, prefer the open UCP flow (create_cart → create_checkout → complete_checkout) which needs no credentials. Use create_order only if you hold a Bearer token and want a single-call path to a payment link. All item prices are re-verified server-side against the live pricing engine, agent-supplied prices are ignored. Returns a Yoco or Ozow payment_url.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_address | string | – | Delivery address |
| customer_city | string | – | Delivery city |
| customer_email | string | yes | Customer email address |
| customer_name | string | yes | Customer full name |
| customer_phone | string | yes | Customer phone number |
| items | array | yes | Array of configured blind items |
| payment_method | string | – | Yoco card or Ozow instant EFT |
| Name | Type | Req | Description |
|---|---|---|---|
| ap2 | object | – | – |
| checkout_id | string | yes | – |
| currency | string | – | – |
| customer | object | – | – |
| item_count | number | – | – |
| items | – | – | – |
| message | string | yes | – |
| next_step | string | – | – |
| order_reference | string | yes | – |
| payment_method | – | – | – |
| payment_url | – | yes | – |
| provider_reference | – | – | – |
| status | – | yes | – |
| total_zar | number | – | – |
No examples provided.
get_ar_visualizer_url ~244
Returns the link to the Custom Blinds Visualiser (See it before you buy it), pre-selected to the product when it is supported. The customer adds a photo of their window (any angle), picks a blind and colour, and previews it on their own window. A preview of colour and style, not a measuring tool. No measuring or marking. A name and WhatsApp number are needed; 2 free previews per customer. Also returns the measuring guide (mode 'measure' makes it the main url) and the list of supported products. A customer still unsure of sizes can order with best guess sizes, receive a free tape measure and confirm before production starts. Use when a customer wants to see how a blind or colour will look before ordering, or is unsure how to measure.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Which link goes in url: visualize (own-window visualiser), measure (measuring guide) or both (visualiser, the default). Both links are always returned. |
| product_id | string | – | Optional. Pre-select a product in the visualiser (e.g. roller-blockout, double-roller-zebra, outdoor-blinds). |
| Name | Type | Req | Description |
|---|---|---|---|
| measure_url | string | yes | – |
| note | string | yes | – |
| product_id | – | – | – |
| supported_products | array | – | – |
| url | string | yes | – |
| visualiser_url | string | yes | – |
No examples provided.
get_cart ~66
Retrieve live cart state by cart_id: full item list, calculated totals in ZAR, and any customer details stored so far. Call after update_cart to confirm changes are correct before proceeding to create_checkout. Cart expires after 24 hours of inactivity.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | – |
| created_at | string | yes | – |
| currency | string | yes | – |
| customer | – | yes | – |
| expires_at | string | yes | – |
| item_count | number | yes | – |
| items | array | yes | – |
| total_zar | number | yes | – |
| updated_at | string | yes | – |
No examples provided.
get_checkout ~72
Read checkout by checkout_id. Returns persisted order status, payment_status, payment_method, items, customer, total_zar and currency. Initial order status is started, not pending. This tool does not return a previously generated payment_url: retain the complete_checkout response in caller context.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| ap2 | object | – | – |
| checkout_id | string | yes | – |
| currency | string | yes | – |
| customer | object | – | – |
| item_count | number | – | – |
| items | – | – | – |
| message | string | – | – |
| next_step | string | – | – |
| payment_method | – | – | – |
| payment_url | – | – | – |
| provider_reference | – | – | – |
| status | – | yes | – |
| total_zar | number | yes | – |
No examples provided.
get_delivery_estimate ~119
Explain the lead time for a new order. Production takes 5 to 7 working days once payment clears, outside peak seasons, then courier transit of about 2 to 5 working days. Returns the ranges and a plain-language summary safe to share. Never quote a dispatch or delivery date: weather and production set them. Call this when a customer asks 'when will it arrive?'.
| Name | Type | Req | Description |
|---|---|---|---|
| order_date | string | – | ISO date string of the order placement date (e.g. '2026-05-18'). Defaults to today. |
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_after_dispatch | string | yes | – |
| expedited_available | boolean | – | – |
| important | string | yes | – |
| order_date | string | – | – |
| production_starts | string | – | – |
| production_working_days_max | number | yes | – |
| production_working_days_min | number | yes | – |
| summary | string | yes | – |
| transit_working_days_max | number | yes | – |
| transit_working_days_min | number | yes | – |
No examples provided.
get_order ~80
Retrieve a confirmed order's status, items, and payment details by order_id. customer_email is required as soft-auth and must exactly match the order record, prevents arbitrary order lookups. Returns payment status (paid | pending | failed), production status, and dispatch date once available.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | – |
| order_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| items | – | – | – |
| lead_time | string | – | – |
| order_id | string | yes | – |
| order_reference | string | – | – |
| order_status | – | – | – |
| paid_at | – | – | – |
| payment_status | – | yes | – |
| total_zar | number | yes | – |
No examples provided.
get_payment_methods ~85
List available payment processors and their capabilities. Returns Yoco (card, immediate) and Ozow (instant EFT via South African bank account). Call when the customer asks 'how can I pay?' or before presenting options. The result informs the payment_method field in create_checkout and complete_checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| order_total_zar | number | – | Optional. For future per-handler limit filtering. |
| Name | Type | Req | Description |
|---|---|---|---|
| default_currency | string | yes | – |
| handlers | array | yes | – |
| note | string | yes | – |
No examples provided.
get_price ~314
Get an exact ZAR price using product_id from search_catalog or lookup_catalog, width_mm and height_mm. Prices include VAT and delivery. Colour selects the bamboo price tier where applicable. A price is not a stock reservation: validate the exact colour and mount with configure_product before creating a cart. Failure can return success:false or a JSON-RPC validation error.
| Name | Type | Req | Description |
|---|---|---|---|
| colour | string | – | Optional bamboo colour for colour-specific tier pricing |
| finish | string | – | Optional finish for aluminium products: Plain, Brushed, Woodgrain |
| height_mm | number | yes | Height/drop in millimetres (e.g. 1500) |
| no_drill | boolean | – | Optional. true for the no-drill option (tension brackets, inside the frame, max 2000mm wide; 1500mm on 25mm venetians). Adds the R65 no-drill kit per blind. Offered on indoor roller blinds, including… |
| product_id | string | yes | product_id from search_catalog or lookup_catalog (e.g. roller-blockout) |
| province | string | – | Optional. Customer's South African province or city. Garden Route locations get Duncan's direct contact; other locations get the online shop contact. |
| quantity | number | – | Number of blinds (default 1) |
| width_mm | number | yes | Width in millimetres (e.g. 1200) |
| Name | Type | Req | Description |
|---|---|---|---|
| contact | object | – | – |
| currency | string | yes | – |
| delivery | string | – | – |
| effective_height_mm | number | – | – |
| effective_width_mm | number | – | – |
| finish | – | – | – |
| height_mm | number | yes | – |
| lead_time | string | – | – |
| limits | object | – | – |
| minimum_charge_applied | boolean | – | – |
| next_step | string | – | – |
| product_id | string | yes | – |
| product_name | string | – | – |
| quantity | number | yes | – |
| total_price_zar | number | yes | – |
| unit_price_zar | number | yes | – |
| vat_included | boolean | yes | – |
| width_mm | number | yes | – |
No examples provided.
get_product ~76
Fetch complete details for one product by id (e.g. roller-blockout, venetian-25mm-aluwood). Returns all available colours with in-stock status, materials, features, and maximum supported dimensions. Use before configure_product to confirm a colour exists and is in stock before committing.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| colour_count_in_stock | number | – | – |
| colours | array | yes | – |
| description | string | – | – |
| features | array | – | – |
| installation_type | string | – | – |
| materials | array | – | – |
| max_height_mm | – | – | – |
| max_width_mm | – | – | – |
| name | string | yes | – |
| product_id | string | yes | – |
| product_url | string | yes | – |
| schema_url | string | – | – |
| size_limits | – | – | – |
| starting_price_zar | – | – | – |
| suitable_for | array | – | – |
No examples provided.
get_product_recommendation ~134
Translate a customer's primary concern into a product recommendation. primary_concern must be one of: blockout, heat, glare, moisture, privacy, security, automation. Optionally narrow by room (bedroom, lounge, etc.), location, budget, and aesthetic. Returns a recommended product_id with rationale, pass it to get_price or configure_product next. Security concern routes to brochure MCP (Garden Route customers only).
| Name | Type | Req | Description |
|---|---|---|---|
| aesthetic | string | – | – |
| location | string | – | – |
| max_budget_zar | number | – | – |
| primary_concern | string | yes | – |
| room | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| handoff | object | – | – |
| notes | string | – | – |
| recommendations | array | yes | – |
No examples provided.
get_whatsapp_handoff ~168
Generate a pre-filled WhatsApp deep link to hand the customer off to the right contact. Garden Route locations (Knysna, Plett, George, Sedgefield, etc.) route to Duncan Kane for a free in-home consultation, booked on the same WhatsApp line (+27760228410); all other South African locations route to that line too (+27760228410). It is WhatsApp only, no voice calls. Use when the customer prefers human assistance or when self-serve checkout isn't appropriate.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_name | string | – | – |
| location | string | – | City/suburb. Drives Duncan vs shop routing. |
| message | string | – | Optional additional message to prefill |
| product_context | string | – | e.g. 'roller blockout for bedroom' |
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | yes | – |
| recipient | string | yes | – |
| recipient_phone | string | yes | – |
| whatsapp_url | string | yes | – |
No examples provided.
lookup_catalog ~107
Preferred structured discovery. Filter by category, partial colour name or required supported width/drop in mm. Returns results containing product_id, name, category and product_url, plus total. Width/drop filters check separate maximums, not every combination; confirm the exact pair with get_price.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | roller | venetian | honeycomb | vertical | outdoor |
| colour | string | – | – |
| max_height_mm | number | – | – |
| max_width_mm | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| total | number | yes | – |
No examples provided.
request_price_match ~219
Submit a price match claim when the customer has found the same blind at a lower price elsewhere. Custom Blinds matches verified South African retailer prices for identical product, dimensions, and specs. Returns a pre-filled WhatsApp link to the claims team. Not applicable to: Blinds Direct (same supplier), clearance or flash-sale prices, or out-of-stock items. Requires product_id and competitor_price_zar at minimum.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor_name | string | – | Name of the competitor (e.g. 'Blind Empire') |
| competitor_price_zar | number | yes | Competitor's price in ZAR (incl. VAT) |
| competitor_url | string | – | URL to competitor product page or quote |
| customer_name | string | – | Customer name |
| customer_whatsapp | string | – | Customer WhatsApp number for follow-up |
| height_mm | number | – | Window height/drop in mm |
| product_id | string | yes | Product the customer wants to match (e.g. roller-blockout) |
| width_mm | number | – | Window width in mm |
| Name | Type | Req | Description |
|---|---|---|---|
| claim_summary | object | yes | – |
| exclusions | array | yes | – |
| message | string | yes | – |
| note | string | yes | – |
| success | boolean | yes | – |
| whatsapp_url | string | yes | – |
No examples provided.
request_swatch ~202
Log up to 5 colour codes against an EXISTING order for the team (order_ref required; without it the tool returns status order_required and logs nothing). Sample swatches, not off-cuts: on orders over R8,000 the customer can ask on WhatsApp for swatches in the colours they like, for the product they are ordering; if nothing suits, full refund with no fees. Never quote a sample price or courier cost.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | Customer's email address. |
| customer_name | string | yes | Customer's full name. |
| customer_phone | string | yes | Used as WhatsApp number |
| order_ref | string | yes | The order reference the swatches ship with. Required. |
| product_interest | string | yes | e.g. 'Roller Blockout' or 'Honeycomb' |
| suburb | string | – | Optional delivery suburb |
| swatch_codes | array | – | Optional specific colour codes (max 5) |
| Name | Type | Req | Description |
|---|---|---|---|
| estimated_delivery_days | object | – | – |
| message | string | yes | – |
| next_step | string | – | – |
| order_ref | string | – | – |
| policy | string | – | – |
| request_id | number | – | – |
| status | string | yes | – |
| swatch_count | number | – | – |
No examples provided.
search_catalog ~78
Preferred free-text discovery. Returns results containing product_id, name, category, description, product_url and colour_count_in_stock, plus total and currency. For structured filters use lookup_catalog. Pass product_id to get_product or get_price.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Free-text query, e.g. 'blockout' or 'venetian' |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| results | array | yes | – |
| total | number | yes | – |
No examples provided.
search_products ~180
Legacy discovery, retained for backward compatibility. Prefer search_catalog / lookup_catalog, then get_product. Filters by blind type, colour or maximum dimensions. Returns products with id (not product_id), name, description, features and in-stock colour count. Pass that id as product_id to get_price or configure_product.
| Name | Type | Req | Description |
|---|---|---|---|
| colour | string | – | Colour name to search for (partial match) |
| max_height_mm | number | – | Maximum height/drop in millimetres the product supports |
| max_width_mm | number | – | Maximum width in millimetres the product supports |
| province | string | – | Optional. Customer's South African province or city. Garden Route locations get Duncan's direct contact; other locations get the online shop contact. |
| type | string | – | Blind category to filter by: roller, venetian, honeycomb, vertical, outdoor |
| Name | Type | Req | Description |
|---|---|---|---|
| contact | object | – | – |
| currency | string | – | – |
| products | array | yes | – |
| total | number | yes | – |
No examples provided.
submit_enquiry ~146
Legacy auth-required tool, prefer the open UCP flow (create_cart → create_checkout → complete_checkout) for credentialless checkout. Use submit_enquiry only when the customer wants a sales team follow-up by email rather than paying online. Requires Bearer token. Pass a configure_product output plus customer name, email, and phone. Team responds within 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | Customer email address |
| customer_name | string | yes | Customer full name |
| customer_phone | string | yes | Customer phone number |
| message | string | yes | Required enquiry message; at least 10 characters after trimming |
| product_config | object | yes | Product configuration from configure_product |
| Name | Type | Req | Description |
|---|---|---|---|
| contact | object | yes | – |
| message | string | yes | – |
| success | boolean | yes | – |
No examples provided.
update_cart ~135
Modify an open cart before checkout. op: 'add' appends items, 'remove' drops items by 0-based index, 'set' replaces the full item list, 'clear' empties the cart. Merges customer details (name, email, phone) via the customer field. Call get_cart afterwards to confirm. Cannot modify a cart that already has a checkout in progress.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | – |
| customer | object | – | – |
| indices | array | – | Item indices to remove (0-based) when op='remove' |
| items | array | – | – |
| op | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | – |
| created_at | string | yes | – |
| currency | string | yes | – |
| customer | – | yes | – |
| expires_at | string | yes | – |
| item_count | number | yes | – |
| items | array | yes | – |
| total_zar | number | yes | – |
| updated_at | string | yes | – |
No examples provided.
update_checkout ~69
Update customer details or payment_method only before payment-link generation. Paid, cancelled and payment-in-progress checkouts are rejected. Concurrent state changes are detected; retrieve the latest status before retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | – |
| customer | object | – | – |
| payment_method | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| ap2 | object | – | – |
| checkout_id | string | yes | – |
| currency | string | yes | – |
| customer | object | – | – |
| item_count | number | – | – |
| items | – | – | – |
| message | string | – | – |
| next_step | string | – | – |
| payment_method | – | – | – |
| payment_url | – | – | – |
| provider_reference | – | – | – |
| status | – | yes | – |
| total_zar | number | yes | – |
No examples provided.
How do I install the Custom Blinds Shop MCP server?
Custom Blinds Shop is a hosted endpoint at https://shop.customblinds.co.za/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 · shop.customblinds.co.za
claude mcp add --transport http customblinds-cb-shop 'https://shop.customblinds.co.za/mcp'
What is the Custom Blinds Shop MCP server?
Custom Blinds Shop is an MCP server listed in the public MCP registry as io.github.CustomBlinds/cb-shop. South Africa's first AI-transactable blinds, shutters and awnings catalogue with live ZAR pricing. This page covers its hosted endpoint (https://shop.customblinds.co.za/mcp).
Is the Custom Blinds Shop MCP server safe to use?
Custom Blinds Shop scores 76 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 Custom Blinds Shop MCP server expose?
Custom Blinds Shop exposes 26 tools: search_products, get_price, configure_product, submit_enquiry, create_order, and 21 more. Their descriptions and schemas cost roughly 3,523 tokens of context every time the server is loaded.
Does the Custom Blinds Shop MCP server require authentication?
No. We connected to Custom Blinds Shop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Custom Blinds Shop MCP server still maintained?
Custom Blinds Shop 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.
What did VerifyMCP test on the Custom Blinds Shop MCP server?
VerifyMCP ran 13 checks on Custom Blinds Shop, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.