Porto Bank MCP

The material states that no local secrets or environment variables are required, which is a positive sign; however, connecting to a Porto Bank/Open Finance account will likely still involve user banking authorization or session credentials in practice. The documentation does not explain how credentials are obtained, stored, refreshed, or revoked, so misuse of financial account authorization should be treated with caution.

It is known to access the remote endpoint api.mcp.ai. Given its stated functionality, user requests involving balances, statements, cards, or investments are likely transmitted to or processed through that service; the material does not disclose the detailed data flow, whether it connects directly to the bank, or what data minimization controls are in place.

The system checks explicitly indicate that it executes code; this is a standard MCP capability and therefore warrants caution by default. The available material does not show requests for unusual system privileges, nor does it describe high-risk local operations unrelated to banking queries.

Its stated capabilities focus on reading Porto Bank/Open Finance financial data such as balances, statements, cards, and investments; this data is inherently sensitive. The material does not mention local file read/write access or data access beyond the stated scope, but the financial data itself should be treated as highly sensitive.

It comes from an official registry and has an auditable open-source repository with updates within the last year, all of which materially reduce supply-chain risk. On the other hand, the lack of a README, an unspecified license, and 0 stars indicate limited transparency and community validation, so “caution” is more appropriate than “safe.”