io.github.CyberPunk11147/cyberwarex-chain-data
OCI · GHCR.IO/CYBERPUNK11147/CYBERWAREX-CHAIN-DATA
EVM onchain data: wallet, token, price, gas, transactions, ENS across 5 chains.
Available components
Last scanned (9 hours ago)
Scores higher than 65% of OCI servers
Category Crypto and Web3
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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 294 tokens (~49/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
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.
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed oci/ghcr.io/cyberpunk11147/cyberwarex-chain-data@1.5.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 →
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 →
chain_ens ~42
Resolve an ENS name to an address (and reverse records). $0.003 via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | e.g. vitalik.eth |
No output schema declared.
No examples provided.
chain_gas ~36
Current gas market for a chain. $0.002 via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Target chain (default base) |
No output schema declared.
No examples provided.
chain_price ~47
Spot USD price for a symbol (e.g. 'eth') or token address. $0.002 via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Symbol or 0x token address |
No output schema declared.
No examples provided.
chain_token ~64
ERC-20 token profile: on-chain metadata plus live DEX market data (USD price, liquidity, 24h volume, top pair). $0.004 via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | Target chain (default base) |
No output schema declared.
No examples provided.
chain_tx ~41
Decoded transaction by hash. $0.003 via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Target chain (default base) |
| hash | string | yes | – |
No output schema declared.
No examples provided.
chain_wallet ~64
Wallet snapshot on any major EVM chain: native balance, USDC balance, transaction count, contract-or-EOA flag, USD values. $0.003 via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | Target chain (default base) |
No output schema declared.
No examples provided.
How do I install the io.github.CyberPunk11147/cyberwarex-chain-data MCP server?
io.github.CyberPunk11147/cyberwarex-chain-data runs locally as a container image, launched with docker run --rm -i -e CHAIN_X_PAYMENT -e CHAIN_BASE_URL ghcr.io/cyberpunk11147/cyberwarex-chain-data:1.5.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-chain-data
claude mcp add cyberpunk11147-cyberwarex-chain-data -- docker run --rm -i -e CHAIN_X_PAYMENT -e CHAIN_BASE_URL ghcr.io/cyberpunk11147/cyberwarex-chain-data:1.5.0
This image reads CHAIN_X_PAYMENT and CHAIN_BASE_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the io.github.CyberPunk11147/cyberwarex-chain-data MCP server?
io.github.CyberPunk11147/cyberwarex-chain-data is an MCP server listed in the public MCP registry as io.github.CyberPunk11147/cyberwarex-chain-data. EVM onchain data: wallet, token, price, gas, transactions, ENS across 5 chains. This page covers its container image (ghcr.io/cyberpunk11147/cyberwarex-chain-data).
Is the io.github.CyberPunk11147/cyberwarex-chain-data MCP server safe to use?
io.github.CyberPunk11147/cyberwarex-chain-data scores 46 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-chain-data MCP server expose?
io.github.CyberPunk11147/cyberwarex-chain-data exposes 6 tools: chain_wallet, chain_token, chain_price, chain_gas, chain_tx, chain_ens. Their descriptions and schemas cost roughly 294 tokens of context every time the server is loaded.
Is the io.github.CyberPunk11147/cyberwarex-chain-data MCP server still maintained?
io.github.CyberPunk11147/cyberwarex-chain-data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.