io.github.2s-io/mcp

It requires EVM_PRIVATE_KEY, which is a highly sensitive credential; if leaked or misused, it could enable on-chain signing, payments, or asset loss. The materials only indicate it is used for x402/USDC settlement, without explaining key handling, least-privilege controls, or support for constrained wallets.

The description indicates calls to the “2s everything API” with pay-per-call settlement, so external network communication is expected; however, the materials do not disclose specific remote endpoints or the scope of transmitted data. There is no evidence of obviously unrelated or suspicious destinations, but the egress boundary is not very transparent.

The system checks indicate that this tool executes code / launches local processes, which is a standard MCP capability and merits caution. The provided materials do not show requests for system privileges clearly disproportionate to its stated purpose, but they also do not detail the exact system capabilities it may invoke.

The materials do not declare broad file read/write scope, but local execution typically implies access at least to tool inputs, environment variables, and payment-related key material. There is no explicit sign of overbroad authorization, yet the actual access boundary to local data, wallet information, and request contents is not fully disclosed.

Positive factors include its presence in the official Registry, an available open-source repository, and updates within the last year, all of which reduce supply-chain risk. Caution remains because the README is absent, the license is unspecified, and community adoption is very low (0 stars), leaving limited audit context and external validation.