Skip to content

MCP servers › io.github.Nutshell2000 › agent-data-tools-chain

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.Nutshell2000/agent-data-tools-chain

64 tools: balances, blocks, gas, txs and logs on 5 EVM chains, plus Bitcoin. 25 free calls. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedversion 1.50.5JavaScriptstreamable HTTP64 tools

Summary

io.github.Nutshell2000/agent-data-tools-chain is a remote MCP server listed in the official MCP registry at version 1.50.5. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 64 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
64
Described as changing data
0 of 64 toolsAI-classified
Mainly works on
nothing outside itself: it only answers questionsAI-classified
Topic
finance-and-paymentsAI-classified
Last tested
2026-10-23

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.50.5, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-19 (earliest version still in the registry; older removed versions would be earlier)
Version history
54 versions listed, 2026-10-19 to 2026-10-22; 54 in the 90 days before the 2026-10-23 snapshot.
Most recent 12 versions
  • 1.50.5 · 2026-10-22
  • 1.50.4 · 2026-10-22
  • 1.50.3 · 2026-10-22
  • 1.50.2 · 2026-10-22
  • 1.50.1 · 2026-10-22
  • 1.50.0 · 2026-10-22
  • 1.49.1 · 2026-10-22
  • 1.49.0 · 2026-10-22
  • 1.48.6 · 2026-10-22
  • 1.48.5 · 2026-10-22
  • 1.48.4 · 2026-10-22
  • 1.48.3 · 2026-10-22
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.50.5 (published 2026-10-22).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
64tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.

None of its 64 tools are described as changing anything.

  • wallet_balanceson 2 other serversreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x wallet address”
  • btc_feeson 3 other serversreads or searches

    “Current Bitcoin network fee rates in sat/vB for next-block, half-hour, one-hour and economy confirmation, the estimated cost in sats of a typical payment, mempool size and total pending fees, and the…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • 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 retu…”
  • eth_balanceon 2 other serversreads or searches

    “Native ETH balance (eth_getBalance) of any 0x wallet address on Ethereum at the latest block, in wei and in ETH.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x wallet or contract address”
  • eth_gason 1 other serverreads or searches

    “Current gas price on Ethereum (eth_gasPrice): gas price, base fee and suggested priority fee in gwei, plus what a plain ETH transfer (21,000 gas) costs right now.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • 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 retu…”
  • base_gason 10 other serversreads or searches

    “Live gas prices on Base (chain 8453) read from the latest block: base fee and priority fee in gwei, suggested maxFeePerGas and maxPriorityFeePerGas in wei for an EIP-1559 transaction, how full the la…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • 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 retu…”
  • walleton 7 other serversreads or searches

    “Base only (all 5 chains: wallet_balances; USD values: wallet_portfolio).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • addressstringrequired“Wallet or contract address on Base (0x...)”
    • tokensstring“Optional comma-separated extra ERC-20 addresses to check (max 20)”
  • btc_addresson 3 other serversreads or searches

    “Balance and activity of any Bitcoin mainnet address (legacy, P2SH or bech32): confirmed balance in sats and BTC, unconfirmed pending amount, total received and sent, and transaction counts.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“Bitcoin mainnet address (1..., 3...”
  • ln_invoiceon 1 other serverreads or searches

    “Decode a BOLT11 Lightning Network invoice without paying it: network, amount in sats and BTC, description, payment hash, creation time, expiry time and whether it has already expired.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • invoicestringrequired“BOLT11 invoice string starting with ln (lnbc...”
  • base_txon 5 other serversreads or searches

    “Look up any transaction on Base by hash: whether it succeeded, reverted or is still pending, sender and receiver, ETH value, called method id, block number and time, number of confirmations, gas used…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“Transaction hash on Base: 0x followed by 64 hex characters”
  • base_allowanceon 6 other serversreads or searches

    “Check how much of a wallet's ERC-20 token a spender contract is approved to move on Base: the raw and formatted allowance, the token symbol and decimals, and whether the approval is unlimited.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 3 required
    • tokenstringrequired“ERC-20 token contract address on Base (0x...)”
    • ownerstringrequired“Wallet address that holds the token (0x...)”
    • spenderstringrequired“Address allowed to spend, usually a router or protocol contract (0x...)”
  • enson 6 other serversreads or searches

    “Resolve an Ethereum Name Service name such as vitalik.eth to its wallet address and avatar, or look up the primary ENS name of an address (reverse resolution).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • namestringrequired“An ENS name such as vitalik.eth, or an address (0x...) for reverse lookup”
  • base_balanceon 5 other serversreads or searches

    “Native ETH balance (eth_getBalance) of any 0x wallet address on Base at the latest block, in wei and in ETH.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x wallet or contract address”
Show 52 more tools
  • base_token_balanceon 1 other serverreads or searches

    “ERC-20 token balance of a wallet on Base (USDC, USDT, WETH or any token, via balanceOf): raw amount, decimals, symbol and the human-readable amount, live from the token contract.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • tokenstringrequired“Token: a ticker such as USDC, USDT, WETH or DAI, or the 0x ERC-20 contract address”
    • addressstringrequired“0x wallet address”
  • base_token_infoon 4 other serversreads or searches

    “Look up the name, symbol, decimals and total supply of an ERC-20 token contract on Base, live from the contract.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • tokenstringrequired“Token: a ticker such as USDC or WETH, or the 0x ERC-20 contract address”
  • base_blockon 5 other serversreads or searches

    “Latest block number and block details on Base, or any block by decimal number: hash, timestamp, transaction count, gas used and limit, base fee in gwei and producer.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • numberstring“Block number, or 'latest' (default)”
  • base_receipton 4 other serversreads or searches

    “Transaction receipt on Base (eth_getTransactionReceipt): success or reverted, gas used, effective gas price, fee paid in ETH, number of event logs and any contract created.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“0x-prefixed transaction hash (64 hex characters)”
  • base_nonceon 4 other serversreads or searches

    “Read the transaction count (nonce) of a 0x address on Base, both confirmed and including pending transactions.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • base_is_contracton 1 other serverreads or searches

    “Check whether a 0x address on Base 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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • base_logson 2 other serversreads or searches

    “Recent contract event logs on Base (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).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x contract address”
    • blocksinteger“How many recent blocks to scan (1-1000, default 50)”
    • topic0string“Optional 0x event signature hash to filter by”
  • base_token_transferson 1 other serverreads or searches

    “List a wallet's recent transfers of one ERC-20 token (default USDC) on Base, in and out, over the last N blocks (1-2,000, default 1,000): direction, counterparty, amount and transaction, newest first…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x wallet address”
    • tokenstring“Token: a ticker such as USDT or WETH, or the 0x ERC-20 contract (default: USDC on this network)”
    • blocksinteger“How many recent blocks to scan (1-2000, default 1000; 2,000 blocks is about 67 minutes on Base)”
  • eth_token_balanceon 1 other serverreads or searches

    “ERC-20 token balance of a wallet on Ethereum (USDC, USDT, WETH or any token, via balanceOf): raw amount, decimals, symbol and the human-readable amount, live from the token contract.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • tokenstringrequired“Token: a ticker such as USDC, USDT, WETH or DAI, or the 0x ERC-20 contract address”
    • addressstringrequired“0x wallet address”
  • eth_token_infoon 1 other serverreads or searches

    “Look up the name, symbol, decimals and total supply of an ERC-20 token contract on Ethereum, live from the contract.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • tokenstringrequired“Token: a ticker such as USDC or WETH, or the 0x ERC-20 contract address”
  • eth_blockon 1 other serverreads or searches

    “Latest block number and block details on Ethereum, or any block by decimal number: hash, timestamp, transaction count, gas used and limit, base fee in gwei and producer.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • numberstring“Block number, or 'latest' (default)”
  • eth_txon 1 other serverreads or searches

    “Look up an Ethereum transaction by hash: sender, recipient, value in ETH, nonce, gas limit, the 4-byte function selector and its block.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“0x-prefixed transaction hash (64 hex characters)”
  • eth_receipton 1 other serverreads or searches

    “Transaction receipt on Ethereum (eth_getTransactionReceipt): success or reverted, gas used, effective gas price, fee paid in ETH, number of event logs and any contract created.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“0x-prefixed transaction hash (64 hex characters)”
  • eth_nonceon 1 other serverreads or searches

    “Read the transaction count (nonce) of a 0x address on Ethereum, both confirmed and including pending transactions.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • eth_is_contracton 1 other serverreads or searches

    “Check whether a 0x address on Ethereum 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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • eth_logson 1 other serverreads or searches

    “Recent contract event logs on Ethereum (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).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x contract address”
    • blocksinteger“How many recent blocks to scan (1-1000, default 50)”
    • topic0string“Optional 0x event signature hash to filter by”
  • eth_token_transferson 1 other serverreads or searches

    “List a wallet's recent transfers of one ERC-20 token (default USDC) on Ethereum, in and out, over the last N blocks (1-2,000, default 1,000): direction, counterparty, amount and transaction, newest f…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x wallet address”
    • tokenstring“Token: a ticker such as USDT or WETH, or the 0x ERC-20 contract (default: USDC on this network)”
    • blocksinteger“How many recent blocks to scan (1-2000, default 1000; 2,000 blocks is about 6.7 hours on Ethereum)”
  • arb_balanceon 1 other serverreads or searches

    “Native ETH balance (eth_getBalance) of any 0x wallet address on Arbitrum One at the latest block, in wei and in ETH.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x wallet or contract address”
  • arb_token_balanceon 1 other serverreads or searches

    “ERC-20 token balance of a wallet on Arbitrum One (USDC, USDT, WETH or any token, via balanceOf): raw amount, decimals, symbol and the human-readable amount, live from the token contract.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • tokenstringrequired“Token: a ticker such as USDC, USDT, WETH or DAI, or the 0x ERC-20 contract address”
    • addressstringrequired“0x wallet address”
  • arb_token_infoon 1 other serverreads or searches

    “Look up the name, symbol, decimals and total supply of an ERC-20 token contract on Arbitrum One, live from the contract.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • tokenstringrequired“Token: a ticker such as USDC or WETH, or the 0x ERC-20 contract address”
  • arb_blockon 1 other serverreads or searches

    “Latest block number and block details on Arbitrum One, or any block by decimal number: hash, timestamp, transaction count, gas used and limit, base fee in gwei and producer.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • numberstring“Block number, or 'latest' (default)”
  • arb_gason 1 other serverreads or searches

    “Current gas price on Arbitrum One (eth_gasPrice): gas price, base fee and suggested priority fee in gwei, plus what a plain ETH transfer (21,000 gas) costs right now.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • 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 retu…”
  • arb_txon 1 other serverreads or searches

    “Look up an Arbitrum One transaction by hash: sender, recipient, value in ETH, nonce, gas limit, the 4-byte function selector and its block.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“0x-prefixed transaction hash (64 hex characters)”
  • arb_receipton 1 other serverreads or searches

    “Transaction receipt on Arbitrum One (eth_getTransactionReceipt): success or reverted, gas used, effective gas price, fee paid in ETH, number of event logs and any contract created.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“0x-prefixed transaction hash (64 hex characters)”
  • arb_nonceon 1 other serverreads or searches

    “Read the transaction count (nonce) of a 0x address on Arbitrum One, both confirmed and including pending transactions.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • arb_is_contracton 1 other serverreads or searches

    “Check whether a 0x address on Arbitrum One 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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • arb_logson 1 other serverreads or searches

    “Recent contract event logs on Arbitrum One (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 has…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x contract address”
    • blocksinteger“How many recent blocks to scan (1-1000, default 50)”
    • topic0string“Optional 0x event signature hash to filter by”
  • arb_token_transferson 1 other serverreads or searches

    “List a wallet's recent transfers of one ERC-20 token (default USDC) on Arbitrum One, in and out, over the last N blocks (1-2,000, default 1,000): direction, counterparty, amount and transaction, newe…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x wallet address”
    • tokenstring“Token: a ticker such as USDT or WETH, or the 0x ERC-20 contract (default: USDC on this network)”
    • blocksinteger“How many recent blocks to scan (1-2000, default 1000; 2,000 blocks is about 8 minutes on Arbitrum One)”
  • op_balanceon 1 other serverreads or searches

    “Native ETH balance (eth_getBalance) of any 0x wallet address on Optimism at the latest block, in wei and in ETH.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x wallet or contract address”
  • op_token_balanceon 1 other serverreads or searches

    “ERC-20 token balance of a wallet on Optimism (USDC, USDT, WETH or any token, via balanceOf): raw amount, decimals, symbol and the human-readable amount, live from the token contract.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • tokenstringrequired“Token: a ticker such as USDC, USDT, WETH or DAI, or the 0x ERC-20 contract address”
    • addressstringrequired“0x wallet address”
  • op_token_infoon 1 other serverreads or searches

    “Look up the name, symbol, decimals and total supply of an ERC-20 token contract on Optimism, live from the contract.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • tokenstringrequired“Token: a ticker such as USDC or WETH, or the 0x ERC-20 contract address”
  • op_blockon 1 other serverreads or searches

    “Latest block number and block details on Optimism, or any block by decimal number: hash, timestamp, transaction count, gas used and limit, base fee in gwei and producer.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • numberstring“Block number, or 'latest' (default)”
  • op_gason 1 other serverreads or searches

    “Current gas price on Optimism (eth_gasPrice): gas price, base fee and suggested priority fee in gwei, plus what a plain ETH transfer (21,000 gas) costs right now.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • 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 retu…”
  • op_txon 1 other serverreads or searches

    “Look up an Optimism transaction by hash: sender, recipient, value in ETH, nonce, gas limit, the 4-byte function selector and its block.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“0x-prefixed transaction hash (64 hex characters)”
  • op_receipton 1 other serverreads or searches

    “Transaction receipt on Optimism (eth_getTransactionReceipt): success or reverted, gas used, effective gas price, fee paid in ETH, number of event logs and any contract created.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“0x-prefixed transaction hash (64 hex characters)”
  • op_nonceon 1 other serverreads or searches

    “Read the transaction count (nonce) of a 0x address on Optimism, both confirmed and including pending transactions.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • op_is_contracton 1 other serverreads or searches

    “Check whether a 0x address on Optimism 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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • op_logson 1 other serverreads or searches

    “Recent contract event logs on Optimism (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).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x contract address”
    • blocksinteger“How many recent blocks to scan (1-1000, default 50)”
    • topic0string“Optional 0x event signature hash to filter by”
  • op_token_transferson 1 other serverreads or searches

    “List a wallet's recent transfers of one ERC-20 token (default USDC) on Optimism, in and out, over the last N blocks (1-2,000, default 1,000): direction, counterparty, amount and transaction, newest f…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x wallet address”
    • tokenstring“Token: a ticker such as USDT or WETH, or the 0x ERC-20 contract (default: USDC on this network)”
    • blocksinteger“How many recent blocks to scan (1-2000, default 1000; 2,000 blocks is about 67 minutes on Optimism)”
  • polygon_balanceon 2 other serversreads or searches

    “Native POL balance (eth_getBalance) of any 0x wallet address on Polygon PoS at the latest block, in wei and in POL.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x wallet or contract address”
  • polygon_token_balanceon 1 other serverreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • tokenstringrequired“Token: a ticker such as USDC, USDT, WETH or DAI, or the 0x ERC-20 contract address”
    • addressstringrequired“0x wallet address”
  • polygon_token_infoon 1 other serverreads or searches

    “Look up the name, symbol, decimals and total supply of an ERC-20 token contract on Polygon PoS, live from the contract.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • tokenstringrequired“Token: a ticker such as USDC or WETH, or the 0x ERC-20 contract address”
  • polygon_blockon 2 other serversreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • numberstring“Block number, or 'latest' (default)”
  • polygon_gason 2 other serversreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • 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 retu…”
  • polygon_txon 2 other serversreads or searches

    “Look up a Polygon PoS transaction by hash: sender, recipient, value in POL, nonce, gas limit, the 4-byte function selector and its block.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“0x-prefixed transaction hash (64 hex characters)”
  • polygon_receipton 1 other serverreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • hashstringrequired“0x-prefixed transaction hash (64 hex characters)”
  • polygon_nonceon 1 other serverreads or searches

    “Read the transaction count (nonce) of a 0x address on Polygon PoS, both confirmed and including pending transactions.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • polygon_is_contracton 1 other serverreads or searches

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • addressstringrequired“0x address”
  • polygon_logson 1 other serverreads or searches

    “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…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x contract address”
    • blocksinteger“How many recent blocks to scan (1-1000, default 50)”
    • topic0string“Optional 0x event signature hash to filter by”
  • polygon_token_transferson 1 other serverreads or searches

    “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, newes…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • addressstringrequired“0x wallet address”
    • tokenstring“Token: a ticker such as USDT or WETH, or the 0x ERC-20 contract (default: USDC on this network)”
    • blocksinteger“How many recent blocks to scan (1-2000, default 1000; 2,000 blocks is about 67 minutes on Polygon PoS)”
  • keccakon 1 other servercalculates or converts

    “Keccak-256 hash (the Ethereum hash) of text or of 0x hex bytes, as used for function selectors, event topics and storage slots.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • textstringrequired“Text, or 0x-prefixed hex bytes, up to 10,000 characters”
  • networkon 6 other serversreads or searches

    “Reference facts for paying and reading on Base mainnet: chain id, native USDC contract and decimals, block explorer and public RPC URLs, and the x402 network identifier.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input
    • 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 retu…”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 64 tools
Says what it returns
100% of 64 tools
States limits, defaults or errors
44% of 64 tools
Says when to use it
100% of 64 tools
Items covered per tool
3.4 of 4 on average

Counted from the listing

Parameters with a description
100% of 92
Tools with a description
100% of 64
Typical description length
564 characters

The tool set

Counted from the listing

Tools
64
Size of the list
about 17,832 tokens for an agent to load (characters ÷ 4)
Naming
60 of 64 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 64 of 64 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://agent-data-tools.revmesh2074.workers.dev/mcp/chain
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "agent-data-tools-chain": {
      "url": "https://agent-data-tools.revmesh2074.workers.dev/mcp/chain"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "agent-data-tools-chain": {
      "type": "http",
      "url": "https://agent-data-tools.revmesh2074.workers.dev/mcp/chain"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"agent-data-tools-chain","type":"http","url":"https://agent-data-tools.revmesh2074.workers.dev/mcp/chain"}'
Claude Code
claude mcp add --transport http agent-data-tools-chain https://agent-data-tools.revmesh2074.workers.dev/mcp/chain
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://agent-data-tools.revmesh2074.workers.dev/mcp/chain --transport http
  • Optional settings the entry also lists (left out above): Authorization.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint agent-data-tools.revmesh2074.workers.dev/mcp/chainSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23
Repository github.com/Nutshell2000/agent-data-toolsOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.Nutshell2000 · 8 servers
GitHub owner
a personal account (Nutshell2000)
Repository
github.com/Nutshell2000/agent-data-tools
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.Nutshell2000/agent-data-tools-chain

Answered from the data above

Is io.github.Nutshell2000/agent-data-tools-chain safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.Nutshell2000/agent-data-tools-chain need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.Nutshell2000/agent-data-tools-chain been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can io.github.Nutshell2000/agent-data-tools-chain do?

It lists 64 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.Nutshell2000/agent-data-tools-chain change or delete data?

None of its 64 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.

Does io.github.Nutshell2000/agent-data-tools-chain publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.Nutshell2000/agent-data-tools-chain?

In github.com/Nutshell2000/agent-data-tools, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 39 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 64 tools, 0 resources, 0 prompts.
  4. 790 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
No value: the AI answer was held back because the quoted text did not clearly support it.
Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Nutshell2000/agent-data-tools-chain: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.Nutshell2000/agent-data-tools-chain

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.Nutshell2000/agent-data-tools-chain)](https://protocolprobe.com/mcp/servers/io.github.Nutshell2000/agent-data-tools-chain)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology