io.github.chrischall/untappd-mcp
NPM · UNTAPPD-MCP
Untappd MCP — search beers/breweries/venues, read check-ins & wishlists, post check-ins
Available components
Last scanned (9 hours ago)
Scores higher than 96% of npm servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to chrischall/untappd-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 13411 tokens (~231/item across 58 items; 58 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 58 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 4 Nov 26 +15
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 2.5.2 → 2.6.1 functional
- Package version: 2.5.2 → 2.6.0 functional
- 3 Nov 26 −27
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Schema quality: 182 → 230 ▼ functional
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 2.4.0 → 2.5.2 functional
- Package version: 2.4.0 → 2.5.1 functional
- Package version: 2.4.0 → 2.5.0 functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 8023 → 8964 ▼ functional
- Package version: 2.3.2 → 2.4.0 functional
- Package version: 2.3.1 → 2.3.2 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/untappd-mcp@2.6.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | chrischall/untappd-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/chrischall/untappd-mcp/.github/workflows/release-please.yml@refs/heads/main |
| Rekor log index | 3691538074 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ddc58ec04c7222dc219956fa40154e2b781435396e78a44efed7d0826d2f060aa2e0d5edb2d5ee0691971140fd27d8e62d5524af059405364974abfd1 |
Background: How many MCP packages publish verified provenance →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
untappd_user_wishlist Get Untappd user wishlist ~196
Get the beers on a user's wishlist. Supports sorting and paging. Omit username for your own account. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max beers (1–50, default 25) |
| offset | integer | – | Result offset for paging (default 0) |
| sort | string | – | Sort order (default date added, newest first) |
| username | string | – | Untappd username. Omit to use your own configured account (UNTAPPD_USERNAME). |
| view | string | – | Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact projects each wishlisted beer to {bid, name, style… |
No output schema declared.
No examples provided.
untappd_venue_activity Get recent check-ins at a venue ~228
Get the recent public check-ins at a venue by its id — who was there, what they drank, and their ratings. Page backwards with max_id (the pagination.max_id from a prior call). Cached locally for 6 hours per venue + limit + max_id (cache.hit, fetched_at, expires_at); refresh:true re-fetches. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max check-ins (1–50, default 25) |
| max_id | integer | – | Return check-ins older than this id (for paging) |
| refresh | boolean | – | Bypass the 6-hour local cache and call Untappd (default false) |
| venue_id | integer | yes | Untappd venue id |
| view | string | – | Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact projects each check-in to {id, user, beer, brewery… |
No output schema declared.
No examples provided.
untappd_venue_by_foursquare Look up an Untappd venue by Foursquare id ~83
Resolve a Foursquare venue id to its Untappd venue. Useful to turn a foursquare_id (e.g. from a check-in) into an Untappd venue you can pass to untappd_venue_info / untappd_venue_activity. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| foursquare_id | string | yes | Foursquare venue id |
No output schema declared.
No examples provided.
untappd_venue_info Get Untappd venue detail ~137
Get full detail for a venue by its Untappd venue id: category, address, contact, rating, total check-ins, and — on view:"full" — top beers and recent activity. Get an id from untappd_search_venue. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| venue_id | integer | yes | Untappd venue id |
| view | string | – | Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact also asks Untappd for its own slim record, droppin… |
No output schema declared.
No examples provided.
untappd_venue_menu Get a venue's verified beer menu (section-paged) ~526
Return a venue's verified beer menu as a flat, compact list of beers. untappd_venue_info returns only the FIRST section of each menu (Untappd defaults the section list to one), so it silently under-reports any venue whose menu spans multiple sections — e.g. a 23-beer wall that comes back with 2 items. This tool forwards the section_limit / section_offset paging params venue/info echoes back but never receives, walks sections up to a per-call max_pages budget (respecting the ~100 calls/hour limit — it does NOT loop to completion in one call), and flattens to [{bid, name, brewery, brewery_id, style, abv, price, serving_type, menu, section}]. Like the sync tools it is resumable: when the budget runs out before full coverage it returns another_run_needed:true plus next_section_offset to pass back on the next call. truncated:true means the upstream returned no more sections short of total_count (e.g. it ignored the paging params) — not resumable. Results are cached locally for 6 hours per venue + paging params (cache.hit, fetched_at, expires_at) so repeated trip planning does not re-spend calls; refresh:true re-fetches. With the cache, the result also carries favorite {is_favorite, sources, reason} for the venue, and favorite / brewery_favorite on each beer that is one (derived from username's history or added with untappd_favorite_add; default your account) — applied on read, so never stale. Get an id from untappd_search_venue. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| max_pages | integer | – | API calls to spend THIS run — page budget, not page size (default 3). Resume with next_section_offset if another_run_needed. |
| menu_id | integer | – | Restrict to a single menu id (from a prior result). Optional. |
| refresh | boolean | – | Bypass the 6-hour local cache and call Untappd (default false) |
| section_limit | integer | – | Sections fetched per API call — page size (default 50). |
| section_offset | integer | – | Section offset to start from; pass a prior next_section_offset to resume (default 0). |
| sort | string | – | Menu sort key (e.g. 'publish_order', 'highest_rated'). Optional. |
| username | string | – | Whose favorites to mark (cache only; default your configured account) |
| venue_id | integer | yes | Untappd venue id |
No output schema declared.
No examples provided.
untappd_venue_pick Pick beers off a venue's Untappd menu that a user hasn't had ~319
Like untappd_menu_pick, but takes an Untappd venue (URL or id) instead of menu lines: it pulls the venue's FULL verified menu (walking every section page until complete, within api_budget), refreshes the user's distinct-beers cache (incremental, or an automatic backfill), checks every menu beer against it and ranks the not-had ones by global rating. Returns the same picks / not_had / had / sync shape plus a venue block (menu_complete is false only if the budget ran out mid-menu). A venue with no verified menu comes back unresolved — use untappd_menu_pick with the tap list instead. Omit username for your own account.
| Name | Type | Req | Description |
|---|---|---|---|
| api_budget | integer | – | Max Untappd API calls this run, shared by the cache sync, searches and rating lookups (default 60; Untappd allows ~100/hour). If it runs out, the result says another_run_needed and a re-run continues… |
| style_filter | string | – | Case-insensitive substring filter on the beer style or parent style for the picks (e.g. "ipa", "stout"). |
| top_n | integer | – | How many picks to return (default 2, max 10). |
| username | string | – | Untappd username. Omit to use your own configured account (UNTAPPD_USERNAME). |
| venue | – | yes | Untappd venue URL (https://untappd.com/v/<slug>/<id>) or numeric venue id. |
No output schema declared.
No examples provided.
untappd_wishlist_add Add a beer to your wishlist ~181
Add a beer to YOUR Untappd wishlist by its bid. Writes to your account. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
| Name | Type | Req | Description |
|---|---|---|---|
| bid | integer | yes | Untappd beer id (bid) — from untappd_search_beer |
| confirmToken | string | – | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has se… |
No output schema declared.
No examples provided.
untappd_wishlist_remove Remove a beer from your wishlist ~181
Remove a beer from YOUR Untappd wishlist by its bid. Writes to your account. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
| Name | Type | Req | Description |
|---|---|---|---|
| bid | integer | yes | Untappd beer id (bid) — from untappd_search_beer |
| confirmToken | string | – | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has se… |
No output schema declared.
No examples provided.
How do I install the io.github.chrischall/untappd-mcp server?
io.github.chrischall/untappd-mcp runs locally as an npm package, launched with npx -y untappd-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · untappd-mcp
claude mcp add chrischall-untappd-mcp -- npx -y untappd-mcp
What is the io.github.chrischall/untappd-mcp server?
io.github.chrischall/untappd-mcp is listed in the public MCP registry as io.github.chrischall/untappd-mcp. Untappd MCP, search beers/breweries/venues, read check-ins & wishlists, post check-ins. This page covers its npm package (untappd-mcp).
Is the io.github.chrischall/untappd-mcp server safe to use?
io.github.chrischall/untappd-mcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.chrischall/untappd-mcp server expose?
io.github.chrischall/untappd-mcp exposes 58 tools: untappd_search_beer, untappd_beer_info, untappd_beer_activity, untappd_search_brewery, untappd_brewery_info, and 53 more. Their descriptions and schemas cost roughly 13,411 tokens of context every time the server is loaded.
Is the io.github.chrischall/untappd-mcp server still maintained?
io.github.chrischall/untappd-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.chrischall/untappd-mcp server under?
io.github.chrischall/untappd-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.chrischall/untappd-mcp server?
VerifyMCP ran 16 checks on io.github.chrischall/untappd-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.