Banco Digio MCP

The material says no local secrets or environment variables are required, which is a positive sign. However, it is intended to connect to a Banco Digio/Open Finance account, so real authorization likely happens via an external financial consent flow. With no README, token exchange, storage, and revocation details are not visible, so caution is warranted around post-authorization misuse risk.

It is known to access the remote endpoint api.mcp.ai; based on the feature description, financial data such as balances, statements, cards, or investments may be transmitted through that endpoint. There is no evidence of unrelated or clearly suspicious domains, but the egress target is not a Banco Digio official domain, and the sparse documentation does not clarify data minimization or transmission boundaries.

The system checks indicate that this MCP tool executes code/spawns a process, which is a normal capability for this class of tools. The material does not show requests for unusual system privileges, arbitrary script execution, or dangerous local capabilities unrelated to banking access, so this is better rated as caution rather than risk.

By description, its target data scope is Banco Digio/Open Finance account information, including balances, statements, cards, and investments, which is highly sensitive financial data. There is no explicit indication that it reads/writes local files or requests excessive local data permissions, but with no README the exact scope, caching behavior, and retention period remain unclear.

The source is an official registry entry, and there is an auditable open-source repository updated within the last year, both of which materially reduce supply-chain risk. On the other hand, no license is declared, community adoption is 0 stars, and public documentation is sparse, which limits confidence and audit depth, so an overall caution rating is still appropriate.