Banrisul MCP

The materials state that no environment variables or API keys are required, but a tool that connects to a Banrisul account and accesses open-finance data will likely still rely on user banking authorization or session credentials in practice. The documentation does not explain the auth flow, token storage, or expiration behavior, so credential handling lacks transparency.

It is known to connect to the remote endpoint api.mcp.ai. Given the stated functions around balances, statements, cards, and investments, user financial data is likely transmitted through that endpoint; the materials do not clarify whether it is only a relay, whether it connects directly to bank APIs, or what the transmission and retention boundaries are.

System checks indicate that the tool executes code or launches a process, which is a standard MCP capability. The provided materials do not show requests for unusual system privileges or unrelated high-risk capabilities, so the main concern is routine isolation and least-privilege execution.

Based on the feature description, the target data includes account balances, statements/transactions, cards, and investment information, all of which are highly sensitive financial data. The materials do not describe local file read/write scope or whether write/transaction actions are supported; the main concern is the unclear visibility and authorization boundary for financial data.

Positive signals include distribution via an official registry, open-source availability, and updates within the last year. Concerns remain because the README is effectively absent, no license is declared, and community adoption is very low (0 stars), which weakens auditability and ecosystem validation; however, these facts alone do not justify a high-risk rating.