untappd-mcp
Related Servers
Alternatives to untappd-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for Untappd connectivity, enabling beer search with optional limit, offset, and sorting.MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching beers, retrieving profiles, wishlists, and drinking history, and performing check-ins with ratings and messages via the beer social platform.665 npmMIT
- AlicenseAqualityCmaintenanceA local-first MCP server for tracking beer releases on Vinmonopolet, enabling users to search new and upcoming beers, check store stock, find nearby stores, and manage watchlists.818 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for Android's Tasker automation app51MIT
- FlicenseNot gradedqualityDmaintenanceA simple MCP server that provides repository information (list repos, get repo details) using GitHub's public REST API, without needing any API keys or tokens.-
- AlicenseAqualityDmaintenanceA Node.js MCP server for X/Twitter that enables user profile queries, tweet search, tweet detail retrieval, and media downloads (images, videos, GIFs) via X's Web GraphQL API.62ISC
TDQS
Scored across 46 tools
Most tools target a distinct resource+action and the lengthy descriptions carefully explain boundaries (read-only vs write, cache-only vs API). However there are genuine overlaps: untappd_open_url is explicitly a superset of untappd_resolve plus an info tool, untappd_cache_has_had vs untappd_cache_has_had_many differ only in single vs list input, and cache_not_had overlaps top_not_had.
Nearly all tools use the untappd_ prefix with a predictable snake_case noun_verb pattern (search_beer, beer_info, delete_checkin, add_friend). A few deviate to bare nouns or irregular forms (untappd_checkin, untappd_toast, untappd_trending, untappd_notifications, untappd_healthcheck), but these are minor and still readable.
At 46 tools this is heavy for the surface and well above a comfortable range; the domain (beers, breweries, venues, users, check-ins, social, cache/sync) is rich but the count suggests over-fragmentation. Several tools could be consolidated (e.g. resolve/open_url, the multiple cache_* variants).
Coverage is broad and lifecycle-aware: search/info for beers, breweries and venues, user profiles/check-ins/beers/friends/wishlist, check-in create/delete, comment add/delete, toast toggle, plus sync/cache tooling and a healthcheck. The main gap is no update/edit-checkin or edit-comment operation, but core flows are otherwise well covered.