untappd-mcp 1.10.0 → 1.10.1

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
   },
   "metadata": {
     "description": "MCP server for Untappd — beers, breweries, venues, check-ins, wishlists, and your friend feed",
-    "version": "1.10.0"
+    "version": "1.10.1"
   },
   "plugins": [
     {
@@ -15,7 +15,7 @@
       "displayName": "Untappd",
       "source": "./",
       "description": "MCP server for Untappd — search beers/breweries/venues, read profiles/check-ins/wishlists, and post check-ins, toasts, and comments",
-      "version": "1.10.0",
+      "version": "1.10.1",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "untappd-mcp",
   "displayName": "Untappd",
-  "version": "1.10.0",
+  "version": "1.10.1",
   "description": "MCP server for Untappd — search beers/breweries/venues, read check-ins and wishlists, and post check-ins, toasts, and comments",
   "author": {
     "name": "Chris Hall",

package/dist/bundle.js

@@ -35675,7 +35675,7 @@ function toolAnnotations(opts = {}) {
 }
 
 // src/version.ts
-var VERSION = "1.10.0";
+var VERSION = "1.10.1";
 
 // src/client.ts
 import { dirname, join } from "path";

package/dist/version.js

@@ -3,4 +3,4 @@
 // json's `extra-files`), and `versionSyncTest` guards that it stays equal to
 // package.json. Import VERSION wherever the version is needed rather than
 // re-declaring it.
-export const VERSION = '1.10.0'; // x-release-please-version
+export const VERSION = '1.10.1'; // x-release-please-version

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "untappd-mcp",
-  "version": "1.10.0",
+  "version": "1.10.1",
   "mcpName": "io.github.chrischall/untappd-mcp",
   "description": "Untappd MCP server for Claude — developed and maintained by AI (Claude Code)",
   "author": "Claude Code (AI) <https://www.anthropic.com/claude>",

package/server.json

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

package/skills/untappd-mcp/SKILL.md

@@ -40,6 +40,95 @@ Run `untappd_healthcheck` to confirm login works.
 
 Most user tools default `username` to your configured account when omitted.
 
+## Response shape (`view`)
+
+Twelve of this server's 45 tools take `view: "compact" | "full"`, and
+**`compact` is the DEFAULT** — the slim rung is what you get without asking
+for it.
+
+**If you were told to pass `compact: true`, that advice is stale.** It used to
+be true: the projection shipped as an opt-in boolean defaulting to `false`,
+and the tool descriptions asked the caller to please turn it on. An efficiency
+you have to request is one that mostly is not requested — and the caller
+paying for the fat record was the one least able to know a slim rung existed.
+So it flipped. The old parameter is gone; it is not declared anywhere, so zod
+drops the unknown key and the call succeeds. You get the compact rung — right
+answer, wrong reason. **The same silence bites the other way**: `compact:
+false` no longer buys you the full record either. It is dropped identically
+and you still get compact. `view: "full"` is the only way back.
+
+Compact comes in two tiers here, and they are not the same thing:
+
+**A hand-written field projection — 8 tools.**
+
+- Check-ins (`untappd_activity_feed`, `untappd_user_checkins`,
+  `untappd_beer_activity`, `untappd_venue_activity`,
+  `untappd_local_checkins`): each ~5 KB record becomes `{checkin_id,
+  created_at, user, rating, comment, beer{bid, name, style, abv}, brewery,
+  venue, toasts, comments, has_photo}`. A default page of 25 was upwards of
+  100 KB to learn what someone drank.
+- `untappd_search_beer`: each ~1.2 KB match becomes `{bid, name, style, abv,
+  ibu, brewery, checkin_count, have_had}` — the long `beer_description` and
+  the nested brewery record go.
+- `untappd_user_wishlist`: the same beer core plus `added_at`.
+- `untappd_user_beers`: the same beer core plus `your_count`, `your_rating`,
+  `global_rating`, `last_had`.
+
+**An upstream request for less — 4 tools.** `untappd_user_info`,
+`untappd_beer_info`, `untappd_brewery_info` and `untappd_venue_info` forward
+`compact=true` to Untappd's own endpoint, which drops the embedded
+activity/list blocks server side. **There is no local projection on these**:
+the entity's own fields are byte-identical on both rungs. What compact saves
+is Untappd's embedded blocks — and the bandwidth, not just the context. Do not
+expect a shorter beer record from `untappd_beer_info`; expect the recent-
+activity block to be absent.
+
+The projectors are **drift-safe**. Each keys off a documented container
+(`checkins.items`, `beers.items`); if that array is not where it is expected —
+this is a reverse-engineered API — the projector warns on stderr and returns
+the RAW response rather than an empty or wrong one. A short answer is never
+silently manufactured.
+
+`view: "full"` returns Untappd's response untouched. There is deliberately
+**no `raw` rung**: nothing here re-serialises or normalises a payload, so
+`full` already IS the upstream response and a third value would silently alias
+one that exists.
+
+### 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`,
+  `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
+  decoration.
+- **`untappd_sync_checkins` / `untappd_sync_user_beers`** answer with sync
+  PROGRESS — pages walked, `another_run_needed`, `backfill_complete`. Slimming
+  a progress report is how you lose the field that says it is not finished.
+- **The five cache tools** (`untappd_cache_has_had`, `…_has_had_many`,
+  `…_not_had`, `untappd_cache_query`, `untappd_top_not_had`) answer from the
+  local SQLite mirror in a shape this repo already wrote — a verdict plus the
+  `freshness` block that says whether a "not found" might be a false negative.
+  There is no upstream payload behind them to project away from.
+- **`untappd_checkin_info`** exists to return the FULL record for one check-in
+  — photos, badges earned, toasts, comments. The ~5 KB the check-in projection
+  removes is exactly what you called this tool to get.
+- **`untappd_venue_menu`** is already its own hand-written projection, with a
+  per-call page budget and a resumable `next_section_offset` contract. A
+  second projection on top of it would fight the first.
+- **`untappd_resolve`, `untappd_open_url`, `untappd_healthcheck`** return a
+  verdict or a diagnostic.
+- **The remaining ten reads** — `untappd_trending`, `untappd_notifications`,
+  `untappd_brewery_beers`, `untappd_search_brewery`, `untappd_search_venue`,
+  `untappd_user_badges`, `untappd_user_friends`, `untappd_user_venues`,
+  `untappd_pending_friends`, `untappd_venue_by_foursquare` — hand back
+  Untappd's payload as it arrived. No projector has been written for their
+  shapes, so there is no rung to ask for and **no slim option exists**.
+  `untappd_brewery_beers` is the one worth budgeting for: it returns a beer
+  list, which is the shape the beer projectors handle, but it is not wired to
+  one — a 50-beer page arrives as 50 full records.
+
 ## Write tools (confirm-gated — these post to your public account)
 
 Each returns a dry-run preview and makes NO network call unless called with