wallet-mcp

SUSPICIOUS: the overall footprint is broader and riskier than a simple wallet connector because it bundles many third-party plugins, transitive skill installation, external CLI execution, shared secrets, and numerous real-money/PII flows. It is not clearly malicious, but the supply-chain and credential/data-routing surface is high enough that this skill should be treated as high-risk vulnerable infrastructure rather than benign.

The fragment documents a DEX transaction workflow and contains no direct evidence of malware. It does create a significant trust boundary: wallet and operation details go to an external service, and its returned transaction data is forwarded to wallet execution with no documented independent validation. Treat the service and all returned or pasted transaction data as untrusted; verify transaction targets and effects before approval.

No clear malware behavior is present in the provided documentation. The principal risks are an embedded shared API token and reliance on API-controlled transaction data and a server-side Permit2 signature relay. Users should independently verify transaction details and typed-data authorization before signing or approving; this review cannot verify the remote service or token.