Home / MCP registry index / com.casabellaoutdoor/outdoor-kitchen

Outdoor Kitchen Designer

com.casabellaoutdoor/outdoor-kitchen in the official MCP registry. Endpoint https://www.casabellaoutdoor.com/api/mcp.

The registry describes it as: Plan a built-in grill and outdoor kitchen: real MSRP, priced layouts, 3D renders and dealer quotes.

We read its 9 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

outdoor_kitchen_start_planning outdoor_kitchen_list_grill_brands outdoor_kitchen_search_built_in_grills outdoor_kitchen_list_cabinets outdoor_kitchen_list_layouts outdoor_kitchen_price_design outdoor_kitchen_get_suggestions outdoor_kitchen_open_designer_for_render outdoor_kitchen_request_formal_quote

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-casabellaoutdoor-outdoor-kitchen/badge.svg)](https://lazaretto.dev/mcp-registry/com-casabellaoutdoor-outdoor-kitchen)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.