# Sienna, Knobs.co hardware advisor (remote · sienna.knobs.co)

Knobs.co cabinet-hardware advisor: sizing, fits, finishes, prices, plans, cart and sample links.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `sienna.knobs.co`: 73/100 (this document), [markdown](https://verifymcp.io/servers/co-knobs-sienna/sienna.md), [page](https://verifymcp.io/servers/co-knobs-sienna/sienna)

## Channel facts

- Endpoint: `https://sienna.knobs.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.2`

## 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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1784 tokens (~162/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Sienna, Knobs.co hardware advisor MCP server?

Sienna, Knobs.co hardware advisor is a hosted endpoint at https://sienna.knobs.co/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 co-knobs-sienna 'https://sienna.knobs.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-knobs-sienna": {
      "url": "https://sienna.knobs.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-knobs-sienna": {
      "type": "http",
      "url": "https://sienna.knobs.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-knobs-sienna]
url = "https://sienna.knobs.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-knobs-sienna": {
      "type": "remote",
      "url": "https://sienna.knobs.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-knobs-sienna --url 'https://sienna.knobs.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-knobs-sienna:
    url: "https://sienna.knobs.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-knobs-sienna": {
      "Transport": "http",
      "Url": "https://sienna.knobs.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-knobs-sienna -t streamable-http -u 'https://sienna.knobs.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-knobs-sienna": {
      "type": "http",
      "url": "https://sienna.knobs.co/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-21 (score 73, +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-11-20 (score 72, 0)

- [security] Tool “start_samples” rewrote its description, which is the text the model reads

### 2026-11-19 (score 72, +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-11-17 (score 71, +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-11-14 (score 70, +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.

### 2026-11-12 (score 69, +1)

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

### 2026-11-10 (score 68, +1)

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

### 2026-11-08 (score 67, +1)

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

## MCP tools (11)

### `ask_sienna` (~148 tokens)

Ask Sienna (Knobs.co hardware advisor)

Ask Knobs.co's automated cabinet-hardware advisor one question in plain words and get one complete answer with the exact products named (title, vendor, finish, size, list price, URL). Best for: which pull length for a drawer width, what fits existing holes (center-to-center), knobs versus pulls, finish and style pairing, a series in a size/finish/budget, samples, returns, the trade program. Include everything known: room, drawer widths, existing hole spacing, finish, style, budget per piece, brand likes or dislikes. One question per call; up to 600 characters.

Input parameters:

- `question` (string, required): The shopper's question, with what is known.

### `search_catalog` (~112 tokens)

Search the Knobs.co catalog

Search the live Knobs.co catalog by item type, size, finish, brand or series ("5 inch pull satin nickel", "Top Knobs Lynwood", "3 inch matte black pull"). Returns up to 10 products with vendor, center-to-center size, overall length, finishes, list prices, variant ids and product URLs. Sizes and finishes in the query are matched exactly when possible, then nearest sizes.

Input parameters:

- `query` (string, required): Plain words: item type + size + finish, or brand + series.

### `get_product` (~79 tokens)

Get one Knobs.co product

Every variant (finish, SKU, list price, variant id) of one product by its handle (from search_catalog or a knobs.co/products/<handle> URL), with sizes and description.

Input parameters:

- `handle` (string, required): The product handle, e.g. "atlas-homewares-a656-whittier-pull-8-13-16-cc".

### `sizing_guide` (~50 tokens)

Cabinet hardware sizing guide

Knobs.co's sizing rules: which pull length for which drawer width, the standard 128 mm size, knobs versus pulls, one pull or two, and how to measure existing holes. No arguments.

### `store_info` (~42 tokens)

About Knobs.co for agents

What Knobs.co is, what it sells, how to buy, samples, trade program, how to reach a person, and how this service works. No arguments.

### `search` (~65 tokens)

Search (connector convention)

Search Knobs.co products. Returns {results:[{id,title,url}]} where id is the product handle for fetch.

Input parameters:

- `query` (string, required): Plain-words product search: item type, size, finish, brand or series (e.g. "3 inch matte black pull").

### `fetch` (~50 tokens)

Fetch (connector convention)

Fetch one Knobs.co product document by id (the handle from search). Returns {id,title,text,url,metadata}.

Input parameters:

- `id` (string, required): The product id returned by search (the knobs.co product handle).

### `build_plan` (~306 tokens)

Build a Hardware Plan (Knobs.co)

Build the shopper's whole-kitchen (or bath) Hardware Plan: one line per zone (doors, drawers by width, island, tall, appliance panels) with the exact Knobs.co product, finish, size, count and list price, totals, the pieces that qualify as samples, and what is still unconfirmed. Use it once the shopper has given counts, drilling (existing holes or fresh), finish, style and a budget; include products they liked from search_catalog as candidates. The plan is saved for 90 days at the returned plan_url, where the shopper can see it and add its samples or the whole plan to their cart. To change counts, finish or products, call build_plan again with the corrected answers; for Kayla's review, request_consultation with the plan_url. No email or account needed. Costs real money on our side, so call it once per shopper, after the facts are gathered.

Input parameters:

- `answers` (object, required): What the shopper has told the agent about the project. Every field is optional, but the plan needs at least the counts, the drilling situation and the finish.
- `candidates` (array): products the shopper liked or the agent found with search_catalog (handle + variant_id in the right finish), optionally with the zone and count they are for
- `summary` (string): two to six sentences of what the shopper told you, in their words where possible (shown to Kayla if they later ask for a review)

### `cart_link` (~145 tokens)

Cart link (Knobs.co checkout)

Turn chosen variants and quantities into a Knobs.co cart link the shopper opens to check out (the cart is pre-filled; they review it, add shipping and pay on knobs.co; nothing is ordered by this call). Variant ids come from search_catalog, get_product or build_plan. Returns the line items with list prices and the subtotal, so you can show the shopper exactly what the cart holds.

Input parameters:

- `items` (array, required): the variants and quantities to pre-fill in the cart
- `note` (string): an optional note for the order (shown to our team)
- `plan_url` (string): the plan_url from build_plan, if this cart comes from a plan

### `start_samples` (~166 tokens)

Samples cart (Knobs.co)

Pick the pieces that qualify as samples (listed at $20 or under, under 7 inches overall, not a made-to-order line) from a plan or from given variant ids, and return a cart link with one of each plus the sample terms. Samples are bought at the normal price and the shopper keeps them. Samples are credited only on a qualifying order (20 or more of the same item); the returned sample terms give the policy link. Never promise a credit on a smaller order. Pieces that do not qualify are returned with the reason.

Input parameters:

- `plan_url` (string): the plan_url from build_plan: samples are taken from that plan
- `variant_ids` (array): or specific variant ids to check for sample eligibility (give plan_url or variant_ids, not both)

### `request_consultation` (~274 tokens)

Ask Kayla to review or call (Knobs.co)

Ask Kayla, Knobs.co's Trade Manager (twenty years in cabinet hardware), to review the shopper's plan by email within one business day, or to set up a call. Only with the shopper's email and their clear agreement to be contacted. This sends the shopper ONE email with a confirmation link; Kayla receives the request only after they click it (within 7 days), so tell the shopper to look for an email from cs@knobs.co and confirm. Include the plan_url from build_plan when there is one, and say in message what they want Kayla to do.

Input parameters:

- `email` (string, required): the shopper's email, given by them for this purpose
- `kind` (string): review = Kayla reviews the plan and emails back; call = Kayla sets up a call (the confirmation page opens her calendar)
- `message` (string, required): what the shopper wants from Kayla, in their words, plus anything she needs to know (no links)
- `name` (string): the shopper's name as they gave it (first name is enough)
- `phone` (string): phone number, only if the shopper offered it (useful when kind is "call")
- `plan_url` (string): the plan_url from build_plan, when there is a plan

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-knobs-sienna/sienna#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 70
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 69
- 2026-11-12: 69
- 2026-11-11: 68
- 2026-11-10: 68
- 2026-11-09: 67
- 2026-11-08: 67
- 2026-11-07: 66
- 2026-11-06: 65

## Common questions

### What is the Sienna, Knobs.co hardware advisor MCP server?

Sienna, Knobs.co hardware advisor is an MCP server listed in the public MCP registry as co.knobs/sienna. Knobs.co cabinet-hardware advisor: sizing, fits, finishes, prices, plans, cart and sample links. This page covers its hosted endpoint (https://sienna.knobs.co/mcp).

### Is the Sienna, Knobs.co hardware advisor MCP server safe to use?

Sienna, Knobs.co hardware advisor scores 73 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 Sienna, Knobs.co hardware advisor MCP server expose?

Sienna, Knobs.co hardware advisor exposes 11 tools: ask_sienna, search_catalog, get_product, sizing_guide, store_info, and 6 more. Their descriptions and schemas cost roughly 1,437 tokens of context every time the server is loaded.

### Does the Sienna, Knobs.co hardware advisor MCP server require authentication?

No. We connected to Sienna, Knobs.co hardware advisor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sienna, Knobs.co hardware advisor MCP server still maintained?

Sienna, Knobs.co hardware advisor is still listed as active in the MCP registry. We last reached this channel on 21 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 Sienna, Knobs.co hardware advisor MCP server?

VerifyMCP ran 12 checks on Sienna, Knobs.co hardware advisor, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Sienna, Knobs.co hardware advisor: HTTPS. 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.

## Links

- Remote endpoint: https://sienna.knobs.co/mcp
- Website: https://knobs.co/pages/agents
- Changelog RSS feed: https://verifymcp.io/servers/co-knobs-sienna/sienna.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-knobs-sienna/sienna/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-knobs-sienna/sienna.json
- HTML version of this page: https://verifymcp.io/servers/co-knobs-sienna/sienna
