Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CyberPunk11147/cyberwarex-wallet-safety

OCI · GHCR.IO/CYBERPUNK11147/CYBERWAREX-WALLET-SAFETY:1.1.0 · SCANNED SEP 20

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

+5 this week 44 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • 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.Unverified
  • Install-script risk not yet assessed.Unverified
  • 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.Unverified
Provenance & Transparency32
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

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.

oci · ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0

# add to Claude Code
claude mcp add cyberpunk11147-cyberwarex-wallet-safety -- docker run --rm -i ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0
// .cursor/mcp.json
{
  "mcpServers": {
    "cyberpunk11147-cyberwarex-wallet-safety": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cyberpunk11147-cyberwarex-wallet-safety": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0"
      ]
    }
  }
}
# add to Codex CLI
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/config.yaml
mcp_servers:
  cyberpunk11147-cyberwarex-wallet-safety:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cyberpunk11147-cyberwarex-wallet-safety": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "cyberpunk11147-cyberwarex-wallet-safety": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +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.

  • 18 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 10 Sept 26 39

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed oci/ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 6 exposed · ~744 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
address_risk ~143

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.

NameTypeReqDescription
addressstringyesWallet or contract address (0x…)
chainstringChain: base (default), bsc, ethereum, polygon, arbitrum, optimism
deepbooleantrue = full risk report incl. scam-deployer ledger (/risk); false = sanctions + taint screen only (/screen, cheaper)

No output schema declared.

No examples provided.

contract_abi ~93

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.

NameTypeReqDescription
addressstringyesContract address (0x…)
chainstringChain: base (default), bsc, ethereum, polygon, arbitrum, optimism

No output schema declared.

No examples provided.

decode_calldata ~80

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.

NameTypeReqDescription
datastringyesHex calldata (0x…)
tostringTarget contract address, improves decoding (optional)

No output schema declared.

No examples provided.

decode_signature_request ~128

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.

NameTypeReqDescription
messagestringpersonal_sign message text or hex (use instead of typed_data)
typed_datastringEIP-712 typed data as a JSON string (domain, types, primaryType, message)

No output schema declared.

No examples provided.

simulate_transaction ~196

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.

NameTypeReqDescription
chainstringChain: base (default), bsc, ethereum, polygon, arbitrum, optimism
datastringHex calldata (0x…), empty for a plain value transfer
fromstringSender address used for the eth_call preview (optional)
tostringyesDestination address (0x…)
valuestringNative value in wei as a decimal or hex string (default 0)

No output schema declared.

No examples provided.

url_safety ~104

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.

NameTypeReqDescription
urlstringyesFull URL to check (https://…)

No output schema declared.

No examples provided.

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.