Alternative Payments

It requires ALTERNATIVE_PAYMENTS_CLIENT_ID and ALTERNATIVE_PAYMENTS_CLIENT_SECRET, which are sensitive payment-integration credentials; if exposed, they could be used to access or operate payment-related resources. The other environment variables appear to be environment/transport/logging configuration and are less sensitive.

The described functions—customers, invoices, payment requests, payouts, and webhooks—strongly imply communication with Alternative Payments-related services, but the materials do not specify the remote host, leaving the exact egress targets and scope unclear. There is no explicit evidence of exfiltration to unrelated or suspicious endpoints.

The system flags it as executes-code, meaning it runs an MCP service process locally. This is a normal capability for this class of tool; the provided materials do not show requests for system privileges beyond its stated purpose, nor any suspicious execution chain.

The materials only indicate operations on payment-platform business objects (customers, invoices, payment requests, payouts, webhooks). They do not state any need to read or write local files, databases, or unrelated user data, and no overbroad data access is evident. Based on current information, local data exposure appears limited.

It comes from an official registry and has an auditable open-source repository with updates within the last year, which are meaningful risk-reducing factors. However, the README is absent, the license is undeclared, and community adoption is minimal (0 stars), so caution is more appropriate than a high-risk rating.