Pague Veloz Serasa MCP

The materials state that no environment variables or API keys are required, which is a positive sign. However, because the tool connects to a Pague Veloz Serasa/Open Finance account, it will likely still handle account authorization tokens or session data in practice. Misuse of such credentials could expose financial data, so authorization scope and login flow should be reviewed carefully.

The tool is known to access the remote endpoint api.mcp.ai, and its description indicates it retrieves balances, statements, and card information, so user financial data is likely transmitted through that endpoint. No obviously unrelated or suspicious domain is shown, but data egress is not purely local, so its privacy policy and data-handling boundaries should be verified.

The system flags it as having executes-code capability, meaning it runs as a local MCP tool process or executes code on the host. This is a normal tool capability, and the materials do not show requests for system privileges that are clearly excessive for its stated purpose, so this is rated caution rather than risk.

By its stated function, the tool accesses highly sensitive financial data, including balances, statements/transactions, and card information. The materials do not specify which local files it reads or writes, and no clear overbroad authorization is evident; however, because the data itself is highly sensitive, account access should be minimized.

Positive factors include that it is from the official registry, open-source, and updated within the past year, giving it a meaningful level of auditability and lowering supply-chain risk. Points to watch are the very low community adoption (0 stars) and the absence of a declared license, so overall this dimension is rated caution.