io.github.yunaremaia/x402-crypto-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 133 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

  pass25% of grade

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

  repository linkage verified

• Credential hygiene

  fail15% of grade

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

  tool "token_info" has a secret-shaped input parameter "token_address" — secrets must never be tool parameters (the model would supply/handle the credential). tool "token_balance" has a secret-shaped input parameter "token_address" — 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

  warn10% of grade

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

  vs prior 1.3.6 (patch bump): new tool "crypto_prices" appeared; new tool "top_movers" appeared; new tool "convert" appeared; new tool "token_profile" appeared; new tool "tx_status" appeared; new tool "solana_tx_status" appeared; new tool "wallet_balance" appeared; new tool "solana_balance" appeared; new tool "token_info" appeared; new tool "token_balance" appeared; new tool "ens_reverse" appeared; new tool "block_height" appeared; new tool "ens_resolve" appeared; new tool "market_sentiment" appeared; new tool "fng_history" appeared; new tool "open_interest" appeared; new tool "funding_rate" appeared; new tool "technical_indicators" appeared; new tool "candle_history" appeared; new tool "market_overview" appeared; new tool "defi_yields" appeared; new tool "gas_price" appeared; new tool "yield_pool_metrics" appeared; new tool "fresh_markets" appeared.

• 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.