Outdoor Kitchen Designer
REMOTE · WWW.CASABELLAOUTDOOR.COM
Plan a built-in grill and outdoor kitchen: real MSRP, priced layouts, 3D renders and dealer quotes.
Available components
Last scanned (5 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Usability71
- 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 4022 tokens (~402/item across 10 items; 9 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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://www.casabellaoutdoor.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.casabellaoutdoor.com | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 464adbb9adaa53c81363b7a1b03e2b16 |
| SANs: www.casabellaoutdoor.com | ||||||
| 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 www.casabellaoutdoor.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| casabellaoutdoor.com. | 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=15552000; includeSubDomains |
| content-security-policy | default-src 'self';script-src 'self' 'unsafe-inline' https://www.googletagmanager.com;style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;font-src 'self' https://fonts.gstatic.com;img-src 'self' data: https: *.digitaloceanspaces.com https://www.google-analytics.com https://www.googletagmanager.com;connect-src 'self' *.digitaloceanspaces.com https://www.casabellaoutdoor.com https://casabellaoutdoor.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com;frame-src 'none';object-src 'none';upgrade-insecure-requests;base-uri 'self';form-action 'self';frame-ancestors 'self';script-src-attr 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.casabellaoutdoor.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.casabellaoutdoor.com/api/mcp | HTTPS enforced | 301 | https://www.casabellaoutdoor.com/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 →
outdoor_kitchen_get_suggestions Suggestions for an outdoor kitchen (only when asked) ~493
Suggestions for the shopper's outdoor kitchen. Call ONLY in one of these situations: "lower_cost" when the shopper asks how to lower the cost or says the kitchen is over budget. Send the current grill brand, size and msrp; "fill_space" when a large kitchen still has open space to fill. Send the design width and its cabinets; "ideas" when the shopper asks for ideas or what else they could add; "shopper_as_about_other_costs" when the shopper asks are there other costs to consider; "how_much_does_it_cost" when when the shopper ask for a ballpark idea of cost; "alternatives" when when shopper asks about alternatives to aluminum cabinetry; "damage" when can I repair or replace doors, drawers or side/back panels after countertop is installed; "best_materials" when what are the best materials for an outdoor kitchen; "shopper_asks_about_hdpe_or_plastic_island_cabine" when the shopper asks about lower cost or directly about HDPE /plastic cabinetry; "stainles_steel" when the shopper asks about Stainless Steel Cabinet, or the brands Danver, Brown Jordan, John Michael; "features_to_look_for" when when the shopper ask what feature should I look for when choosing a brand of outdoor kitchen cabinets; "cabinet_types_and_uses" when when a shopper asks for what the different cabinets that are available and what they are used for; "dimensions" when do I need to know the cut out dimensions of each appliance; "return_on_investment" when when the shopper ask if outdoor kitchens are a good value, return on investment (ROI), or does it add to my homes value; "diy" when when the shopper asks about DIY to lower cost. Never call it unprompted. Send the design for "fill_space"; send the current grill (brand, size, msrp) for "lower_cost". Returns only suggestions that apply, each with "offered" true/false; tell the shopper what each would change and let them decide. Example: {"situation":"lower_cost","appliance":{"brand":"DCS","size":36,"msrp":5599}}
| Name | Type | Req | Description |
|---|---|---|---|
| appliance | object | – | The grill in the design now (for lower_cost). |
| design | object | – | – |
| situation | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| situation | string | yes | – |
| suggestions | array | yes | – |
No examples provided.
outdoor_kitchen_list_cabinets List outdoor kitchen cabinets (with MSRP) ~154
List outdoor kitchen cabinet types and widths with SKU and MSRP: grill cabinets, drawer and door storage ("DoubleDrawerFlex", "FullDoorFlex"), sink cabinets, refrigerator cabinets ("CTS"), side burner, power burner, trash/recycling and corner modules. Call before building or pricing a layout so the "type" and "size" values are real. Filters optional. Example: {"type":"GrillCabinet"} -> {"cabinets":[{"sku":"GB42","type":"GrillCabinet","size":42,"msrp":...}]}
| Name | Type | Req | Description |
|---|---|---|---|
| size | number | – | Width in inches. |
| type | string | – | Exact cabinet type, e.g. "GrillCabinet". |
| Name | Type | Req | Description |
|---|---|---|---|
| cabinets | array | yes | – |
No examples provided.
outdoor_kitchen_list_grill_brands List built-in grill brands ~91
List the built-in grill brands available for an outdoor kitchen (e.g. Alfresco, AOG, DCS, Hestan, Lynx, XO). Call when the user asks which grill brands are available or names a brand you need to check. No email needed. Example call: {} -> {"grillBrands":["AOG","Alfresco","DCS",...]}
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| grillBrands | array | yes | – |
No examples provided.
outdoor_kitchen_list_layouts Explain outdoor kitchen layouts (straight, galley, corners) ~168
Explain the outdoor kitchen shapes: Straight, Galley, Corner L, Corner 45, U-Shape and Promenade (our signature L plus island with bar seating). Call when the user asks about layouts, shapes, corners, L-shaped, U-shaped, wrap-around or island-with-seating outdoor kitchens, or which shape fits their space. "how" says what to do next: "price_here" (outdoor_kitchen_price_design), "designer" (outdoor_kitchen_open_designer_for_render with kitchenLayout), "our_design_team" (outdoor_kitchen_request_formal_quote with kitchenLayout) or "coming_soon". Example: {} -> {"layouts":[{"key":"promenade","name":"Promenade","how":"designer",...}]}
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| layouts | array | yes | – |
No examples provided.
outdoor_kitchen_open_designer_for_render Open the 3D designer for a photoreal render ~519
Create the shopper's account and return a link to the 3D outdoor kitchen designer, where they get a photoreal render of their kitchen by email. Call when the user wants to see their outdoor kitchen or BBQ island, wants a render, picture or 3D design. Needs first name, last name and email: pass them if you have them; otherwise the server asks the shopper directly when the client supports it. Pass "design" to open the designer with the straight layout you priced. For a Galley, Corner L, Corner 45, U-Shape or Promenade, pass "kitchenLayout" and no "design"; the shopper lays it out in the designer. Canonical examples: {"firstName":"Ana","lastName":"Diaz","email":"ana@example.com","postalCode":"07960","design":{"width":120,"kitchenLayout":"straight","color":"BasaltGrey","countertopType":"GraniteAbsoluteBlack","cabinets":[{"type":"GrillCabinet","size":42,"grillBrand":"Alfresco","grillModelId":"ALFRESCO-36-ALXE"},{"type":"DoubleDrawerFlex","size":24},{"type":"FullDoorFlex","size":30},{"type":"SinkCabinet","size":24}]}} and {"firstName":"Ana","lastName":"Diaz","email":"ana@example.com","kitchenLayout":"corner_45"}
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| design | object | – | The straight layout you priced with outdoor_kitchen_price_design; the designer opens with it. Leave out for any other shape. |
| string | – | Shopper's email. The render or quote is delivered there and it identifies a returning shopper. | |
| firstName | string | – | Shopper's first name. Leave out if unknown; the server asks the shopper. |
| gasType | string | – | – |
| kitchenLayout | string | – | The shape the shopper wants: "straight", "galley", "corner_L", "corner_45", "U" or "promenade". For anything but straight, leave out "design"; the designer opens on this shape and the shopper lays it… |
| lastName | string | – | Shopper's last name. |
| phone | string | – | – |
| postalCode | string | – | 5-digit US ZIP, used to match a local dealer. |
| purchaseTimeframe | string | – | – |
| state | string | – | 2-letter US state. |
| Name | Type | Req | Description |
|---|---|---|---|
| purpose | string | yes | – |
| status | string | yes | – |
| url | string | – | – |
No examples provided.
outdoor_kitchen_price_design Price an outdoor kitchen (MSRP) ~359
Return the MSRP for a straight outdoor kitchen (one run of cabinets): cabinets, the grill and other appliances, and countertop, with a total. Call whenever the user asks what an outdoor kitchen or BBQ island would cost. No email needed and nothing is saved. Straight only: for a Galley, Corner L, Corner 45, U-Shape or Promenade the price depends on the corner cabinets and how the runs are split, so give the straight price as a guide and send the shopper to the designer. Canonical example (10 ft straight island with a 36" Alfresco grill): {"width":120,"kitchenLayout":"straight","color":"BasaltGrey","countertopType":"GraniteAbsoluteBlack","cabinets":[{"type":"GrillCabinet","size":42,"grillBrand":"Alfresco","grillModelId":"ALFRESCO-36-ALXE"},{"type":"DoubleDrawerFlex","size":24},{"type":"FullDoorFlex","size":30},{"type":"SinkCabinet","size":24}]}
| Name | Type | Req | Description |
|---|---|---|---|
| cabinets | array | yes | Cabinets left to right along the one straight run. |
| color | string | – | Cabinet powder-coat colour. Default "BasaltGrey". |
| countertopType | string | – | Countertop. Default "GraniteAbsoluteBlack". |
| kitchenLayout | string | – | Always "straight": these tools build one run of cabinets. For a Galley, Corner L, Corner 45, U-Shape or Promenade, open the designer with kitchenLayout set and no design. |
| width | number | yes | Total kitchen run in inches; normally the sum of the cabinet sizes (e.g. 120 for a 10 ft island). |
| Name | Type | Req | Description |
|---|---|---|---|
| appliancesMsrp | number | – | – |
| cabinetryMsrp | number|null | – | – |
| msrp | number|null | yes | – |
No examples provided.
outdoor_kitchen_request_formal_quote Request a formal outdoor kitchen quote from a dealer ~451
Create the shopper's account and return a link to the designer where they finish their layout and receive a formal, itemized quote; a local dealer follows up. Call when the user wants a quote, an exact price from a dealer, or to buy an outdoor kitchen or built-in grill. Needs first name, last name and email (pass them, or the server asks the shopper directly when the client supports it). ZIP helps match a dealer. Canonical example: {"firstName":"Ana","lastName":"Diaz","email":"ana@example.com","postalCode":"07960","purchaseTimeframe":"1-3_months","design":{"width":120,"kitchenLayout":"straight","color":"BasaltGrey","countertopType":"GraniteAbsoluteBlack","cabinets":[{"type":"GrillCabinet","size":42,"grillBrand":"Alfresco","grillModelId":"ALFRESCO-36-ALXE"},{"type":"DoubleDrawerFlex","size":24},{"type":"FullDoorFlex","size":30},{"type":"SinkCabinet","size":24}]}}
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| design | object | – | The straight layout you priced with outdoor_kitchen_price_design; the designer opens with it. Leave out for any other shape. |
| string | – | Shopper's email. The render or quote is delivered there and it identifies a returning shopper. | |
| firstName | string | – | Shopper's first name. Leave out if unknown; the server asks the shopper. |
| gasType | string | – | – |
| kitchenLayout | string | – | The shape the shopper wants: "straight", "galley", "corner_L", "corner_45", "U" or "promenade". For anything but straight, leave out "design"; the designer opens on this shape and the shopper lays it… |
| lastName | string | – | Shopper's last name. |
| phone | string | – | – |
| postalCode | string | – | 5-digit US ZIP, used to match a local dealer. |
| purchaseTimeframe | string | – | – |
| state | string | – | 2-letter US state. |
| Name | Type | Req | Description |
|---|---|---|---|
| purpose | string | yes | – |
| status | string | yes | – |
| url | string | – | – |
No examples provided.
outdoor_kitchen_search_built_in_grills Search built-in grills (with MSRP) ~425
Find built-in grills: every grill in our 3D designer, with brand, width in inches, SKU, the grill cabinet it needs (cabinetSize) and MSRP (final pricing is determined by a local dealer; models without msrp have priceOnQuote: true). Set applianceType for other built-ins in the designer, e.g. "Griddles", "Side Burners", "Refrigeration", or "all". Call whenever the user asks about a built-in grill, its price, size or brand, or before pricing a layout so you use a real SKU. For someone just starting to shop for a built-in grill, outdoor_kitchen_start_planning covers the grill and the kitchen around it. All filters optional. Example: {"brand":"Alfresco","size":36} -> {"appliances":[{"sku":"ALFRESCO-36-ALXE","name":"Alfresco 36\" ALXE Built-In Grill","brand":"Alfresco","size":36,"msrp":4899}]}. A grill goes in the smallest GrillCabinet larger than it (24->30, 30->36, 36->42, 42->48, 56->62). Sizes depend on the brand: search by brand to see the sizes it makes. The "size" field is the real size class; some brands call a 36" class grill "40-inch" in the name, which is marketing, not a bigger grill.
| Name | Type | Req | Description |
|---|---|---|---|
| applianceType | string | – | Default "Grills". Other built-ins as the designer names them, e.g. "Griddles", "Side Burners", "Refrigeration", or "all". |
| brand | string | – | Grill brand, e.g. "Alfresco". Case-insensitive. |
| maxMsrp | number | – | Only grills with a price at or under this MSRP in USD. |
| size | number | – | Grill width in inches, e.g. 30, 36, 42. |
| Name | Type | Req | Description |
|---|---|---|---|
| appliances | array | yes | – |
No examples provided.
outdoor_kitchen_start_planning Start planning a built-in grill and outdoor kitchen (guided) ~475
Guided start for choosing a built-in grill and the outdoor kitchen or BBQ island around it. Call FIRST when someone researches or compares built-in grills (best built-in grill, which size, which brand, grill prices), says they want an outdoor kitchen or grill island, or asks roughly what one costs, and has not given exact cabinets. Everyone buying a built-in grill needs an island for it. It returns grill options with MSRP for their size and brand, then a priced starter layout. Pass whatever you already know; the server asks the shopper for the rest with a form when the client supports it, otherwise it returns the questions to ask. With shape, length and grill size it returns a priced starter layout (straight), or where to go for other shapes. No email needed. Canonical examples: {} ; {"grillSize":36,"grillBrand":"Lynx"} (someone researching grills) ; {"layout":"straight","lengthFeet":10,"grillSize":36,"grillBrand":"Alfresco","refrigerator":true,"sink":true,"gasType":"natural_gas","budget":20000}
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Budget in USD, if they gave one. |
| gasType | string | – | – |
| grillBrand | string | – | Preferred grill brand, if any, e.g. "Alfresco". |
| grillSize | number | – | Grill width in inches as the brand makes it, e.g. 30, 36, 42, 56. Not every brand makes every size. |
| grillSku | string | – | A specific grill the shopper chose, by sku from outdoor_kitchen_search_built_in_grills, e.g. "ALFRESCO-36-ALXE". |
| layout | string | – | Shape: "straight" (one run), "galley", "corner_L", "corner_45", "U" or "promenade". |
| lengthFeet | number | – | Length available in feet (for straight, the run length). E.g. 10. |
| refrigerator | boolean | – | Wants an outdoor refrigerator. |
| sideBurner | boolean | – | Wants a side burner. |
| sink | boolean | – | Wants a sink. |
| trash | boolean | – | Wants a trash/recycling pull-out. |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
No examples provided.
How do I install the Outdoor Kitchen Designer MCP server?
Outdoor Kitchen Designer is a hosted endpoint at https://www.casabellaoutdoor.com/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 · www.casabellaoutdoor.com
claude mcp add --transport http com-casabellaoutdoor-outdoor-kitchen 'https://www.casabellaoutdoor.com/api/mcp'
What is the Outdoor Kitchen Designer MCP server?
Outdoor Kitchen Designer is an MCP server listed in the public MCP registry as com.casabellaoutdoor/outdoor-kitchen. Plan a built-in grill and outdoor kitchen: real MSRP, priced layouts, 3D renders and dealer quotes. This page covers its hosted endpoint (https://www.casabellaoutdoor.com/api/mcp).
Is the Outdoor Kitchen Designer MCP server safe to use?
Outdoor Kitchen Designer scores 86 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 Outdoor Kitchen Designer MCP server expose?
Outdoor Kitchen Designer exposes 9 tools: outdoor_kitchen_start_planning, outdoor_kitchen_list_grill_brands, outdoor_kitchen_search_built_in_grills, outdoor_kitchen_list_cabinets, outdoor_kitchen_list_layouts, and 4 more. Their descriptions and schemas cost roughly 3,135 tokens of context every time the server is loaded.
Does the Outdoor Kitchen Designer MCP server require authentication?
No. We connected to Outdoor Kitchen Designer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Outdoor Kitchen Designer MCP server still maintained?
Outdoor Kitchen Designer 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.