C6 Bank MCP

The materials state that no keys or environment variables are required, and there is no indication that users must provide a local API key or long-lived secret; however, if banking authorization tokens are used, they would still be highly sensitive, and the documentation does not explain how they are handled.

It is known to connect to the remote endpoint api.mcp.ai; given the stated functionality, account balances, statements, card, or investment query data is likely transmitted through that endpoint. Only a single declared endpoint is visible, with no clear red flag of exfiltration to unrelated or unknown hosts.

System checks indicate that this tool executes code or starts a local process, which is a common MCP behavior; the available materials do not show requests for system privileges beyond its stated purpose, nor do they disclose additional dangerous system capabilities.

Its stated capabilities cover C6 Bank balances, statements, cards, and investments, which are highly sensitive financial data; however, the materials do not show arbitrary local file access, disk writes, or access to unrelated data resources, so the current scope appears closer to functionally necessary data access.

The source is an official registry entry and has an auditable open-source repository with updates within the last year, all of which are positive signals; however, community adoption is very low (0 stars), the license is undeclared, and the README is missing, leaving limited audit context and maturity, so cautious validation is recommended before use.