mcpField
C
cyberwarex-wallet-safety

cyberwarex-wallet-safety

Local
cyberwarex.comSecurity0Updated 1w ago
RepositoryVisit website

About cyberwarex-wallet-safety

Pre-sign wallet safety: tx simulation, signature decoding, address risk, ABI, URL phishing

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cyberpunk11147-cyberwarex-wallet-safety": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CWX_X_PAYMENT",
        "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.5.0"
      ],
      "env": {
        "CWX_X_PAYMENT": "<CWX_X_PAYMENT>"
      }
    }
  }
}
Run commanddocker run -i --rm -e CWX_X_PAYMENT ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.5.0
Environment variables to set
CWX_X_PAYMENTSecretOptional x402 X-PAYMENT header. If unset, the server uses each service's free trial (3 calls/day) and then surfaces the 402 invoice to the agent so its own x402 client can pay and retry.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.5.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.