Paytoll

27 tools for DeFi, DEX swaps, cross-chain bridges, Twitter/X, on-chain token data, crypto utilities, and LLM access via x402 micro-payments on Base. No API keys needed — payment is the auth.

This skill is plausible for pay-per-call DeFi tools, but exercise caution: 1) The SKILL.md requires a PRIVATE_KEY and node and instructs running an npx package at runtime — npx will fetch and execute remote code, so do not expose your main wallet key. 2) Use a dedicated, funded-with-minimal-amounts wallet (as advised) or a read-only / watch-only signer when possible. 3) Before enabling the skill, review the npm package and the linked GitHub repo to confirm that signing is done locally and nothing is exfiltrated; prefer a pinned package version or running audited code locally rather than npx -y fetching latest. 4) Because the registry metadata contradicted the SKILL.md, ask the publisher to clarify and provide a reproducible install and package integrity info (exact npm package version / checksum). 5) If you must test, do so in an isolated environment or VM with a throwaway wallet. If you want help auditing the linked GitHub or npm package, provide the package name/version and I can list the files/entry points to check.

Type: OpenClaw Skill Name: paytoll Version: 1.0.8 The skill bundle is classified as suspicious due to its high-risk execution model and reliance on external, dynamically loaded components. It executes `npx -y paytoll-mcp`, which downloads and runs a third-party package from npm, posing a significant supply chain risk. This package is granted access to the user's `PRIVATE_KEY` environment variable, which, despite claims of local-only usage for micro-payments, introduces a critical trust dependency. Furthermore, the skill states that the 'MCP server discovers tools dynamically from the API,' meaning the agent's capabilities can change without explicit review of the skill bundle, potentially introducing new, unvetted functionalities. The `SKILL.md` file contains these instructions and requirements.