Woop MCP

The materials state that no keys or environment variables are required, and there is no indication that users must provide an API key, token, or other long-lived local credential; this keeps local credential exposure relatively low. Still, because the tool connects to a Woop financial account, users should pay attention to any session-based authorization or account-linking flow.

It is known to access the remote endpoint api.mcp.ai. Given the stated features (balances, statements, cards, investments), user-related financial data is likely transmitted through that endpoint; the materials do not describe detailed data flows, encryption specifics, or whether data is further forwarded to other services, so caution is warranted.

The system checks indicate that this MCP tool can execute code or start processes. This is a normal capability for this class of tool, and the materials do not show requests for unusual system privileges, privilege escalation, or execution behavior clearly unrelated to its stated purpose, so this is a caution rather than a high-risk finding.

The description shows that the target data scope includes Woop account balances, statements/transactions, cards, and investments, which are highly sensitive financial data. The materials do not indicate a need to read or write local files or access unrelated system resources, but account-level financial data should itself be treated as sensitive.

The source is an official registry entry and there is an auditable open-source repository with updates within the last year; these are strong positive signals. Although the repository does not declare a license and has low star count, the available materials show no high-risk supply-chain red flags such as opaque closed-source exfiltration, unknown provenance, or obvious abandonment.