Chain reads (x402) MCP server
work.agentexchange/chain-readsagentexchange.workstreamable-httpv1.0.0Scanned
EVM chain reads for agents: balances, gas, fees, blocks, txs, logs, ENS. 15 tools, x402 per call.
15 tools: 1 do something that can't be undone, 5 change things and 9 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
6 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Chain reads (x402) MCP server can do
The Chain reads (x402) MCP server is published by agentexchange.work, a domain the MCP Registry verified. It has 15 tools. It can do things that cannot be undone, such as sending, paying or publishing (chain_estimate_gas) and create or change data (5 tools: chain_native_balance, chain_block_header, chain_fee_history, chain_confirmations and 1 more), but cannot delete data. 9 tools only read.
1 tool can send data out of your system (chain_estimate_gas).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Can't be undone 1Claude Code: ask
chain_estimate_gas$0.005 via x402: estimate the gas a transaction will use (eth_estimateGas) across 6 chains — the pre-send read tx-building, trading and settlement agents make to size gas and avoid…Can send data outNo findings
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it $0.005 via x402: estimate the gas a transaction will use (eth_estimateGas) across 6 chains — the pre-send read tx-building, trading and settlement agents make to size gas and avoid out-of-gas reverts. Pass to (+ optional from/value/data).
Changes things 5Claude Code: ask
chain_block_header$0.005 via x402: the full header of any block — timestamp and age, transaction count, gas used vs limit with a utilization ratio and congested flag, base fee in gwei, miner and par…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it $0.005 via x402: the full header of any block — timestamp and age, transaction count, gas used vs limit with a utilization ratio and congested flag, base fee in gwei, miner and parent hash. /chain/block-number says WHERE the chain is; this says WHEN that block happened and how contested it was. Accepts a height or latest/finalized/safe. Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis.
chain_confirmations$0.005 via x402: did this transaction land, how deep is it buried, and is it safe to treat as FINAL on this chain.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it $0.005 via x402: did this transaction land, how deep is it buried, and is it safe to treat as FINAL on this chain. Returns status, block, tip, confirmations, gas used, fee paid and log count, compared against the chain's own finality threshold (Ethereum 64, Polygon 128, OP-stack 60). A success with two confirmations is not a settled payment. Also distinguishes 'no receipt yet' from 'failed' — conflating those is how agents double-spend.
chain_fee_history$0.005 via x402: EIP-1559 fee history — base-fee trend over N blocks, priority-fee percentiles (10/50/90), mean block utilization, and a recommended maxFeePerGas / maxPriorityFeePe…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it $0.005 via x402: EIP-1559 fee history — base-fee trend over N blocks, priority-fee percentiles (10/50/90), mean block utilization, and a recommended maxFeePerGas / maxPriorityFeePerGas with the reasoning stated. A single gas number cannot tell you whether fees are rising; this can. Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis.
chain_gas_price$0.002 via x402: live network gas prices (slow/average/fast, in gwei) for any chain — the pre-transaction read every trading, sniping and settlement agent makes before sending a tx…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it $0.002 via x402: live network gas prices (slow/average/fast, in gwei) for any chain — the pre-transaction read every trading, sniping and settlement agent makes before sending a tx to size the fee. Across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. Live from Blockscout; one paid call instead of running your own RPC.
chain_native_balance$0.003 via x402: the core on-chain RPC read — any address's native coin balance (ETH/POL/xDAI) with live USD value and outgoing transaction count, across Base, Ethereum, Optimism, …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it $0.003 via x402: the core on-chain RPC read — any address's native coin balance (ETH/POL/xDAI) with live USD value and outgoing transaction count, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The high-frequency balance check wallet-tracking, settlement and trading agents poll constantly. Live from Blockscout; 6 chains vs onesource's Ethereum-only.
Only reads 9Show 9 read-only tools
chain_ens_resolve$0.005 via x402: resolve ENS in either direction on Ethereum — pass an ENS name (vitalik.eth) to get its 0x address, or pass a 0x address to get its primary ENS name (and avatar wh…No findings
Why it is in this group
- The name "chain_ens_resolve" says "resolve": a word for reading.
Description, as the server wrote it $0.005 via x402: resolve ENS in either direction on Ethereum — pass an ENS name (vitalik.eth) to get its 0x address, or pass a 0x address to get its primary ENS name (and avatar when set). The identity read every wallet, payment and UX agent makes to verify who it's sending to, or to display a human-readable name instead of a raw hex address. Live ENS registry; one paid call instead of running your own resolver.
chain_event_logs$0.005 via x402: raw event logs by contract address and/or indexed topics over a block range (eth_getLogs) — the indexing primitive.No findings
Why it is in this group
- The name "chain_event_logs" says "log": a word for reading.
Description, as the server wrote it $0.005 via x402: raw event logs by contract address and/or indexed topics over a block range (eth_getLogs) — the indexing primitive. Defaults to a 25-block window and narrows automatically when a node refuses on result size, and every cap or narrowing that bit is named in the response instead of silently applied. Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis.
chain_transaction_explain$0.005 via x402: decode any transaction by hash into a plain-English explanation — what actually happened (a swap, transfer, approval, mint, or contract call), who the actors are, …No findings
Why it is in this group
- The name "chain_transaction_explain" says "explain": a word for reading.
Description, as the server wrote it $0.005 via x402: decode any transaction by hash into a plain-English explanation — what actually happened (a swap, transfer, approval, mint, or contract call), who the actors are, and the full list of asset changes (every native coin and token in/out with symbol, amount and direction), plus status, fee and the decoded method. The read agents make to UNDERSTAND a tx, not just confirm it landed: for wallet UX, accounting, risk, dispute and trading agents. Across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. Live from Blockscout; one paid call instead of running your own indexer + ABI decoder.
chain_transaction_status$0.008 via x402: look up any transaction by hash — confirmation status (success/failed/pending), block number, confirmations, value, from/to, fee paid, gas used, and decoded method…No findings
Why it is in this group
- The name "chain_transaction_status" says "status": a word for reading.
Description, as the server wrote it $0.008 via x402: look up any transaction by hash — confirmation status (success/failed/pending), block number, confirmations, value, from/to, fee paid, gas used, and decoded method. The read every settlement, trading and payment agent polls after sending a tx to confirm it landed. Across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. Live from Blockscout; one paid call instead of running your own RPC.
get_chain_allowanceHow much of an ERC-20 token a spender is approved to move from an owner's wallet, via allowance, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis.No findings
Why it is in this group
- The name "get_chain_allowance" says "get": a word for reading.
Description, as the server wrote it How much of an ERC-20 token a spender is approved to move from an owner's wallet, via allowance, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The approval read every DeFi, swap and trading agent makes before (and after) a transaction to know if an approve is needed. Live public RPC; one paid call.
get_chain_block_numberThe current chain tip (latest block height) via eth_blockNumber, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis.No findings
Why it is in this group
- The name "get_chain_block_number" says "get": a word for reading.
Description, as the server wrote it The current chain tip (latest block height) via eth_blockNumber, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The freshness read settlement, indexing and trading agents poll to know where the chain is. Live public RPC; one paid call.
get_chain_codeIs an address a smart contract or a regular wallet (EOA)?No findings
Why it is in this group
- The name "get_chain_code" says "get": a word for reading.
Description, as the server wrote it Is an address a smart contract or a regular wallet (EOA)? Returns whether deployed bytecode exists and its size via eth_getCode, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The safety/identity read wallet, payment and trading agents make before interacting with an address. Live public RPC; one paid call.
get_chain_erc20_balanceAny wallet's balance of any ERC-20 token (USDC, USDT, DAI, or any contract) via balanceOf, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis.No findings
Why it is in this group
- The name "get_chain_erc20_balance" says "get": a word for reading.
Description, as the server wrote it Any wallet's balance of any ERC-20 token (USDC, USDT, DAI, or any contract) via balanceOf, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The token-balance read wallet-tracking, copy-trade, treasury and trading agents poll constantly — the most-called RPC read after native balance. Live public RPC; 6 chains vs onesource's Ethereum-only coverage.
get_chain_nonceAn address's transaction count (nonce) via eth_getTransactionCount — the next nonce to use and total outgoing transactions, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnos…No findings
Why it is in this group
- The name "get_chain_nonce" says "get": a word for reading.
Description, as the server wrote it An address's transaction count (nonce) via eth_getTransactionCount — the next nonce to use and total outgoing transactions, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The read settlement and trading agents make to build and sequence transactions. Live public RPC; one paid call.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:20 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://store.agentexchange.work/.well-known/oauth-protected-resource/chain/mcp
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://store.agentexchange.work/chain/mcp: tools/list returned 15 tools to an anonymous client, including chain_estimate_gas (irreversible), chain_native_balance (write), chain_block_header (write), chain_fee_history (write), chain_confirmations (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http chain-reads https://store.agentexchange.work/chain/mcpclaude mcp add --transport http chain-reads https://store.agentexchange.work/chain/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__chain-reads__chain_event_logs",
"mcp__chain-reads__chain_transaction_status",
"mcp__chain-reads__chain_transaction_explain",
"mcp__chain-reads__chain_ens_resolve",
"mcp__chain-reads__get_chain_erc20_balance",
"mcp__chain-reads__get_chain_code",
"mcp__chain-reads__get_chain_block_number",
"mcp__chain-reads__get_chain_allowance",
"mcp__chain-reads__get_chain_nonce"
],
"ask": [
"mcp__chain-reads__chain_native_balance",
"mcp__chain-reads__chain_block_header",
"mcp__chain-reads__chain_fee_history",
"mcp__chain-reads__chain_confirmations",
"mcp__chain-reads__chain_gas_price",
"mcp__chain-reads__chain_estimate_gas"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as chain-reads. Review it before you use it.
Capability tags behind 1 rule
- mcp__chain-reads__chain_estimate_gas outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/work.agentexchange/chain-reads/verify?hash=aca610f521d508b608fa14556cc7ed7a9868130087cd73adf4ca11217b0dd3a0" | jq -e '.changed == false'Pinned hash aca610f521d5, from Nov 19, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/work.agentexchange/chain-reads/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/work.agentexchange/chain-reads)Source: MCP Registry. Synced Nov 19, 2026, 01:18 UTC.
Chain reads (x402) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Chain reads (x402) MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Chain reads (x402) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Chain reads (x402) MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: chain_estimate_gas.
What tools does the Chain reads (x402) MCP server have?
- 15 tools: 1 irreversible, 5 write, 9 read. chain_estimate_gas, chain_native_balance, chain_block_header, chain_fee_history, chain_confirmations, chain_gas_price, chain_event_logs, chain_transaction_status and 7 more.
Does the Chain reads (x402) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Chain reads (x402) MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): chain_estimate_gas.
Has the Chain reads (x402) MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.