KitchenWatt (US)
REMOTE · KITCHENWATT.COM
Search, filter and compare food processors in KitchenWatt's catalogue, with links to each page.
Available components
Last scanned (23 hours ago)
Scores higher than 62% 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 Security91
- 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, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 754 tokens (~107/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management6
- Stability check failed: schema churn in the 13 days we've observed: 0 tool removals, 5 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 6.
- 9 Nov 26 +3
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compare_models” rewrote its description, which is the text the model reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Tool “get_model” rewrote its description, which is the text the model reads security
- Tool “list_filters” rewrote its description, which is the text the model reads security
- Tool “list_guides” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Tool “search_models” rewrote its description, which is the text the model reads security
- Schema quality: 50 → 107 ▼ functional
- “compare_models” added a required parameter “market”, so existing callers break ▼ functional
- “get_model” added a required parameter “market”, so existing callers break ▼ functional
- “list_filters” added a required parameter “market”, so existing callers break ▼ functional
- “list_guides” added a required parameter “market”, so existing callers break ▼ functional
- “search_models” added a required parameter “market”, so existing callers break ▼ functional
- Tool coverage: 29% → 64% ▲ functional
- Schema quality: fair → good functional
- “fetch” added an optional parameter “market” cosmetic
- “search” added an optional parameter “market” cosmetic
- “search_models” reworded the description of “filters” cosmetic
- 8 Nov 26 71
First indexed and scored.
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://kitchenwatt.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kitchenwatt.com | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2cf98eaa2c689ca11343721e0bebdb42 |
| SANs: kitchenwatt.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 kitchenwatt.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| kitchenwatt.com. | 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://kitchenwatt.com/mcp | Verified | 200 | |
| http (plaintext) | http://kitchenwatt.com/mcp | HTTPS enforced | 301 | https://kitchenwatt.com/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 →
compare_models Compare models ~80
Compare 2 to 4 food processors from KitchenWatt's comparison (slugs) side by side on the same criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | The market: us = the United States (Amazon.com, in English), fr = France (Amazon.fr, in French). Each market has its own catalog. |
| slugs | array | yes | – |
No output schema declared.
No examples provided.
fetch Fetch a model ~85
The full content of one of KitchenWatt's food processors (an id returned by search): our data, its filter values, its official data and its address.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| market | string | – | The market: us = the United States (Amazon.com, in English), fr = France (Amazon.fr, in French). Each market has its own catalog. |
No output schema declared.
No examples provided.
get_model Get a model ~80
All the data of one of the food processors in KitchenWatt's comparison (by its slug) and the link to its page.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | The market: us = the United States (Amazon.com, in English), fr = France (Amazon.fr, in French). Each market has its own catalog. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_filters List filters ~73
The filters of KitchenWatt's food processors comparison: key, label, possible values or range and unit, and what each means.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | The market: us = the United States (Amazon.com, in English), fr = France (Amazon.fr, in French). Each market has its own catalog. |
No output schema declared.
No examples provided.
list_guides List buying guides ~61
KitchenWatt's buying guides for food processors, with their address.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | The market: us = the United States (Amazon.com, in English), fr = France (Amazon.fr, in French). Each market has its own catalog. |
No output schema declared.
No examples provided.
search Search ~96
Search the food processors in KitchenWatt's comparison, for the United States (Amazon.com, in English) or France (Amazon.fr, in French) (free text); returns each one's id, title and address.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | The market: us = the United States (Amazon.com, in English), fr = France (Amazon.fr, in French). Each market has its own catalog. |
| query | string | yes | – |
No output schema declared.
No examples provided.
search_models Search models ~180
Search the food processors in KitchenWatt's comparison, for the United States (Amazon.com, in English) or France (Amazon.fr, in French), by need (free text) and exact filters; returns name, brand, filter values, official data with its source and the link to the model's page on the site (today's price and ratings are there).
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | {key: [exact values]} or {key: {min, max}}, using the keys and values of the comparison's filters |
| limit | integer | – | – |
| market | string | yes | The market: us = the United States (Amazon.com, in English), fr = France (Amazon.fr, in French). Each market has its own catalog. |
| query | string | – | Need in plain words (e.g. "quiet for a studio") |
No output schema declared.
No examples provided.
How do I install the KitchenWatt (US) MCP server?
KitchenWatt (US) is a hosted endpoint at https://kitchenwatt.com/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 · kitchenwatt.com
claude mcp add --transport http com-kitchenwatt-food-processors 'https://kitchenwatt.com/mcp'
What is the KitchenWatt (US) MCP server?
KitchenWatt (US) is an MCP server listed in the public MCP registry as com.kitchenwatt/food-processors. Search, filter and compare food processors in KitchenWatt's catalogue, with links to each page. This page covers its hosted endpoint (https://kitchenwatt.com/mcp).
Is the KitchenWatt (US) MCP server safe to use?
KitchenWatt (US) scores 75 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 KitchenWatt (US) MCP server expose?
KitchenWatt (US) exposes 7 tools: search_models, get_model, compare_models, list_filters, list_guides, and 2 more. Their descriptions and schemas cost roughly 655 tokens of context every time the server is loaded.
Does the KitchenWatt (US) MCP server require authentication?
No. We connected to KitchenWatt (US) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the KitchenWatt (US) MCP server still maintained?
KitchenWatt (US) 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 KitchenWatt (US) MCP server?
VerifyMCP ran 13 checks on KitchenWatt (US), 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.