three.ws Agent Wallet

The material states that no keys or environment variables are required, and no explicit API token dependency is shown. However, the tool's purpose is wallet and USDC payments, so any generated, imported, or stored wallet signing material or account data would still be highly sensitive. With no README, credential handling is not transparent, so it should be treated as a sensitive wallet component.

The tool is known to access the remote endpoint three.ws, and the description explicitly mentions discovering and paying for services, indicating network interactions for service discovery and payment flows. The available material does not specify what user data, transaction metadata, or wallet identifiers are transmitted, so there is a normal outbound data exposure surface and the transmitted scope should be verified.

The system checks indicate that this tool executes code, which is a common MCP pattern involving local process startup or runtime logic. The current description does not show requests for unusual system privileges or a suspicious execution chain, so this should be treated as standard code-execution capability with caution.

Given its 'agent wallet' and payment purpose, the tool may need access to local wallet state, transaction records, or configuration data, but the material does not define the exact files, directories, or data resources it can read or write. There is no explicit evidence of overbroad access, but the data access boundary is unclear, especially for any locally persisted wallet-related information.

Positive signals include an official registry source, an auditable open-source repository, and updates within the last year, all of which materially reduce supply-chain risk. Points to watch are the missing README, undeclared license, and very low community adoption (0 stars), which limit external review and maturity signals, making this more of a moderate caution than a high-risk case.