Wallet and token data on 5 EVM chains

io.github.CyberPunk11147Published by GitHub account CyberPunk11147v1.6.0Updated Nov 6, 2026

Wallet balances, token prices, gas, decoded transactions and ENS on 5 EVM chains. No RPC key.

The publisher's own server: Agent.chain.tokyo Address Contracts

VerifiedSTDIODesktop onlyDatabasesFinance

Overview

AI-generated overview

Local MCP server giving an assistant wallet balances, token prices, gas, decoded transactions and ENS lookups across 5 EVM chains, without an RPC key.

What you can do
  • Look up wallet balances and token holdings across 5 EVM chains
  • Fetch token prices and current gas estimates
  • Decode transactions and resolve ENS names
  • Query a hosted chain-data service, with an optional URL override for a different endpoint
When to use it
Useful when an assistant needs on-chain EVM data — balances, prices, gas or transaction details — for analysis or support work, and you would rather not manage your own RPC provider key.
Requirements
Runs as a local stdio process from a container image, so a container runtime is needed. Network access to the default service URL, which can be overridden with CHAIN_BASE_URL. No account or RPC key is required; an optional CHAIN_X_PAYMENT secret can be supplied.
Before you install
The service is paid per request over x402: without CHAIN_X_PAYMENT the server returns a 402 invoice so the agent's own x402 client can pay and retry, which can spend funds. Queries go to a third-party host (chain.cyberwarex.com by default), so wallet addresses you look up are shared with it.

Installation

In SourceWeft

  1. Open Wallet and token data on 5 EVM chains in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

6
  1. v1.6.0LatestNov 6, 2026
  2. v1.5.0Oct 10, 2026
  3. v1.4.0Oct 9, 2026
  4. v1.3.0Oct 9, 2026
  5. v1.2.1Oct 7, 2026
  6. v1.1.0Sep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

Other Chain integrations