Sicoob MCP

The materials state that no local API key or environment variable is required, which is a positive sign. However, connecting to a Sicoob/Open Finance account typically still involves user banking authorization or session credentials. With no README or flow documentation, the credential handling, storage, and revocation model is unclear, so financial authorization misuse risk should be treated with caution.

It is known to access the remote endpoint api.mcp.ai. Given the stated functionality, requests and related financial data for balances, statements, cards, and investments are likely transmitted through that endpoint. There is no evidence of exfiltration to unrelated or unknown domains, so this is a normal remote-connectivity concern rather than a clear high-risk red flag.

System checks indicate that this tool executes code or starts a local process, which is a common property of MCP tools. The available materials do not show requests for unusual system privileges, unrelated actions, or clearly dangerous command execution, so this is rated as caution rather than risk.

Its stated capabilities cover balances, statements, cards, and investments, indicating access to highly sensitive financial data. The materials do not state that it reads or writes local files or other extra resources, and there is no sign of permissions beyond the banking-data use case. Still, because the data is sensitive and documentation is sparse, access should be granted cautiously.

Positive factors include the official registry source, an auditable open-source repository, and updates within the last year, all of which materially reduce supply-chain risk. Points of caution are the missing README, no declared license, and 0 stars, which leave limited audit context and weak community validation, so it should not yet be treated as fully low risk.