Stone Pagamentos MCP

The materials state that no extra keys or environment variables are required, and there is no explicit request for API tokens, passwords, or long-lived credentials. This reduces credential exposure, though any real Open Finance connection may still involve runtime authorization tokens.

It is known to connect to the remote endpoint api.mcp.ai. Based on the stated functionality, financial data such as balances, statements, and card information may be transmitted through that endpoint. This is a normal property of connected tools, but the sensitivity of the data warrants verification of the endpoint’s relationship to the Stone/Open Finance integration and its data handling.

System checks indicate that the tool executes code or starts a local process, which is standard behavior for MCP tools. The materials do not show requests for unusual system privileges or execution capabilities beyond its stated finance-connection purpose, so caution is appropriate.

Based on the description, the intended data scope includes account balances, statements/transaction history, and card information, all of which are highly sensitive financial data. The materials do not specify local file access or clearly indicate overbroad permissions; the main concern is access to account data itself rather than any known abnormal local data permissions.

The source is an official registry entry and an open-source repository is provided, with updates within the last year; these are meaningful risk-reducing signals. While the repository lacks a declared license and has very low star count, that affects maturity and reuse confidence more than security severity, and does not by itself justify a high-risk rating given the auditability and relatively trustworthy source.