Chain reads (x402)
REMOTE · STORE.AGENTEXCHANGE.WORK
EVM chain reads for agents: balances, gas, fees, blocks, txs, logs, ENS. 15 tools, x402 per call.
Available components
Last scanned (19 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 Nov 2026.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2399 tokens (~159/item across 15 items; 15 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 Management7
- Stability observed for 2 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +9
- Authorization: unverified → partial ▲ security
- Schema quality: 140 → 159 ▼ functional
- Tool coverage: 63% → 100% ▲ functional
- Schema quality: fair → good functional
- “chain_block_header” reworded the description of “x_payment” cosmetic
- “chain_confirmations” reworded the description of “x_payment” cosmetic
- “chain_ens_resolve” reworded the description of “x_payment” cosmetic
- “chain_estimate_gas” reworded the description of “from” cosmetic
- “chain_estimate_gas” reworded the description of “x_payment” cosmetic
- “chain_event_logs” reworded the description of “fromBlock” cosmetic
- “chain_event_logs” reworded the description of “toBlock” cosmetic
- “chain_event_logs” reworded the description of “topic1” cosmetic
- “chain_event_logs” reworded the description of “topic2” cosmetic
- “chain_event_logs” reworded the description of “topic3” cosmetic
- “chain_event_logs” reworded the description of “x_payment” cosmetic
- “chain_fee_history” reworded the description of “x_payment” cosmetic
- “chain_gas_price” reworded the description of “x_payment” cosmetic
- “chain_native_balance” reworded the description of “x_payment” cosmetic
- “chain_transaction_explain” reworded the description of “x_payment” cosmetic
- “chain_transaction_status” reworded the description of “x_payment” cosmetic
- 20 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Nov 26 54
First indexed and scored.
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 21 Nov 2026 · Probed https://store.agentexchange.work/chain/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentexchange.work | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | cdd21212e1bb1f6a135983b641230886 |
| SANs: agentexchange.work, store.agentexchange.work, *.store.agentexchange.work | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of store.agentexchange.work. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| work. | DS published | 33659 | 13 | Verified |
| agentexchange.work. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://store.agentexchange.work/chain/mcp | Verified | 200 | |
| http (plaintext) | http://store.agentexchange.work/chain/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
chain_block_header ~188
$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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | base|ethereum|optimism|arbitrum|polygon|gnosis (default base) |
| number | string | – | Block height (decimal or 0x hex) or latest|finalized|safe|earliest (default latest) |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
chain_confirmations ~183
$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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | base|ethereum|optimism|arbitrum|polygon|gnosis (default base) |
| hash | string | – | Transaction hash (0x + 64 hex) |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
chain_ens_resolve ~179
$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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | 0x address to reverse-resolve to its primary ENS name |
| name | string | – | ENS name to resolve to an address, e.g. vitalik.eth |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
chain_estimate_gas ~177
$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).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | base|ethereum|optimism|arbitrum|polygon|gnosis (default base) |
| data | string | – | Calldata 0x... |
| from | string | – | Sender address 0x… for the simulated call |
| to | string | yes | Recipient/contract address 0x... |
| value | string | – | Wei (hex or decimal) |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
chain_event_logs ~297
$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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Contract address to filter on (0x...) |
| chain | string | – | base|ethereum|optimism|arbitrum|polygon|gnosis (default base) |
| fromBlock | string | – | First block of the range, decimal or 0x hex (e.g. 24000000) |
| toBlock | string | – | Last block of the range, decimal, 0x hex or latest |
| topic0 | string | – | Event signature topic (32-byte 0x...) |
| topic1 | string | – | First indexed event topic (0x… 32-byte hex), optional filter |
| topic2 | string | – | Second indexed event topic (0x… 32-byte hex), optional filter |
| topic3 | string | – | Third indexed event topic (0x… 32-byte hex), optional filter |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
chain_fee_history ~171
$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.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | number | – | Recent blocks to sample, 1-100 (default 20) |
| chain | string | – | base|ethereum|optimism|arbitrum|polygon|gnosis (default base) |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
chain_gas_price ~146
$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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | base|ethereum|optimism|arbitrum|polygon|gnosis (default ethereum) |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
chain_native_balance ~161
$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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Account address (0x...) |
| chain | string | – | base|ethereum|optimism|arbitrum|polygon|gnosis (default base) |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
chain_transaction_explain ~218
$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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | base|ethereum|optimism|arbitrum|polygon|gnosis (default base) |
| hash | string | yes | Transaction hash (0x... 64 hex) |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
chain_transaction_status ~174
$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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | base|ethereum|optimism|arbitrum|polygon|gnosis (default base) |
| hash | string | yes | Transaction hash (0x... 64 hex) |
| x_payment | string | – | x402 payment payload (base64) to settle this call; omit to receive the payment terms first |
No output schema declared.
No examples provided.
get_chain_allowance ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| x_payment | string | – | Signed x402 payment payload |
No output schema declared.
No examples provided.
get_chain_block_number ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| x_payment | string | – | Signed x402 payment payload |
No output schema declared.
No examples provided.
get_chain_code ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| x_payment | string | – | Signed x402 payment payload |
No output schema declared.
No examples provided.
get_chain_erc20_balance ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| x_payment | string | – | Signed x402 payment payload |
No output schema declared.
No examples provided.
get_chain_nonce ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| x_payment | string | – | Signed x402 payment payload |
No output schema declared.
No examples provided.
How do I install the Chain reads (x402) MCP server?
Chain reads (x402) is a hosted endpoint at https://store.agentexchange.work/chain/mcp, 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 · store.agentexchange.work
claude mcp add --transport http work-agentexchange-chain-reads 'https://store.agentexchange.work/chain/mcp'
What is the Chain reads (x402) MCP server?
Chain reads (x402) is an MCP server listed in the public MCP registry as work.agentexchange/chain-reads. EVM chain reads for agents: balances, gas, fees, blocks, txs, logs, ENS. 15 tools, x402 per call. This page covers its hosted endpoint (https://store.agentexchange.work/chain/mcp).
Is the Chain reads (x402) MCP server safe to use?
Chain reads (x402) scores 63 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 Chain reads (x402) MCP server expose?
Chain reads (x402) exposes 15 tools: chain_native_balance, chain_block_header, chain_event_logs, chain_fee_history, chain_confirmations, and 10 more. Their descriptions and schemas cost roughly 2,361 tokens of context every time the server is loaded.
Does the Chain reads (x402) MCP server require authentication?
No. We connected to Chain reads (x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chain reads (x402) MCP server still maintained?
Chain reads (x402) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Chain reads (x402) MCP server?
VerifyMCP ran 13 checks on Chain reads (x402), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.