io.github.cammac-creator/ibanforge

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 "validate_iban" description: off-vendor URL in a description (api.ibanforge.com); capability text should not name where data goes. tool "batch_validate_iban" description: off-vendor URL in a description (api.ibanforge.com); capability text should not name where data goes. tool "lookup_bic" description: off-vendor URL in a description (api.ibanforge.com); capability text should not name where data goes. tool "check_compliance" description: off-vendor URL in a description (api.ibanforge.com); capability text should not name where data goes. tool "validate_payment_reference" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn). tool "validate_payment_reference" description: off-vendor URL in a description (api.ibanforge.com); capability text should not name where data goes. tool "check_postal_address" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn). tool "check_postal_address" description: off-vendor URL in a description (api.ibanforge.com); capability text should not name where data goes. tool "lookup_ch_clearing" description: off-vendor URL in a description (api.ibanforge.com); capability text should not name where data goes. server instructions: off-vendor URL in a description (api.ibanforge.com); capability text should not name where data goes. server instructions: off-vendor URL in a description (ibanforge.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.4.3 (patch bump): tool "validate_iban" description changed and now contains embedded outbound URL; tool "batch_validate_iban" description changed and now contains embedded outbound URL; tool "lookup_bic" description changed and now contains embedded outbound URL; tool "check_compliance" description changed and now contains embedded outbound URL; tool "validate_payment_reference" description changed and now contains embedded outbound URL; tool "check_postal_address" description changed and now contains embedded outbound URL; tool "lookup_ch_clearing" description changed and now contains embedded outbound URL; new hardcoded outbound host/BCC destination(s): basescan.org, cdn.sheetjs.com, dashboard.stripe.com, github.com, ibanforge.com, relay.example.net, www.ibanforge.com, x402.org.

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