Banco do Brasil MCP

The material says no local keys/environment variables are required, but connecting a bank account will likely still involve user banking/Open Finance authorization tokens or sessions in practice; misuse of such credentials would impact financial data security. No request for additional system-level secrets or explicit credential-abuse design is shown.

It is known to access the remote endpoint api.mcp.ai. Given the stated functionality, financial data such as balances, statements, and cards is likely transmitted through that endpoint; there is no evidence here of exfiltration to unrelated or unknown third-party domains, but it should still be treated as a sensitive data egress path.

The system checks indicate that this tool executes code/spawns a process, which is a normal MCP capability. The available material does not show requests for system privileges beyond its stated function, nor does it describe arbitrary high-risk system operations, so a caution rating is more appropriate.

Its stated purpose directly covers highly sensitive financial data such as account balances, statements/transactions, and cards, so the data sensitivity is high; however, that access is aligned with the declared functionality. The material does not indicate local file read/write, access to unrelated data sources, or clearly excessive authorization.

The source is an official registry entry, and an open-source repository is available with updates within the last year, providing some auditability and maintenance signals; these factors materially reduce supply-chain risk. That said, community adoption is very low (0 stars) and the license is not declared, so independent review of the code and dependencies is still advisable.