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.

Agent Data Tools: Chain data

Owner verified

REMOTE · AGENT-DATA-TOOLS.REVMESH2074.WORKERS.DEV

64 tools: balances, blocks, gas, txs and logs on 5 EVM chains, plus Bitcoin. 25 free calls.

70 Trust /100

Last scanned (3 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security69
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 12604 tokens (~196/item across 64 items; 64 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 Management13
  • Stability observed for 4 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
  • Structured output schemas are declared (2% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 64 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 65 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 22 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “op_is_contract” rewrote its description, which is the text the model reads security
    • Tool “arb_balance” rewrote its description, which is the text the model reads security
    • Tool “arb_block” rewrote its description, which is the text the model reads security
    • Tool “arb_gas” rewrote its description, which is the text the model reads security
    • Tool “arb_is_contract” rewrote its description, which is the text the model reads security
    • Tool “arb_logs” rewrote its description, which is the text the model reads security
    • Tool “arb_nonce” rewrote its description, which is the text the model reads security
    • Tool “arb_receipt” rewrote its description, which is the text the model reads security
    • Tool “arb_token_balance” rewrote its description, which is the text the model reads security
    • Tool “arb_token_info” rewrote its description, which is the text the model reads security
    • Tool “arb_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “base_balance” rewrote its description, which is the text the model reads security
    • Tool “base_block” rewrote its description, which is the text the model reads security
    • Tool “base_is_contract” rewrote its description, which is the text the model reads security
    • Tool “base_logs” rewrote its description, which is the text the model reads security
    • Tool “base_nonce” rewrote its description, which is the text the model reads security
    • Tool “base_receipt” rewrote its description, which is the text the model reads security
    • Tool “base_token_balance” rewrote its description, which is the text the model reads security
    • Tool “base_token_info” rewrote its description, which is the text the model reads security
    • Tool “base_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “btc_address” rewrote its description, which is the text the model reads security
    • Tool “ens” rewrote its description, which is the text the model reads security
    • Tool “eth_balance” rewrote its description, which is the text the model reads security
    • Tool “eth_block” rewrote its description, which is the text the model reads security
    • Tool “eth_gas” rewrote its description, which is the text the model reads security
    • Tool “eth_is_contract” rewrote its description, which is the text the model reads security
    • Tool “eth_logs” rewrote its description, which is the text the model reads security
    • Tool “eth_nonce” rewrote its description, which is the text the model reads security
    • Tool “eth_receipt” rewrote its description, which is the text the model reads security
    • Tool “eth_token_balance” rewrote its description, which is the text the model reads security
    • Tool “eth_token_info” rewrote its description, which is the text the model reads security
    • Tool “eth_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “keccak” rewrote its description, which is the text the model reads security
    • Tool “ln_invoice” rewrote its description, which is the text the model reads security
    • Tool “network” rewrote its description, which is the text the model reads security
    • Tool “op_balance” rewrote its description, which is the text the model reads security
    • Tool “op_block” rewrote its description, which is the text the model reads security
    • Tool “op_gas” rewrote its description, which is the text the model reads security
    • Tool “op_logs” rewrote its description, which is the text the model reads security
    • Tool “op_nonce” rewrote its description, which is the text the model reads security
    • Tool “op_receipt” rewrote its description, which is the text the model reads security
    • Tool “op_token_balance” rewrote its description, which is the text the model reads security
    • Tool “op_token_info” rewrote its description, which is the text the model reads security
    • Tool “op_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “polygon_balance” rewrote its description, which is the text the model reads security
    • Tool “polygon_block” rewrote its description, which is the text the model reads security
    • Tool “polygon_gas” rewrote its description, which is the text the model reads security
    • Tool “polygon_is_contract” rewrote its description, which is the text the model reads security
    • Tool “polygon_logs” rewrote its description, which is the text the model reads security
    • Tool “polygon_nonce” rewrote its description, which is the text the model reads security
    • Tool “polygon_receipt” rewrote its description, which is the text the model reads security
    • Tool “polygon_token_balance” rewrote its description, which is the text the model reads security
    • Tool “polygon_token_info” rewrote its description, which is the text the model reads security
    • Tool “polygon_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “polygon_tx” rewrote its description, which is the text the model reads security
    • Tool “arb_tx” rewrote its description, which is the text the model reads security
    • Tool “eth_tx” rewrote its description, which is the text the model reads security
    • Tool “op_tx” rewrote its description, which is the text the model reads security
    • Server version: 1.50.3 → 1.50.5 functional
    • Server version: 1.50.2 → 1.50.3 functional
    • Server version: 1.50.1 → 1.50.2 functional
    • Server version: 1.49.1 → 1.50.1 functional
    • Server version: 1.48.6 → 1.49.1 functional
    • Server version: 1.48.5 → 1.48.6 functional
    • Server version: 1.48.2 → 1.48.5 functional
    • Server version: 1.48.0 → 1.48.2 functional
    • Server version: 1.47.15 → 1.48.0 functional
    • Server version: 1.47.7 → 1.47.15 functional
    • Server version: 1.45.3 → 1.47.7 functional
    • Tool “wallet_balances” changed its title: Wallet balance: native and USDC balances on 5 networks → Wallet balance, USDC balance: native and USDC balances on 5 networks cosmetic
    • Tool “ens” changed its title: ENS name to address and address to ENS name → ENS name lookup: ENS name to address and address to ENS name cosmetic
  • 21 Oct 26 0
    • Server version: 1.45.1 → 1.45.3 functional
    • Server version: 1.45.0 → 1.45.1 functional
    • Server version: 1.44.0 → 1.45.0 functional
    • Tool “wallet_balances” changed its title: Native and USDC balances on 5 networks → Wallet balance: native and USDC balances on 5 networks cosmetic
  • 20 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “arb_balance” rewrote its description, which is the text the model reads security
    • Tool “arb_block” rewrote its description, which is the text the model reads security
    • Tool “arb_logs” rewrote its description, which is the text the model reads security
    • Tool “arb_receipt” rewrote its description, which is the text the model reads security
    • Tool “arb_token_balance” rewrote its description, which is the text the model reads security
    • Tool “arb_token_info” rewrote its description, which is the text the model reads security
    • Tool “arb_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “base_balance” rewrote its description, which is the text the model reads security
    • Tool “base_block” rewrote its description, which is the text the model reads security
    • Tool “base_logs” rewrote its description, which is the text the model reads security
    • Tool “base_receipt” rewrote its description, which is the text the model reads security
    • Tool “base_token_balance” rewrote its description, which is the text the model reads security
    • Tool “base_token_info” rewrote its description, which is the text the model reads security
    • Tool “base_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “eth_balance” rewrote its description, which is the text the model reads security
    • Tool “eth_block” rewrote its description, which is the text the model reads security
    • Tool “eth_logs” rewrote its description, which is the text the model reads security
    • Tool “eth_receipt” rewrote its description, which is the text the model reads security
    • Tool “eth_token_balance” rewrote its description, which is the text the model reads security
    • Tool “eth_token_info” rewrote its description, which is the text the model reads security
    • Tool “eth_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “op_balance” rewrote its description, which is the text the model reads security
    • Tool “op_block” rewrote its description, which is the text the model reads security
    • Tool “op_logs” rewrote its description, which is the text the model reads security
    • Tool “op_receipt” rewrote its description, which is the text the model reads security
    • Tool “op_token_balance” rewrote its description, which is the text the model reads security
    • Tool “op_token_info” rewrote its description, which is the text the model reads security
    • Tool “op_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “polygon_balance” rewrote its description, which is the text the model reads security
    • Tool “polygon_block” rewrote its description, which is the text the model reads security
    • Tool “polygon_logs” rewrote its description, which is the text the model reads security
    • Tool “polygon_receipt” rewrote its description, which is the text the model reads security
    • Tool “polygon_token_balance” rewrote its description, which is the text the model reads security
    • Tool “polygon_token_info” rewrote its description, which is the text the model reads security
    • Tool “polygon_token_transfers” rewrote its description, which is the text the model reads security
    • Tool “wallet” rewrote its description, which is the text the model reads security
    • Tool “arb_gas” rewrote its description, which is the text the model reads security
    • Tool “base_gas” rewrote its description, which is the text the model reads security
    • Tool “btc_fees” rewrote its description, which is the text the model reads security
    • Tool “eth_gas” rewrote its description, which is the text the model reads security
    • Tool “network” rewrote its description, which is the text the model reads security
    • Tool “op_gas” rewrote its description, which is the text the model reads security
    • Tool “polygon_gas” rewrote its description, which is the text the model reads security
    • Schema quality: 176 → 196 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.41.0 → 1.44.0 functional
    • Server version: 1.40.0 → 1.41.0 functional
    • Server version: 1.39.3 → 1.40.0 functional
    • Server version: 1.37.1 → 1.39.3 functional
    • Server version: 1.36.1 → 1.37.1 functional
    • Server version: 1.35.3 → 1.36.1 functional
    • “arb_gas” added an optional parameter “only” cosmetic
    • “base_gas” added an optional parameter “only” cosmetic
    • “btc_fees” added an optional parameter “only” cosmetic
    • “eth_gas” added an optional parameter “only” cosmetic
    • “network” added an optional parameter “only” cosmetic
    • “op_gas” added an optional parameter “only” cosmetic
    • “polygon_gas” added an optional parameter “only” cosmetic
    • “arb_gas” reworded the description of “only” cosmetic
    • “arb_token_balance” reworded the description of “token” cosmetic
    • “arb_token_info” reworded the description of “token” cosmetic
    • “arb_token_transfers” reworded the description of “blocks” cosmetic
    • “arb_token_transfers” reworded the description of “token” cosmetic
    • “base_gas” reworded the description of “only” cosmetic
    • “base_token_balance” reworded the description of “token” cosmetic
    • “base_token_info” reworded the description of “token” cosmetic
    • “base_token_transfers” reworded the description of “blocks” cosmetic
    • “base_token_transfers” reworded the description of “token” cosmetic
    • “btc_fees” reworded the description of “only” cosmetic
    • “eth_gas” reworded the description of “only” cosmetic
    • “eth_token_balance” reworded the description of “token” cosmetic
    • “eth_token_info” reworded the description of “token” cosmetic
    • “eth_token_transfers” reworded the description of “blocks” cosmetic
    • “eth_token_transfers” reworded the description of “token” cosmetic
    • “network” reworded the description of “only” cosmetic
    • “op_gas” reworded the description of “only” cosmetic
    • “op_token_balance” reworded the description of “token” cosmetic
    • “op_token_info” reworded the description of “token” cosmetic
    • “op_token_transfers” reworded the description of “blocks” cosmetic
    • “op_token_transfers” reworded the description of “token” cosmetic
    • “polygon_gas” reworded the description of “only” cosmetic
    • “polygon_token_balance” reworded the description of “token” cosmetic
    • “polygon_token_info” reworded the description of “token” cosmetic
    • “polygon_token_transfers” reworded the description of “blocks” cosmetic
    • “polygon_token_transfers” reworded the description of “token” cosmetic
  • 19 Oct 26 69

    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 23 Oct 2026 · Probed https://agent-data-tools.revmesh2074.workers.dev/mcp/chain

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=revmesh2074.workers.dev CN=YE1,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA384 538c1f22b424c14420d956229d7db3228c3
SANs: *.revmesh2074.workers.dev, revmesh2074.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agent-data-tools.revmesh2074.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent-data-tools.revmesh2074.workers.dev/mcp/chain Verified 200
http (plaintext) http://agent-data-tools.revmesh2074.workers.dev/mcp/chain Inconclusive 405
MCP tools · 64 exposed · ~12,087 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
op_tx ~203

Look up an Optimism transaction by hash: sender, recipient, value in ETH, nonce, gas limit, the 4-byte function selector and its block. Use to see what was sent or whether it exists; for success or failure and fees paid use op_receipt, for emitted events op_logs. Input is a 0x-prefixed 64-hex hash; an unknown hash returns 404, uncharged. Example: hash=0x721f3e9a996da49e2a8929bd2dd42e0f51344c11d7ca7bc3328fda349cdfae89. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
hashstringyes0x-prefixed transaction hash (64 hex characters)

No output schema declared.

No examples provided.

polygon_balance ~177

Native POL balance (eth_getBalance) of any 0x wallet address on Polygon PoS at the latest block, in wei and in POL. Use to check whether a wallet can pay gas or a transfer; for ERC-20 tokens use polygon_token_balance, for all holdings at once use wallet_portfolio. A malformed address is rejected with 400, uncharged. Example: address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
addressstringyes0x wallet or contract address

No output schema declared.

No examples provided.

polygon_block ~144

Latest block number and block details on Polygon PoS, or any block by decimal number: hash, timestamp, transaction count, gas used and limit, base fee in gwei and producer. Use for timestamps and confirmation counts; for current fees use polygon_gas. A block that does not exist yet returns 404, uncharged. Example: number=latest. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
numberstring–Block number, or 'latest' (default)

No output schema declared.

No examples provided.

polygon_gas ~170

Current gas price on Polygon PoS (eth_gasPrice): gas price, base fee and suggested priority fee in gwei, plus what a plain POL transfer (21,000 gas) costs right now. Takes no input. Use before sending a transaction or to decide whether to wait; for the fee a past transaction actually paid use polygon_receipt. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
onlystring–Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result

No output schema declared.

No examples provided.

polygon_is_contract ~174

Check whether a 0x address on Polygon PoS is a smart contract or a plain wallet: bytecode size, and whether it is an EIP-1167 minimal proxy and which implementation it points to. Use before sending funds or approving a spender; for a fuller risk verdict use check_counterparty. A malformed address is rejected with 400, uncharged. Example: address=0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
addressstringyes0x address

No output schema declared.

No examples provided.

polygon_logs ~223

Recent contract event logs on Polygon PoS (eth_getLogs): the events a contract emitted over the last N blocks (1-1,000, default 50), optionally filtered by topic0 (the 0x 32-byte event signature hash). Returns up to 100 logs with block, transaction hash and topics. Use to watch transfers or contract events; for one transaction's outcome use polygon_receipt. Example: address=0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
addressstringyes0x contract address
blocksinteger–How many recent blocks to scan (1-1000, default 50)
topic0string–Optional 0x event signature hash to filter by

No output schema declared.

No examples provided.

polygon_nonce ~160

Read the transaction count (nonce) of a 0x address on Polygon PoS, both confirmed and including pending transactions. Use to build the next transaction or to tell whether an address has ever sent anything; for its balance use polygon_balance. A malformed address is rejected with 400, uncharged. Example: address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
addressstringyes0x address

No output schema declared.

No examples provided.

polygon_receipt ~202

Transaction receipt on Polygon PoS (eth_getTransactionReceipt): success or reverted, gas used, effective gas price, fee paid in POL, number of event logs and any contract created. Use to confirm a payment or call went through; for sender, value and calldata use polygon_tx. Input is a 0x-prefixed 64-hex hash; a pending or unknown hash returns 404, uncharged. Example: hash=0x23e86c30c46638b2e9798692fe89327a66aa8569a5d4a566125f655aeb8f80c7. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
hashstringyes0x-prefixed transaction hash (64 hex characters)

No output schema declared.

No examples provided.

polygon_token_balance ~204

ERC-20 token balance of a wallet on Polygon PoS (USDC, USDT, WETH or any token, via balanceOf): raw amount, decimals, symbol and the human-readable amount, live from the token contract. Use to check stablecoin or token holdings before a transfer or trade; for the native coin use polygon_balance. Both inputs are 0x addresses (40 hex characters); no contract returns 404 and a non-ERC-20 contract 422, both uncharged. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
addressstringyes0x wallet address
tokenstringyesToken: a ticker such as USDC, USDT, WETH or DAI, or the 0x ERC-20 contract address

No output schema declared.

No examples provided.

polygon_token_info ~207

Look up the name, symbol, decimals and total supply of an ERC-20 token contract on Polygon PoS, live from the contract. Use to identify an unknown token address or to format raw amounts; for a holder's balance use polygon_token_balance. Input is a ticker (USDC, WETH…) or the token's 0x contract address; an address that is not an ERC-20 contract returns 422, uncharged. Example: token=0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
tokenstringyesToken: a ticker such as USDC or WETH, or the 0x ERC-20 contract address

No output schema declared.

No examples provided.

polygon_token_transfers ~270

List a wallet's recent transfers of one ERC-20 token (default USDC) on Polygon PoS, in and out, over the last N blocks (1-2,000, default 1,000): direction, counterparty, amount and transaction, newest first, up to 50. Use to confirm a payment arrived or see what was sent; for the current balance use polygon_token_balance. Malformed addresses are rejected with 400, uncharged. Example: address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
addressstringyes0x wallet address
blocksinteger–How many recent blocks to scan (1-2000, default 1000; 2,000 blocks is about 67 minutes on Polygon PoS)
tokenstring–Token: a ticker such as USDT or WETH, or the 0x ERC-20 contract (default: USDC on this network)

No output schema declared.

No examples provided.

polygon_tx ~204

Look up a Polygon PoS transaction by hash: sender, recipient, value in POL, nonce, gas limit, the 4-byte function selector and its block. Use to see what was sent or whether it exists; for success or failure and fees paid use polygon_receipt, for emitted events polygon_logs. Input is a 0x-prefixed 64-hex hash; an unknown hash returns 404, uncharged. Example: hash=0x23e86c30c46638b2e9798692fe89327a66aa8569a5d4a566125f655aeb8f80c7. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
hashstringyes0x-prefixed transaction hash (64 hex characters)

No output schema declared.

No examples provided.

wallet ~222

Base only (all 5 chains: wallet_balances; USD values: wallet_portfolio). An address on Base: ETH and major token balances (USDC, WETH, cbBTC, DAI, USDbC, cbETH, AERO, EURC) plus up to 20 token addresses you pass, the account nonce, and whether it is an EOA, a contract or an EIP-7702 account. The nonce counts outgoing transactions only; not transfer or trading history. Use to check a counterparty's holdings. Example: address=0x4200000000000000000000000000000000000006. Price $0.005/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
addressstringyesWallet or contract address on Base (0x...)
tokensstring–Optional comma-separated extra ERC-20 addresses to check (max 20)

No output schema declared.

No examples provided.

wallet_balances ~196

Read a wallet's native coin and USDC balances on Base, Ethereum, Arbitrum, Optimism and Polygon in one call, live from each network, plus the USDC total. Use to find where a wallet's funds are before a payment or bridge; for one token on one network use <chain>_token_balance, for all tokens on Base use wallet_portfolio. A network whose nodes do not answer is listed with an error instead of failing the call. Example: address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. Price $0.005/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

NameTypeReqDescription
addressstringyes0x wallet address

No output schema declared.

No examples provided.

Install

How do I install the Agent Data Tools: Chain data MCP server?

Agent Data Tools: Chain data is a hosted endpoint at https://agent-data-tools.revmesh2074.workers.dev/mcp/chain, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agent-data-tools.revmesh2074.workers.dev

# add to Claude Code
claude mcp add --transport http nutshell2000-agent-data-tools-chain 'https://agent-data-tools.revmesh2074.workers.dev/mcp/chain'
Common questions

What is the Agent Data Tools: Chain data MCP server?

Agent Data Tools: Chain data is an MCP server listed in the public MCP registry as io.github.Nutshell2000/agent-data-tools-chain. 64 tools: balances, blocks, gas, txs and logs on 5 EVM chains, plus Bitcoin. 25 free calls. This page covers its hosted endpoint (https://agent-data-tools.revmesh2074.workers.dev/mcp/chain). Its publisher has verified ownership with us.

Is the Agent Data Tools: Chain data MCP server safe to use?

Agent Data Tools: Chain data scores 70 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 Agent Data Tools: Chain data MCP server expose?

Agent Data Tools: Chain data exposes 64 tools: wallet_balances, btc_fees, eth_balance, eth_gas, base_gas, and 59 more. Their descriptions and schemas cost roughly 12,087 tokens of context every time the server is loaded.

Does the Agent Data Tools: Chain data MCP server require authentication?

No. We connected to Agent Data Tools: Chain data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agent Data Tools: Chain data MCP server still maintained?

Agent Data Tools: Chain data is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.