Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Hobart Warewash is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
trust score
7
downloads a day
local
runs on your machine
466
downloads in 30d
What it does
Unofficial MCP server for Hobart dishwashers: errors, temperatures, consumption, hygiene log.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'HOBART_USERNAME=${HOBART_USERNAME}' --env 'HOBART_PASSWORD=${HOBART_PASSWORD}' --transport stdio hobart-warewash-mcp '--' npx -y hobart-warewash-mcp
# 2 — ask your agent for something these tools do
# hobart_ping, hobart_list_machines, hobart_machine_overview and 5 more
It needs HOBART_USERNAME, HOBART_PASSWORD: this reads them from your environment, so export them first.
Hobart Warewash costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Hobart Warewash as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads HOBART_USERNAME (Hobart Cloud-to-Cloud API account (e-mail)), HOBART_PASSWORD (Hobart Cloud-to-Cloud API password) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx HOBART_USERNAME …, setx HOBART_PASSWORD … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'HOBART_USERNAME=${HOBART_USERNAME}' --env 'HOBART_PASSWORD=${HOBART_PASSWORD}' --transport stdio hobart-warewash-mcp '--' npx -y hobart-warewash-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: HOBART_USERNAME — Hobart Cloud-to-Cloud API account (e-mail).; HOBART_PASSWORD — Hobart Cloud-to-Cloud API password.. You set them in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Checks that the Hobart Cloud-to-Cloud API is reachable and that the configured account can sign in. Use it only when another tool fails and you need to know whether the problem is the connection.
No parameter schema on file.
Lists the Hobart dishwashers registered on this account: serial number, machine type, protocol version and the machine clock at last contact. Start here: every other tool needs a serial number.
No parameter schema on file.
One-call health check of a dishwasher: active errors, last wash/rinse temperatures and the daily consumption figures. Prefer this to calling the three detail tools separately when the question is "how is machine X doing".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| serial | string | yes | Machine serial number, as returned by hobart_list_machines. |
Daily data of a dishwasher: consumption (DailyWaterCons, DailyEnergyCons, DailyDetergentCons, DailyRinseAidCons), counters (C0xx codes) and the hygiene protocol (one entry per wash cycle, with its program code). Hobart refreshes this only after the machine is powered off or shortly before…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| serial | string | yes | Machine serial number, as returned by hobart_list_machines. |
Errors currently active on a dishwasher, with their code and since when. An empty list means no active error was reported, not that the machine is running. Hobart allows one real call every 30 seconds per machine; faster calls return the cached answer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| serial | string | yes | Machine serial number, as returned by hobart_list_machines. |
Wash tank (A270) and rinse (A283) temperatures in °C, and the last program run. Hobart allows one real call every 60 seconds per machine; faster calls return the cached answer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| serial | string | yes | Machine serial number, as returned by hobart_list_machines. |
Adds a dishwasher to this Hobart account using the 6-character registration code shown on the machine. Only call this when the person gives you the code and asks for the registration.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The 6-character registration code displayed by the machine. |
Changes settings on a dishwasher remotely. Only the fields you pass are changed. This acts on a real machine in a real kitchen: read the current values with hobart_get_machine_data, state the exact change (old → new) and get the person's explicit agreement before calling. Fails with…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| serial | string | yes | Machine serial number, as returned by hobart_list_machines. |
| detergentDosage | yes | — | |
| rinseAidDosage | yes | — | |
| detergentDensity | yes | — | |
| rinseAidDensity | yes | — | |
| autostartEnable | boolean | no | Autostart on/off (S078). |
| autostartTime1 | yes | — | |
| autostartTime2 | yes | — | |
| autostartTime3 | yes | — | |
| autostartTime4 | yes | — | |
| autostartTime5 | yes | — | |
| autostartTime6 | yes | — | |
| autostartTime7 | yes | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Hobart Warewash or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 96 / 100
Release 0.1.0 · scanned 3 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest462a63c78e4daeed2ecca88ec5069f93bdc67797fcaa46885685a8f1734fdbbc
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (8 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
2 of the 8 recovered tools are registered only when config.allowWrite holds (dist/server.js:127) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
6 tools are registered unconditionally · 2 more only when config.allowWrite holds (dist/server.js:127) — typically when a key or option is configured. All 8 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| hobart_ping | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| hobart_list_machines | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| hobart_machine_overview | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| hobart_get_machine_data | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| hobart_get_active_errors | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| hobart_get_temperatures | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| hobart_register_machine conditional | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| hobart_update_settings conditional | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest462a63c78e4daeed
Scanned2026-11-03
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Hobart Warewash can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.