RecargaPay MCP

The material explicitly states that no keys or environment variables are required, and there is no stated need for local API keys, tokens, or long-lived secrets; direct credential exposure appears low. However, because it connects to RecargaPay/Open Finance accounts, the actual account authorization scope should still be reviewed for least privilege.

It is known to access the remote endpoint api.mcp.ai, and its stated functions include balances, statements, cards, and investments, indicating that user financial data is likely transmitted over the network to the declared service. This is normal for the tool’s functionality, but the data involved is sensitive and the transmitted scope and purpose should be verified.

System checks indicate that the tool executes code/spawns a process, which is common for MCP tools. The provided material does not show requests for extra system privileges clearly unrelated to its finance-query function, so this is best rated as a normal caution-level execution capability.

By description, it can access RecargaPay/Open Finance account data such as balances, statements, cards, and investments, which is highly sensitive financial information; however, this aligns with its stated purpose. The material does not indicate local file reads, disk writes, or requests for data permissions beyond the declared scope.

The source is an official registry entry and there is an open-source repository available for audit, with updates within the last year—these are strong positive signals. While the low star count and undeclared license reduce maturity and licensing clarity, they are not sufficient on their own to make this high risk.