io.github.Yummybait-fin/uniswap-tx-builder-mcp

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  pass25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  Scanned 100 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

• Supply chain

  warn25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  dependency "viem" is edit-distance 2 from top-20 package "vue" (typosquat candidate)

• Credential hygiene

  fail15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  tool "build_mint" has a secret-shaped input parameter "token0" — secrets must never be tool parameters (the model would supply/handle the credential). tool "build_mint" has a secret-shaped input parameter "token1" — secrets must never be tool parameters (the model would supply/handle the credential). tool "plan_position" has a secret-shaped input parameter "token0" — secrets must never be tool parameters (the model would supply/handle the credential). tool "plan_position" has a secret-shaped input parameter "token1" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_pool_state" has a secret-shaped input parameter "token0" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_pool_state" has a secret-shaped input parameter "token1" — secrets must never be tool parameters (the model would supply/handle the credential). tool "build_swap" has a secret-shaped input parameter "tokenIn" — secrets must never be tool parameters (the model would supply/handle the credential). tool "build_swap" has a secret-shaped input parameter "tokenOut" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_swap_quote" has a secret-shaped input parameter "tokenIn" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_swap_quote" has a secret-shaped input parameter "tokenOut" — secrets must never be tool parameters (the model would supply/handle the credential).

• Permission scope

  pass15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• Version behavior

  fail10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  vs prior 0.4.2 (patch bump): new tool "build_collect" touches a sensitive surface (email/exec/net/fs); new tool "build_close" touches a sensitive surface (email/exec/net/fs); new tool "build_mint" appeared; new tool "build_increase" appeared; new tool "build_approve" appeared; new tool "plan_position" touches a sensitive surface (email/exec/net/fs); new tool "get_pool_state" touches a sensitive surface (email/exec/net/fs); new tool "get_positions" touches a sensitive surface (email/exec/net/fs); new tool "build_wrap" touches a sensitive surface (email/exec/net/fs); new tool "build_swap" touches a sensitive surface (email/exec/net/fs); new tool "get_swap_quote" touches a sensitive surface (email/exec/net/fs).

• Transport config

  unscannable10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.