io.github.CSOAI-ORG/agent-commerce-protocol-mcp

The material explicitly states that no keys or environment variables are required. No API key, OAuth token, or local credential request is disclosed, so the credential collection and leakage surface appears relatively small.

System checks confirm outbound access to the remote endpoint api.meok.ai. As a payment-bridging MCP, user input or transaction-related data may be sent to that declared endpoint; however, no README or data-flow description is provided, so the scope of egress is not transparent and deserves caution.

The system indicates it has executes-code capability, meaning it runs and executes code locally as an MCP tool process. This is a normal property for such tools; the material does not show excessive privileges beyond its stated purpose, but it should still be treated as a local code-executing component.

The material does not specify which local files, databases, or system resources it reads or writes, and no explicit overbroad permission request is shown. Because it runs locally as an MCP process, it may access host-provided context and business data in principle, but the least-privilege boundary is not documented.

Positive factors include an official registry source, open-source availability, and updates within the last year, all of which reduce supply-chain risk. Points of caution are the missing README, unspecified license, and very low community adoption (0 stars), so auditability exists but maturity and external validation are limited.