dev.true402/mcp-server

It requires WALLET_PRIVATE_KEY, SERVER_URL, and MAX_PAYMENT_USDC; the wallet private key is a highly sensitive credential, and leakage or misuse could directly lead to on-chain asset loss. The materials do not explain how the key is used, stored, or scoped for signing, creating a clear credential abuse risk.

Although no fixed remote host is listed, the presence of SERVER_URL and the stated pay-per-call AI, web, and on-chain functions imply network communication. The materials do not disclose the actual destinations, data types transmitted, or whether user content is sent out, so data egress boundaries require caution, but this alone is insufficient for a high-risk rating.

The system checks indicate that this tool executes code/spawns processes, which is a common MCP capability. The current materials do not show it requesting clearly excessive system privileges beyond its stated purpose, but the lack of documentation leaves its exact local execution scope opaque.

The materials do not specify what local files, session data, or on-chain related data it can read or write, so minimum-privilege boundaries cannot be verified. There is no explicit evidence of overbroad access, but given its AI, web, and on-chain functions, it should be treated cautiously as potentially handling user inputs, outputs, and payment-related data.

Positive factors include its presence in the official registry and recent updates within the last year; however, there is no open-source repository, no declared license, no README, and very low community adoption, leaving the implementation unauditable. Source trust mitigates risk somewhat, but there is still clear supply-chain opacity.