Banco Sofisa MCP

The materials state that no environment variables or static keys are required, which reduces long-lived secret exposure. However, because it connects to a bank account, it will likely still handle runtime authorization tokens or sessions, which are sensitive financial access credentials and should be protected with least privilege.

It is known to connect to the declared endpoint api.mcp.ai. Given its purpose of retrieving balances, statements, cards, and investments, user financial query data will likely transit through that remote service. This egress is aligned with the stated function, and no unrelated or unknown endpoints are disclosed, but the sensitivity of financial data warrants caution.

System checks indicate that this MCP executes code or runs a local process. This is a normal MCP capability, and the materials do not show requests for unusual system privileges or unrelated high-risk actions, so this is rated caution rather than risk.

The description indicates access to Banco Sofisa account data, including balances, statements, cards, and investments; all of these are highly sensitive financial data. The materials do not state that it reads or writes local files or requests data beyond its declared purpose, so the main concern is the sensitivity of the account data itself.

The source is an official registry entry and the code is publicly available with updates within the last year, all of which reduce risk. However, the repository has no declared license, very low community adoption (0 stars), and no README, limiting audit context and real-world scrutiny, so caution is still appropriate.