Unicred MCP

The material states no local API key or environment variable is required, which is a positive sign. However, because the tool connects to a Unicred/Open Finance account, real use likely involves account authorization tokens or session credentials. As this is tied to financial accounts, credential misuse would be sensitive, although the docs do not show any requirement for the user to provide a long-lived API key manually.

It is known to connect to the remote endpoint api.mcp.ai. Given the described features (balances, statements, cards, investments), user queries and related financial account data are likely transmitted through that endpoint. The material does not show exfiltration to unrelated or unknown domains, so this fits the normal caution level for a networked MCP tool.

The system checks indicate that this tool executes code or launches a local process, which is a standard MCP capability and implies some local execution permission. The available material does not show requests for system privileges beyond its stated purpose, so there is not enough evidence to rate this as high risk.

By description, it primarily accesses Unicred/Open Finance account data, potentially including balances, statements, cards, and investments, which are sensitive financial records. The material does not show broad read/write access to local files, arbitrary disk locations, or unrelated resources, so this looks more like purpose-bound financial data access than obvious over-privilege.

The source is an official registry entry with an auditable open-source repository and updates within the last year, all of which materially reduce supply-chain risk. Still, the missing README, undeclared license, and 0 stars indicate limited public review and adoption, so the supply-chain dimension is best rated as caution rather than fully safe.