Skip to content
anlyon.dev

io.brewmark/brewmark

io.brewmark/brewmarkbrewmark.iostreamable-httpv1.0.0Scanned

Grind-setting conversion between 77 coffee grinders, plus dial-in charts for every model.

3 tools: 1 do something that can't be undone and 2 only read.

Tools: 0 delete, 1 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 1 finding

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →
Compare with similar serversMarkdownJSONReport this listing

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Can't be undone 1Claude Code: ask
  • convert_grind_settingTranslate a grind setting from one coffee grinder to another.Can send data out1 finding

    Why it is in this group

    • The name "convert_grind_setting" says "convert": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "convert_grind_setting" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "convert_grind_setting" says "convert": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Convert a grind setting
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • get_grinder_chartGrind settings for one grinder across every brew method.No findings

    Why it is in this group

    • The name "get_grinder_chart" says "get": a word for reading.
    Description, as the server wrote it
    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, drip, Chemex, French press and cold brew. The grinder can be named however the user said it.

    Annotations the server declares

    • title: Grinder settings chart
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_grindersEvery grinder BrewMark supports.No findings

    Why it is in this group

    • The name "list_grinders" says "list": a word for reading.
    Description, as the server wrote 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.

    Annotations the server declares

    • title: List supported grinders
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnconvert_grind_setting

    The server marks "convert_grind_setting" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "convert_grind_setting" says "convert": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http brewmark https://brewmark.io/api/mcp
claude mcp add --transport http brewmark https://brewmark.io/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__brewmark__get_grinder_chart",
      "mcp__brewmark__list_grinders"
    ],
    "ask": [
      "mcp__brewmark__convert_grind_setting"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as brewmark. Review it before you use it.

Capability tags behind 1 rule
  • mcp__brewmark__convert_grind_setting outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.brewmark/brewmark/verify?hash=87270cf72dcf7ac2b9d21314581943343ca71d85835abcdf27762d59f27a4cd0" | jq -e '.changed == false'

Pinned hash 87270cf72dcf, from Oct 22, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.brewmark/brewmark/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.brewmark/brewmark
[![anlyon.dev](https://anlyon.dev/badge/io.brewmark/brewmark.svg)](https://anlyon.dev/servers/io.brewmark/brewmark)

Source: MCP Registry. Synced Oct 22, 2026, 16:17 UTC.