Sienna, Knobs.co hardware advisor
REMOTE · SIENNA.KNOBS.CO
Knobs.co cabinet-hardware advisor: sizing, fits, finishes, prices, plans, cart and sample links.
Available components
Last scanned (22 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 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 Security63
- 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. 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 21 Nov 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.
- 20 Nov 26 0
- Tool “start_samples” rewrote its description, which is the text the model reads security
- 19 Nov 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.
- 17 Nov 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.
- 14 Nov 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.
- 12 Nov 26 +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.
- 10 Nov 26 +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.
- 8 Nov 26 +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.
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 21 Nov 2026 · Probed https://sienna.knobs.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=knobs.co | CN=WE1,O=Google Trust Services,C=US | 6 Nov 2026 | 4 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 86d1d332eec94069139e3b867d40ec29 |
| SANs: knobs.co, sienna.knobs.co, *.sienna.knobs.co | ||||||
| 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 sienna.knobs.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| knobs.co. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sienna.knobs.co/mcp | Verified | 200 | |
| http (plaintext) | http://sienna.knobs.co/mcp | Inconclusive | 405 |
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 →
ask_sienna Ask Sienna (Knobs.co hardware advisor) ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The shopper's question, with what is known. |
No output schema declared.
No examples provided.
build_plan Build a Hardware Plan (Knobs.co) ~306
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | 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) |
No output schema declared.
No examples provided.
cart_link Cart link (Knobs.co checkout) ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 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 |
No output schema declared.
No examples provided.
fetch Fetch (connector convention) ~50
Fetch one Knobs.co product document by id (the handle from search). Returns {id,title,text,url,metadata}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The product id returned by search (the knobs.co product handle). |
No output schema declared.
No examples provided.
get_product Get one Knobs.co product ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | The product handle, e.g. "atlas-homewares-a656-whittier-pull-8-13-16-cc". |
No output schema declared.
No examples provided.
request_consultation Ask Kayla to review or call (Knobs.co) ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
search Search (connector convention) ~65
Search Knobs.co products. Returns {results:[{id,title,url}]} where id is the product handle for fetch.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Plain-words product search: item type, size, finish, brand or series (e.g. "3 inch matte black pull"). |
No output schema declared.
No examples provided.
search_catalog Search the Knobs.co catalog ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Plain words: item type + size + finish, or brand + series. |
No output schema declared.
No examples provided.
sizing_guide Cabinet hardware sizing guide ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_samples Samples cart (Knobs.co) ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
store_info About Knobs.co for agents ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · sienna.knobs.co
claude mcp add --transport http co-knobs-sienna 'https://sienna.knobs.co/mcp'
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.