untappd-mcp 2.1.3 → 2.2.1

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/chrischall/untappd-mcp",
     "source": "github"
   },
-  "version": "2.1.3",
+  "version": "2.2.1",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "untappd-mcp",
-      "version": "2.1.3",
+      "version": "2.2.1",
       "transport": {
         "type": "stdio"
       },

package/skills/untappd-mcp/SKILL.md

@@ -42,7 +42,7 @@ Most user tools default `username` to your configured account when omitted.
 
 ## Response shape (`view`)
 
-Thirteen of this server's 45 tools take `view: "compact" | "full"`, and
+Thirteen of this server's 46 tools take `view: "compact" | "full"`, and
 **`compact` is the DEFAULT** — the slim rung is what you get without asking
 for it.
 
@@ -104,14 +104,14 @@ silently manufactured.
 `full` already IS the upstream response and a third value would silently alias
 one that exists.
 
-### The 32 tools without `view`
+### The 33 tools without `view`
 
 Each for its own reason — and none of them will tell you it ignored the
 parameter, because an undeclared key is dropped by zod without a warning:
 
-- **The 11 confirm-gated writes** (`untappd_checkin`, `untappd_toast`,
+- **The 12 confirmation-gated writes** (`untappd_checkin`, `untappd_toast`,
   `untappd_add_comment`, the two deletes, the wishlist pair, the four friend
-  actions) answer with a dry-run preview or a receipt. Nothing in a receipt is
+  actions, and the local `untappd_cache_forget`) answer with a confirmation preview or a receipt. Nothing in a receipt is
   decoration.
 - **`untappd_sync_checkins` / `untappd_sync_user_beers`** answer with sync
   PROGRESS — pages walked, `another_run_needed`, `backfill_complete`. Slimming
@@ -140,10 +140,15 @@ parameter, because an undeclared key is dropped by zod without a warning:
   (#161) — it takes a `view` now, and its field shape is documented with the
   other projections above.
 
-## Write tools (confirm-gated — these post to your public account)
+## Write tools (confirmation-gated — these post to your public account)
 
-Each returns a dry-run preview and makes NO network call unless called with
-`confirm: true`:
+Each asks the user to confirm first. Where the client can show a confirmation
+prompt, it does. Otherwise the first call makes NO network call and returns
+`status: "confirmation-required"` with a `preview` of the exact request and a
+`confirmToken`; show the preview to the user, and only after they approve call
+the tool again with the same arguments plus `confirmToken`. A token works once
+and only for those arguments (a change returns `DRAFT_CHANGED` with a fresh
+preview). `MCP_CONFIRM_MODE` on the server can make this `auto` or `refuse`.
 
 - `untappd_toast` — toast/like a check-in (this endpoint is a toggle).
 - `untappd_add_comment` — comment on a check-in.
@@ -185,6 +190,12 @@ Query tools (has-had ones consult BOTH sources — a hit in either = had):
 - `untappd_cache_query` — filter cached check-ins by brewery, style, `min_rating`,
   venue, and date range.
 
+**Retention.** The cache keeps what you sync until you remove it — including
+friends' dated check-ins, comments and venues. `untappd_cache_forget` (confirmation-gated)
+deletes one user's check-ins, distinct beers and sync state from the LOCAL cache
+only; Untappd is untouched and a later sync can re-fetch. The file is created
+owner-only (dir `0700`, file `0600`).
+
 Every cache read returns a `freshness` block reporting each source's completeness
 separately (plus `coverage_complete` and a `caveat` when incomplete), so you can
 flag a "not found" as possibly a false negative until the relevant sync finishes.