Cyberwarex Wallet Safety MCP server
Pre-sign wallet safety: tx simulation, signature decoding, address risk, ABI, URL phishing.
B73/100grade B
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Cyberwarex Wallet Safety yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Cyberwarex Wallet Safety tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 7 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add cyberwarex-wallet-safety -- docker run -i --rm ghcr.io/cyberpunk11147/cyberwarex-wallet-safety:1.1.0
Cyberwarex Wallet Safety: common questions
- Is Cyberwarex Wallet Safety MCP server safe?
- Mostly: it is graded B (73/100). Read the Cyberwarex Wallet Safety safety report
- How do I install Cyberwarex Wallet Safety?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Cyberwarex Wallet Safety need an API key?
- Yes. The registry entry asks for
CWX_X_PAYMENT. - Is Cyberwarex Wallet Safety maintained?
- The last commit was 8 days ago (2026-09-12). The latest release is v1.1.0.