three.ws 3D Agent Tools

It requires MCP_SVM_PAYMENT_ADDRESS, SOLANA_RPC_URL, and HELIUS_API_KEY. HELIUS_API_KEY and any payment-/wallet-related address are sensitive configurations; exposure could enable quota abuse, billing/privacy leakage, or unauthorized on-chain use, although the materials show no explicit credential-stealing behavior.

No fixed remote hosts are listed, but SOLANA_RPC_URL, HELIUS_API_KEY, and the description of “Paid x402 MCP tools from three.ws” imply outbound access to the configured Solana RPC/Helius services and related service infrastructure. The exact endpoints and data sent are not documented, so transparency is limited, but there is no clear evidence of exfiltration to unrelated or suspicious destinations.

The system flags executes-code, indicating the tool can run code/processes in the local environment. This is a common MCP capability and not inherently high risk, but it should be run with least privilege and in an isolated execution environment.

The README is absent and does not clearly describe what local files, working directories, or generated asset locations it can access. Given its 3D generation/rigging features, it likely handles user inputs and generated outputs at minimum. There is no explicit sign of overbroad authorization, but the data access boundary is insufficiently documented.

It comes from an official registry entry and has public source code with updates within the last year, which are meaningful risk-reducing signals. However, the license is unspecified, community adoption is very low (0 stars), and documentation is sparse, limiting confidence in auditability and maturity; caution is more appropriate than safe.