Bradesco MCP

The material states that no environment variables or API keys are required, which is a positive sign; however, connecting a bank account will likely still involve user authorization tokens or banking/Open Finance sessions in practice. The documentation does not explain credential acquisition, storage, or expiration behavior, so financial authorization misuse should be treated with caution.

It is known to connect to the remote endpoint api.mcp.ai. Given the stated features (balances, statements, cards, investments), related financial data will reasonably be transmitted through that service; however, there is no evidence here of exfiltration to unrelated or unknown third-party endpoints.

System checks indicate that this MCP executes code/spawns processes, which is a normal capability for this class of tool and warrants caution. The available material does not describe any unusual system permissions or local control beyond what would typically be needed for a banking data connector.

Its stated access scope includes balances, statements, cards, and investment information, all of which are highly sensitive financial data. The material does not indicate local file access or access to resources unrelated to banking, so the main concern is the sensitivity of the financial data itself rather than obvious over-permissioning.

It comes from an official registry, has an auditable open-source repository, and has been updated within the last year, all of which materially reduce supply-chain risk. Although the README is missing, the license is undeclared, and community stars are very low, the current facts do not justify a high-risk rating.