$THREE Token

It requires environment variables including SOLANA_SECRET_KEY, SOLANA_RPC_URL, and THREE_WS_BASE. SOLANA_SECRET_KEY is highly sensitive because exposure could allow direct on-chain transactions or token burns; MAX_BURN_USD and REQUIRE_CONFIRM are control parameters rather than secrets, but they materially affect transaction safety.

No fixed remote host is listed, but SOLANA_RPC_URL and THREE_WS_BASE indicate it will connect to user-configured Solana RPC/WebSocket endpoints for queries and transaction submission. There is no explicit red flag showing exfiltration to unrelated or unknown third-party endpoints, though network egress is inherent to its function.

The system marks it as executes-code, meaning it runs local service/code to handle MCP requests and likely uses network and signing capabilities for on-chain actions. The available material does not show requests for system privileges clearly beyond its stated purpose, so this remains a standard caution case.

It will at minimum read environment-based private key and endpoint configuration, and process wallet/holding/burn-related data. The material does not state that it broadly accesses local files, user directories, or unrelated resources, and no obvious overbroad authorization is described; however, it should be assumed to handle transaction-sensitive data.

Positive indicators include listing in the official registry, an open-source repository available for review, and updates within the last year, all of which reduce supply-chain risk. Still, the README is effectively absent, the license is undeclared, and community adoption is very low (0 stars), so audit context and external validation remain limited; it should not be treated as fully low risk.