Banco PAN MCP

The material states that no separate keys or environment variables are required, and there is no indication that users must provide local API keys, tokens, or system credentials. However, the banking use case may still involve bank-side authorization flows, so account authentication data should not be exposed in chat.

It is known to connect to the remote endpoint api.mcp.ai. Given its stated functions (balances, statements, cards, investments, etc.), user queries and related financial data are likely transmitted through that endpoint; this is typical for a cloud-backed financial integration tool, but data handling and retention should be verified.

The system checks indicate that it executes code/spawns a process, which is a normal operating model for MCP tools. The material does not show requests for system privileges beyond its stated purpose, nor any suspicious command execution or privilege escalation behavior.

Based on the description, its primary access target is Banco PAN Open Finance account data, potentially including balances, statements, cards, and investments. There is no stated broad local file read/write access or access to unrelated resources, but the financial data itself is sensitive, so least-privilege access is advisable.

It comes from an official registry, has a public source repository, and was updated within the last year, all of which are strong risk-reducing factors. Although the license is not declared and community stars are low, the available material is sparse and does not show closed-source exfiltration, an unknown origin, or obvious supply-chain red flags.