io.github.lonniev/optionality-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 430 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

  fail25% of grade

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

  Python build script executes at build time: network call in build script

• Credential hygiene

  fail15% of grade

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

  tool "optionality_check_balance" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_purchase_credits" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_check_payment" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_restore_credits" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_account_statement" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_account_statement_infographic" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_report_issue" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_get_patron_onboarding_status" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_receive_credentials" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_receive_credentials" has a secret-shaped input parameter "credential_card" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_forget_credentials" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_update_patron_credential" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_delete_patron_credential" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_get_patron_credential_fields" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_receive_npub_proof" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_check_proof_status" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_set_pricing_model" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_reset_pricing_model" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_request_adoption" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_adoption_status" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_restore_neon_schema" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_check_price" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_mint_coupon" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_list_coupons" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_update_coupon" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_delete_coupon" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_redeem_coupon" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_list_my_coupons" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_forget_coupon" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_deal_scenario" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_fetch_scenario" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_ask_tip" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_fetch_tip" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_judge_trade" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_fetch_judgement" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_save_draft" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_list_journal" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_get_journal" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_delete_journal" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_share_entry" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_get_leaderboard" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_get_my_rank" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_set_display_name" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_get_patron_profile" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_set_profile" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_escrow_nsec" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_withdraw_nsec" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_send_patron_dm" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_get_escrow_status" has a secret-shaped input parameter "dpop_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "optionality_get_api_usage_stats" has a secret-shaped input parameter "dpop_token" — 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.

  Network egress present (pyproject declares an HTTP client dependency) — expected for most servers and not a finding on its own. 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

  unscannable10% of grade

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

  no prior version to diff (first sight of io.github.lonniev/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

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