PagBank MCP

The install spec shows no local API key or environment variable requirement, which reduces explicit secret exposure. However, because it connects to PagBank/Open Finance accounts, real usage likely involves account authorization tokens or sessions tied to highly sensitive financial data, so the authorization scope and token storage should be reviewed.

The materials explicitly indicate network access to the remote endpoint api.mcp.ai. Given the stated features (balances, statements, cards, investments), related financial account data can reasonably be expected to traverse that service path; the provided materials do not specify finer-grained data destinations, retention, or onward transfer behavior.

System checks indicate that this tool executes code or starts a local process, which is a standard MCP capability. The available materials do not show requests for unusual system privileges or clearly unrelated high-risk actions, so this should be treated as a normal execution surface with caution rather than as a high-risk indicator by itself.

Its stated access appears focused on PagBank/Open Finance account data rather than obvious local filesystem read/write. However, the data itself is highly sensitive, covering balances, statements/transactions, cards, and investments. The materials do not provide least-privilege details, field scope, or retention behavior, so authorization should be granted cautiously.

Positive factors include being listed in the official registry, having an open-source repository for inspection, and showing updates within the last year; these materially reduce supply-chain risk. Points to watch are the missing README, undeclared license, and very low community adoption (0 stars), which limit auditability and make a caution rating more appropriate than safe.