Rico MCP

The materials state that no local environment variables or API keys are required, which is a positive sign. However, because the tool connects to Rico/Open Finance accounts, practical use will likely still involve account authorization tokens, sessions, or OAuth-style credentials, which are highly sensitive in a financial context.

It is known to access the remote endpoint api.mcp.ai. Based on the stated functionality, user financial data such as balances, statements, cards, and investments will likely be transmitted through this endpoint. No unrelated or clearly suspicious egress endpoint is shown, but the network transmission itself warrants caution.

The system checks indicate this tool has executes-code capability, meaning it runs related code/processes locally as part of its MCP behavior. This is a normal property for such tools; with no detailed README available, there is no clear sign of system permissions beyond its stated purpose, but it should still be run in a constrained environment.

Per the description, the tool can access Rico/Open Finance balances, statements, card, and investment information, which is highly sensitive data. The materials do not specify local file read/write scope or excessive local data permissions, so the main concern is the financial account data access itself, and least-privilege access should be enforced.

The source is the official registry, and there is an open-source repository with updates within the last year, which are positive risk-reducing signals. However, the absence of a README, no declared license, and 0 community stars mean the audit context and community validation remain limited, so the supply-chain dimension is better rated as caution rather than high risk.