Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Brewmark 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
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Grind settings for 200+ home coffee grinders, conversion between them, and help choosing one.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http brewmark-mcp https://brewmark.io/api/mcp
# 2 — ask your agent for something these tools do
# convert_grind_setting, get_grinder_chart, dial_in and 2 more
Brewmark costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BRAll 1 server
brewmark1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http brewmark-mcp https://brewmark.io/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 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.
Translate a grind setting from one coffee grinder to another. Use whenever a recipe quotes a setting for a grinder the user does not own — "the recipe says 18 clicks on a Comandante, what is that on my Encore?". Grinder names can be written however the user said them ("Fellow Ode", "1Zpresso J-Max"); exact slugs are not required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | The grinder the setting is quoted for, e.g. "Comandante C40 MK4" |
| setting | number/string | yes | The setting on the source grinder as written on it, e.g. 18. On Fellow dials the digit after the point counts marks (4.2 on an Ode is the second mark after 4); a Baratza Forte is macro number and micr |
| to | string | yes | The grinder to convert to, e.g. "Baratza Encore" |
Grind settings for one grinder across every brew method. Use this for any question of the form "what grind should I use for my <grinder>", "what setting for French press on a <grinder>", or "how do I dial in my <grinder>". Returns the recommended setting and usable range for espresso, moka pot, AeroPress, pour over, siphon, steep-and-release (Clever Dripper, Hario Switch), drip, cupping, Chemex, F
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grinder | string | yes | Grinder name as the user said it, e.g. "Fellow Ode", "Baratza Encore", or a slug |
| method | string | no | Optional brew method the user asked about, as they said it: "V60", "pour over", "French press", "espresso", "AeroPress", "cold brew", "Chemex", "drip", "moka pot", "siphon", "Clever Dripper", "cupping |
| roast | string | no | Optional roast level of the coffee the user is brewing. If they name a coffee rather than a roast ("Stumptown Hair Bender", "Lavazza Super Crema"), use what you know of it; leave out when unsure. Ligh |
The next grind setting to try after the user brewed and tasted: "I used 18 on my Encore and it was sour", "my espresso is bitter at 4.5 on the Ode". Sour, weak or fast means grind finer; bitter, harsh or slow means coarser. Returns one move on that grinder's own dial. Call again after each cup, and with result "good" once it tastes right, which also adds an anonymous report (grinder, method, setti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grinder | string | yes | Grinder name as the user said it, e.g. "Baratza Encore" |
| setting | number/string | yes | The setting they brewed at as written on the grinder, e.g. 18. On Fellow dials 4.2 is the second mark after 4; a Baratza Forte is macro number and micro letter, e.g. "4R". |
| result | string | yes | How it tasted: sour (also weak, thin, ran fast), bitter (also harsh, dry, ran slow), or good |
| method | string | no | Brew method, e.g. "espresso", "V60", "Kalita Wave". Pass it whenever the user has said it; the card shows that method's recipe. |
| coffee | string | no | The coffee as the user named it, roaster and name: "Stumptown Hair Bender". Only the coffee: never the user's name or other personal details. Leave out if they have not said. |
| roast | string | no | Optional roast level of that coffee, if known. Recorded with the report; it does not change the suggestion. |
Shortlist coffee grinders for someone deciding which one to buy: "which grinder should I get for pour over under $200?", "a quiet grinder for espresso", "best hand grinder for travel". Ranks BrewMark's grinder finder by how they brew, budget, hand or electric, and must-haves, and returns each pick with an approximate US price, why it fits, and a link to its BrewMark buying guide. BrewMark does not
| Parameter | Type | Required | Notes |
|---|---|---|---|
| methods | array | no | Brew methods they will use. Leave out if they did not say. |
| budget | number | no | Most they want to spend, in US dollars. Leave out for any price. |
| power | string | no | Hand grinder, electric, or either (default). |
| must_have | array | no | Only if the user asked for it. |
Every grinder BrewMark supports. Use this to check whether a grinder is covered, or to disambiguate when another tool reports more than one match. Not needed just to look up a name — the other tools accept ordinary names directly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Optional case-insensitive filter on brand or model name |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Brewmark 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: —
ATool-list grade · score 96 / 100
Release 1.1.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
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 · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestc7bfaa7e4b88d8602bd9050ddd5330115df1698aea1aa46e7be46be5ee2326c7
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| convert_grind_setting | no tags | |
| get_grinder_chart | no tags | |
| dial_in | no tags | |
| find_grinder | no tags | |
| list_grinders | no tags |
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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc7bfaa7e4b88d860
Scanned2026-10-28
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.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 Brewmark 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.