# io.github.CyberPunk11147/cyberwarex-wallet-safety (oci · ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0) Pre-sign wallet safety: tx simulation, signature decoding, address risk, ABI, URL phishing. - Trust score: 44/100 (low) - Change this week: +5 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - oci · `ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0`: 44/100 (this document), [markdown](https://verifymcp.io/servers/cyberpunk11147-cyberwarex-wallet-safety/ghcr-io-cyberpunk11147-cyberwarex-wallet-safety-1-1-0.md), [page](https://verifymcp.io/servers/cyberpunk11147-cyberwarex-wallet-safety/ghcr-io-cyberpunk11147-cyberwarex-wallet-safety-1-1-0) ## Channel facts - Registry: `oci` - Package: `ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-20. - **Supply Chain Security**: 0/100 - Malware scan not yet available for this package. - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it. - **Provenance & Transparency**: 32/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - License check failed: no license is declared. - Actively maintained (last published 10 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 82/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 744 tokens (~124/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 33/100 - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). **Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the io.github.CyberPunk11147/cyberwarex-wallet-safety MCP server? io.github.CyberPunk11147/cyberwarex-wallet-safety runs locally as a container image, launched with docker run --rm -i ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add cyberpunk11147-cyberwarex-wallet-safety -- docker run --rm -i ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0 ``` ### Cursor ```json { "mcpServers": { "cyberpunk11147-cyberwarex-wallet-safety": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0" ] } } } ``` ### VS Code ```json { "servers": { "cyberpunk11147-cyberwarex-wallet-safety": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0" ] } } } ``` ### Codex ```bash codex mcp add cyberpunk11147-cyberwarex-wallet-safety -- docker run --rm -i ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "cyberpunk11147-cyberwarex-wallet-safety": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: cyberpunk11147-cyberwarex-wallet-safety: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0"] ``` ### Netclaw ```json { "McpServers": { "cyberpunk11147-cyberwarex-wallet-safety": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0" ] } } } ``` ### Other ```json { "mcpServers": { "cyberpunk11147-cyberwarex-wallet-safety": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-20 (score 44, +1) No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-18 (score 43, +4) - [functional improvement] Stability: unverified → 0.27 ### 2026-09-10 (score 39) First indexed and scored. ## MCP tools (6) ### `simulate_transaction` (~196 tokens) Simulate an unsigned EVM transaction BEFORE signing it: decodes the function and arguments, flags dangerous actions (unlimited token approvals, setApprovalForAll, ownership transfers, native-value drains) and runs a keyless eth_call preview that says whether it would succeed or revert. Base, BSC, Ethereum, Polygon, Arbitrum, Optimism. Deterministic, read-only. Call this on every transaction a wallet or trading agent is about to sign. Input parameters: - `chain` (string): Chain: base (default), bsc, ethereum, polygon, arbitrum, optimism - `data` (string): Hex calldata (0x…), empty for a plain value transfer - `from` (string): Sender address used for the eth_call preview (optional) - `to` (string, required): Destination address (0x…) - `value` (string): Native value in wei as a decimal or hex string (default 0) ### `decode_calldata` (~80 tokens) Decode raw EVM calldata into a named function, signature and arguments plus the same security risk flags as simulate_transaction, without running the simulation (cheaper). Use when you only need to know WHAT a transaction does. Input parameters: - `data` (string, required): Hex calldata (0x…) - `to` (string): Target contract address, improves decoding (optional) ### `decode_signature_request` (~128 tokens) Decode an off-chain SIGNATURE REQUEST (EIP-712 typed data or a personal_sign message) into a plain summary with risk level and drainer flags: Permit / Permit2 / DAI permit token approvals, Seaport and other marketplace listings, unlimited amounts, far-future deadlines, unknown spenders. Call this before signing anything a dapp asks for. Input parameters: - `message` (string): personal_sign message text or hex (use instead of typed_data) - `typed_data` (string): EIP-712 typed data as a JSON string (domain, types, primaryType, message) ### `address_risk` (~143 tokens) Screen an EVM wallet or contract address BEFORE paying or interacting with it: OFAC sanctions lists, taint from known-bad addresses and (deep=true) CyberWareX's own scam/rug deployer ledger. Returns BLOCK / REVIEW / ALLOW with reasons and a 0-100 risk score. Input parameters: - `address` (string, required): Wallet or contract address (0x…) - `chain` (string): Chain: base (default), bsc, ethereum, polygon, arbitrum, optimism - `deep` (boolean): true = full risk report incl. scam-deployer ledger (/risk); false = sanctions + taint screen only (/screen, cheaper) ### `contract_abi` (~93 tokens) Fetch a verified contract's ABI keylessly (from Sourcify): full ABI, function and event signatures/selectors, contract name and proxy detection (implementation address). Use it to encode calls or to understand what a contract can do. Input parameters: - `address` (string, required): Contract address (0x…) - `chain` (string): Chain: base (default), bsc, ethereum, polygon, arbitrum, optimism ### `url_safety` (~104 tokens) Score a URL for phishing risk before an agent opens, trusts or sends funds through it: typosquats of known brands, homoglyph/punycode domains, credentials in the URL, raw IP hosts, risky TLDs, suspicious subdomain depth and domain age (RDAP). Returns SAFE / SUSPICIOUS / DANGEROUS with a 0-100 score and reasons. Input parameters: - `url` (string, required): Full URL to check (https://…) ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cyberpunk11147-cyberwarex-wallet-safety/ghcr-io-cyberpunk11147-cyberwarex-wallet-safety-1-1-0#diagnostics ## Score history - 2026-09-20: 44 - 2026-09-19: 43 - 2026-09-18: 43 - 2026-09-17: 39 - 2026-09-16: 39 - 2026-09-15: 39 - 2026-09-14: 39 - 2026-09-13: 39 - 2026-09-12: 39 - 2026-09-11: 39 - 2026-09-10: 39 ## Common questions ### What is the io.github.CyberPunk11147/cyberwarex-wallet-safety MCP server? io.github.CyberPunk11147/cyberwarex-wallet-safety is an MCP server listed in the public MCP registry as io.github.CyberPunk11147/cyberwarex-wallet-safety. Pre-sign wallet safety: tx simulation, signature decoding, address risk, ABI, URL phishing. This page covers its container image (ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0). ### Is the io.github.CyberPunk11147/cyberwarex-wallet-safety MCP server safe to use? io.github.CyberPunk11147/cyberwarex-wallet-safety scores 44 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the io.github.CyberPunk11147/cyberwarex-wallet-safety MCP server expose? io.github.CyberPunk11147/cyberwarex-wallet-safety exposes 6 tools: simulate_transaction, decode_calldata, decode_signature_request, address_risk, contract_abi, url_safety. Their descriptions and schemas cost roughly 744 tokens of context every time the server is loaded. ### Is the io.github.CyberPunk11147/cyberwarex-wallet-safety MCP server still maintained? io.github.CyberPunk11147/cyberwarex-wallet-safety is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Repository: https://github.com/CyberPunk11147/cyberwarex-mcp - Website: https://cyberwarex.com/ - Changelog RSS feed: https://verifymcp.io/servers/cyberpunk11147-cyberwarex-wallet-safety/ghcr-io-cyberpunk11147-cyberwarex-wallet-safety-1-1-0.xml - Changelog JSON feed: https://verifymcp.io/servers/cyberpunk11147-cyberwarex-wallet-safety/ghcr-io-cyberpunk11147-cyberwarex-wallet-safety-1-1-0.json - HTML version of this page: https://verifymcp.io/servers/cyberpunk11147-cyberwarex-wallet-safety/ghcr-io-cyberpunk11147-cyberwarex-wallet-safety-1-1-0