Itaú MCP

The materials state that no separate API key or environment variables are required, which reduces static secret exposure. However, connecting an Itaú account will likely still involve user banking/Open Finance authorization tokens or sessions in practice, which are highly sensitive financial credentials and should not be granted in uncontrolled environments.

It is known to access the remote endpoint api.mcp.ai. Based on the stated functionality, user requests and account data such as balances, statements, cards, and investments are likely transmitted through that endpoint. This is consistent with the declared purpose, and there is no evidence of transmission to unrelated or unknown domains, but the data sensitivity is high.

The system checks explicitly indicate that this MCP tool executes code / runs as a local process. This is standard behavior for MCP tools, and the materials do not show requests for unusual system privileges or actions unrelated to its stated purpose, so this is a caution rather than a high-risk finding.

Per the description, the primary data scope includes balances, statements/transactions, cards, and investment information, all of which are highly sensitive personal financial data. However, this scope is broadly aligned with the stated functionality. The materials do not indicate local file read/write access or additional permissions beyond the financial aggregation use case.

The source is an official registry entry and an open-source repository is provided, with updates within the past year; these are strong positive supply-chain signals that lower overall risk. Caveats include the lack of a README, no declared license, and low star count, which reduce audit convenience and adoption confidence, but they do not amount to a high-risk red flag here.