Untappd (darrenjrobinson) MCP Server

untappd-mcp-server npm v2.0.0 Source verified

Published by darrenjrobinson — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server exposing Untappd API tools for AI agents — full v4 read API coverage

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (dist/auth.js)MTC-SRC-002

In the server's implementation (`dist/auth.js:46`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ractiveAuth; const node_child_process_1 = require("node:child_process"); const node_crypto_1 = require("node:crypto"); c

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/auth.js

Tools 27

Each tool and what it can reach — statically extracted from the published source.

  • authenticate_untappdno sensitive capability
  • get_auth_statusno sensitive capability
  • get_beer_checkinsno sensitive capability
  • get_beer_infono sensitive capability
  • get_brewery_checkinsno sensitive capability
  • get_brewery_infono sensitive capability
  • get_checkin_infono sensitive capability
  • get_friend_feedno sensitive capability
  • get_global_feedno sensitive capability
  • get_local_feedno sensitive capability
Show 17 more tools ↓
  • get_trending_beersno sensitive capability
  • get_user_activityno sensitive capability
  • get_user_badge_summaryno sensitive capability
  • get_user_badgesno sensitive capability
  • get_user_beer_statsno sensitive capability
  • get_user_distinct_beersno sensitive capability
  • get_user_friendsno sensitive capability
  • get_user_infono sensitive capability
  • get_user_stats_at_venueno sensitive capability
  • get_user_wishlistno sensitive capability
  • get_venue_checkinsno sensitive capability
  • get_venue_foursquare_lookupno sensitive capability
  • get_venue_infono sensitive capability
  • search_beerno sensitive capability
  • search_breweryno sensitive capability
  • search_venue_then_get_user_statsno sensitive capability
  • venue_searchno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.0.0 latest A 94/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/untappd-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/untappd-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/untappd-mcp-server"><img src="https://mcptrustchecker.com/registry/untappd-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/untappd-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan untappd-mcp-server --online

Use the free API → How scoring works

Other implementations of Untappd 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Web, Search & Scraping