Dock MCP

The materials state that no standalone environment variables or API keys are required, which reduces explicit secret exposure. However, the tool’s purpose is to connect a Dock account and access balances, statements, cards, and investments, so real-world use likely still involves account authorization or session tokens tied to sensitive financial accounts; the authorization scope and token handling should be reviewed.

It is declared to contact api.mcp.ai; given the stated functionality, financial account query data is likely transmitted through that endpoint. The egress target is a declared endpoint rather than an obviously unrelated destination, so no abnormal exfiltration red flag is apparent, but the sensitivity of the data warrants checking what is sent, whether it is minimized, and the server-side retention policy.

The system checks indicate that the tool executes code or starts processes, which is a normal capability for MCP tools. The available materials do not show it invoking system capabilities beyond its stated purpose or requesting unusually broad privileges, so this is a caution rather than a high-risk finding.

Per the description, its primary data access scope is Dock/Open Finance account information, including balances, statements, cards, and investments, which is highly sensitive financial data. There is no explicit indication that it reads or writes local files or accesses unrelated resources, but because the reachable data is inherently sensitive, it should be used only with necessary accounts and the minimum authorization scope.

The tool comes from the official registry and is open-source with updates within the last year, all of which are clear positive signals that reduce supply-chain risk. However, community adoption is currently very low (0 stars), the README is absent, and no license is declared, leaving limited audit context and unclear usage constraints, so a caution rating is appropriate.