io.github.brunovicco/openfinance-br-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

  unscannable25% of grade

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

  No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.

• 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

  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.

  Network egress present (src/openfinance_br_mcp/context.py: outbound HTTP/socket call) — 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

  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.1.0 (minor bump): new capability primitive(s) in source: http-client; new hardcoded outbound host/BCC destination(s): ..., api.banco.com.br, api.bradesco.com, api.caixa.gov.br, api.mais.ob.btgpactual.com, api.nubank.com.br, api.sicoob.com.br, bank.example, bank.example.com, cloud.langfuse.com, customerdata-mtls.of.bb.com.br, data.directory.openbankingbrasil.org.br, data.sandbox.directory.openbankingbrasil.org.br, example.com, github.com, idp.example.com, impostor-idp.example.com, impostor.example.com, matls-banking-openfinance.xpi.com.br, matls-open.btgmais.com, mcp.example.com, oauth-mtls.of.bb.com.br, oauth2.opf.itau, oidc-mtls.openbanking.picpay.com, openbanking.api.nubank.com.br, openbanking.api.santander.com.br, openfinancebrasil.atlassian.net, resolved.example.com, resources-mtls.openbanking.picpay.com, secure.opf.api.itau, some-other-server.example.com, tempo.example.com, token.example.com, trust-openbanking.api.santander.com.br, unused.example.com, us.cloud.langfuse.com, x, x.com, your-domain.com, your-idp.example.com, your-mcp-server.example.com.

• Transport config

  warn10% of grade

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

  manifest/source references Tracking behavior — disclosure