io.github.AlvisoOculus/optionsahoy-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

  warn25% of grade

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

  tool "amt_iso_optimize" description: off-vendor URL in a description (optionsahoy.com); capability text should not name where data goes. tool "nso_calculate" description: off-vendor URL in a description (optionsahoy.com); capability text should not name where data goes. tool "rsu_sell_vs_hold" description: off-vendor URL in a description (optionsahoy.com); capability text should not name where data goes. tool "concentration_analyze" description: off-vendor URL in a description (optionsahoy.com); capability text should not name where data goes. tool "protective_put_price" description: off-vendor URL in a description (optionsahoy.com); capability text should not name where data goes. tool "qsbs_check" description: off-vendor URL in a description (optionsahoy.com); capability text should not name where data goes. tool "equity_funding_plan" description: off-vendor URL in a description (optionsahoy.com); capability text should not name where data goes. tool "rsu_lot_optimize" description: off-vendor URL in a description (optionsahoy.com); capability text should not name where data goes. server instructions: off-vendor URL in a description (optionsahoy.com); capability text should not name where data goes.

• Supply chain

  pass25% of grade

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

  repository linkage verified

• Credential hygiene

  pass15% of grade

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

  No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• 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 1.9.8 (minor bump): tool "amt_iso_optimize" description changed (wording only, no injection pattern); tool "nso_calculate" description changed (wording only, no injection pattern); tool "rsu_sell_vs_hold" description changed (wording only, no injection pattern); tool "concentration_analyze" description changed (wording only, no injection pattern); tool "protective_put_price" description changed and now contains embedded outbound URL; tool "qsbs_check" description changed and now contains embedded outbound URL; tool "equity_funding_plan" description changed and now contains embedded outbound URL; tool "rsu_lot_optimize" description changed and now contains embedded outbound URL; new hardcoded outbound host/BCC destination(s): github.com, optionsahoy.com.

• Transport config

  fail10% of grade

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

  remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class)