Sicredi MCP

The materials state that no environment variables or API keys are required, but connecting a Sicredi/Open Finance account will typically still involve user banking authorization or session credentials. There is no evidence of credential abuse, yet any authorization token or login flow should be treated as highly sensitive due to the financial context.

It is known to connect to the remote endpoint api.mcp.ai; given the stated functionality, financial data such as balances, statements, cards, and investments will likely be transmitted through that endpoint. There is no visible red flag of exfiltration to unrelated or unknown third-party hosts, but users should assume relevant account data leaves the local environment.

System checks indicate that the tool can execute code/spawn processes, which is a normal characteristic of MCP tools. The available materials do not show requests for system privileges beyond its declared purpose, nor suspicious command execution behavior, so this is rated as caution rather than high risk.

Based on the description, its primary access target is Sicredi/Open Finance account data, including balances, statements, cards, and investments, all of which are highly sensitive personal financial information. There is no indication that it needs broad local file read/write access, but the accessible account scope and consented data categories should be tightly controlled.

The supply-chain signals are relatively positive: the tool is listed in the official registry, has an auditable open-source repository, and was updated within the last year. While the missing README, unspecified license, and very low star count reduce transparency and adoption confidence, these do not by themselves constitute a high-risk red flag.