Banco Bmg MCP

The material indicates no separate environment variables or API keys are required, which reduces explicit secret-handling exposure. However, because it connects to a Banco Bmg account, real use will likely involve bank/Open Finance authorization tokens or account consent, which are highly sensitive financial credentials and warrant scrutiny over scope and storage.

It is known to connect to api.mcp.ai; given the stated functionality, financial data such as balances, statements, cards, or investments may be transmitted through that endpoint. There is no evidence of exfiltration to unrelated or suspicious domains, but outbound network access still involves sensitive financial information and should be reviewed for transmitted scope, least privilege, and privacy terms.

System checks indicate the tool executes code or starts a local process, which is a normal MCP capability and merits caution by default. The available material does not specify additional system capabilities or show requests for privileges beyond its stated function, so there is not enough evidence to rate this as high risk.

Its functionality directly targets Banco Bmg Open Finance data and is expected to access balances, statements/transactions, cards, and investment information, all of which are highly sensitive. The material does not show a need to read/write local files or access resources unrelated to banking, so the main concern is the scope of financial data rather than obvious excessive local access.

Positive factors include being listed in an official registry, being open source, and having updates within the last year, all of which materially reduce supply-chain risk. Points to watch are the currently very low community adoption (0 stars), no declared license, and missing README, which limit audit context; therefore caution is more appropriate than a low-risk rating.