XP MCP

The materials indicate no separate API key or environment variables are required, and there is no sign that users must directly provide local long-lived secrets; however, the functionality inherently involves XP/Open Finance account authorization, so any related financial authorization tokens remain highly sensitive and should not be granted longer than necessary.

It is known to connect to the remote endpoint api.mcp.ai; based on the stated functionality, account queries and related financial data will likely be transmitted through that service. Network egress to its declared endpoint is a normal capability for this type of tool, but the high sensitivity of the data means the actual data flow and privacy policy should be verified.

System checks indicate that the tool can execute code/start processes. For MCP tools this is a standard operational characteristic, and the provided materials do not show requests for extra system privileges unrelated to its financial-query purpose, so this is rated as caution rather than risk.

The description explicitly covers balances, statements, cards, and investment information, which are highly sensitive personal financial data. The materials do not specify local file read/write scope, nor do they show obviously excessive data permissions beyond the stated function; the main concern is the broad visibility into account data once connected, so least-privilege access should be enforced.

Positive signals include an official registry source, visible source code, and updates within the last year; these materially reduce supply-chain risk. Points of caution are the missing README, undeclared license, and low community adoption (0 stars), which limit audit context and external validation, so the overall rating remains caution.