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.

P0: wallet balances and EVM reads

REMOTE · X402-BAZAAR-RANK.X402-BAZAAR-RANK-WORKER.WORKERS.DEV

Wallet balances, ERC-20, blocks, transactions, receipts, ENS and payment checks, pay per call

+3 this week 68 Trust /100

Last scanned (15 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 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 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
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2742 tokens (~228/item across 12 items; 12 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 Management47
  • Stability observed for 14 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_check" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 13 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
What we tested

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 →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1
    • Tool “evm_block” rewrote its description, which is the text the model reads security
    • Tool “evm_code” rewrote its description, which is the text the model reads security
    • Tool “evm_ens” rewrote its description, which is the text the model reads security
    • Tool “evm_erc20_balance” rewrote its description, which is the text the model reads security
    • Tool “evm_native_balance” rewrote its description, which is the text the model reads security
    • Tool “evm_nonce” rewrote its description, which is the text the model reads security
    • Tool “evm_receipt” rewrote its description, which is the text the model reads security
    • Tool “evm_transaction” rewrote its description, which is the text the model reads security
    • Tool “pay_check” rewrote its description, which is the text the model reads security
    • Tool “quote_swap” rewrote its description, which is the text the model reads security
    • Tool “wallet_balance” rewrote its description, which is the text the model reads security
    • Tool “wallet_balance_batch” rewrote its description, which is the text the model reads security
    • Schema quality: 289 → 228 ▲ functional
    • “evm_ens” reworded the description of “address” cosmetic
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “evm_block” rewrote its description, which is the text the model reads security
    • Tool “evm_code” rewrote its description, which is the text the model reads security
    • Tool “evm_ens” rewrote its description, which is the text the model reads security
    • Tool “evm_erc20_balance” rewrote its description, which is the text the model reads security
    • Tool “evm_native_balance” rewrote its description, which is the text the model reads security
    • Tool “evm_nonce” rewrote its description, which is the text the model reads security
    • Tool “evm_receipt” rewrote its description, which is the text the model reads security
    • Tool “evm_transaction” rewrote its description, which is the text the model reads security
    • Tool “pay_check” rewrote its description, which is the text the model reads security
    • Tool “quote_swap” rewrote its description, which is the text the model reads security
    • Tool “wallet_balance” rewrote its description, which is the text the model reads security
    • Tool “wallet_balance_batch” rewrote its description, which is the text the model reads security
    • Schema quality: 248 → 289 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • “evm_block” reworded the description of “number” cosmetic
    • “evm_code” reworded the description of “address” cosmetic
    • “evm_ens” reworded the description of “address” cosmetic
    • “evm_erc20_balance” reworded the description of “chain” cosmetic
    • “evm_erc20_balance” reworded the description of “token” cosmetic
    • “evm_native_balance” reworded the description of “address” cosmetic
    • “evm_native_balance” reworded the description of “chain” cosmetic
    • “evm_nonce” reworded the description of “address” cosmetic
    • “evm_receipt” reworded the description of “chain” cosmetic
    • “evm_receipt” reworded the description of “hash” cosmetic
    • “evm_transaction” reworded the description of “chain” cosmetic
    • “evm_transaction” reworded the description of “hash” cosmetic
    • “pay_check” reworded the description of “amount” cosmetic
    • “pay_check” reworded the description of “to” cosmetic
    • “quote_swap” reworded the description of “amount” cosmetic
    • “quote_swap” reworded the description of “from_decimals” cosmetic
    • “quote_swap” reworded the description of “taker” cosmetic
    • “quote_swap” reworded the description of “to_decimals” cosmetic
    • “wallet_balance_batch” reworded the description of “chains” cosmetic
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 21 Nov 2026 · Probed https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/evm-wallet-onchain

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=x402-bazaar-rank-worker.workers.dev CN=YE2,O=Let's Encrypt,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA384 6c09b073fe5d3fd83fd987465725765b6e5
SANs: *.x402-bazaar-rank-worker.workers.dev, x402-bazaar-rank-worker.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. 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://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/evm-wallet-onchain Verified 200
http (plaintext) http://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/evm-wallet-onchain Served over HTTP 200
MCP tools · 12 exposed · ~2,546 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
evm_block ~181

Use when you need a block header on Base, Ethereum, Arbitrum, Polygon or Optimism: latest or a given number, with hash, parent, timestamp, miner, gas used/limit. Returns the paid x402 request for your input (GET /evm/block, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Block header only; for one transaction use evm_transaction or evm_receipt. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
chainstring–Chain; default base
numberstring–Decimal or 0x-hex block number, or latest (default); a block the node does not have yet is refused before any charge

No output schema declared.

No examples provided.

evm_code ~185

Use when you need to know whether an address is a contract on Base, Ethereum, Arbitrum, Polygon or Optimism: is_contract, bytecode size, sha256 of the bytecode. Returns the paid x402 request for your input (GET /evm/code, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Contract check with bytecode size and hash only; for the coin balance use evm_native_balance, for the transaction count use evm_nonce. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
addressstringyesAddress to test for contract code (0x + 40 hex); a plain account returns is_contract=false
chainstring–Chain; default base

No output schema declared.

No examples provided.

evm_ens ~179

Use when you need ENS on Ethereum: name to address (name=vitalik.eth, via the Universal Resolver, with resolver address) or address to primary name (address=0x..., reverse record, forward-verified). Returns the paid x402 request for your input (GET /evm/ens, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
addressstring–0x address for the reverse (primary name) lookup instead of name; if both are given, name is used. Read on Ethereum
namestring–ENS name (lowercase labels), e.g. vitalik.eth

No output schema declared.

No examples provided.

evm_erc20_balance ~206

Use when you need one ERC-20 balance for one wallet: balanceOf, decimals and symbol read in a single multicall on Base, Ethereum, Arbitrum, Polygon or Optimism, with raw units, a decimal amount. Returns the paid x402 request for your input (GET /evm/erc20-balance, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. One token on one chain; for several tokens or chains at once use wallet_balance. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
addressstringyesWallet address (0x + 40 hex)
chainstring–Chain where the token is deployed; default base
tokenstringyesERC-20 contract address on the chosen chain; a non-token address is refused before any charge

No output schema declared.

No examples provided.

evm_native_balance ~189

Use when you need the native coin balance (ETH or POL) of an address on Base, Ethereum, Arbitrum, Polygon or Optimism: wei and a decimal amount from a public node, with the block number and as_of. Returns the paid x402 request for your input (GET /evm/native-balance, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Native coin on one chain only; for stablecoins or several chains use wallet_balance. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
addressstringyesAccount whose native coin balance is read (0x + 40 hex)
chainstring–Chain to read; the coin is ETH, or POL on polygon; default base

No output schema declared.

No examples provided.

evm_nonce ~192

Use when you need an account's transaction count on Base, Ethereum, Arbitrum, Polygon or Optimism: nonce at the latest block and the pending nonce (queued transactions in the node's pool). Returns the paid x402 request for your input (GET /evm/nonce, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Transaction count (latest and pending) only; for the coin balance use evm_native_balance, for a transaction by hash use evm_transaction or evm_receipt. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
addressstringyesAccount whose nonce is read (0x + 40 hex); returns the latest nonce and the pending nonce
chainstring–Chain; default base

No output schema declared.

No examples provided.

evm_receipt ~200

Use when you need to know whether a transaction succeeded on Base, Ethereum, Arbitrum, Polygon or Optimism: receipt status, block, confirmations, gas used, effective gas price. Returns the paid x402 request for your input (GET /evm/receipt, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Status and logs of a mined transaction; for the transaction fields (from, to, value, input) use evm_transaction; to check a payment amount use pay_check. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
chainstring–Chain to look the transaction up on; default base
hashstringyesTransaction hash (0x + 64 hex); a transaction with no receipt yet (pending) is refused before any charge

No output schema declared.

No examples provided.

evm_transaction ~217

Use when you need a transaction by hash on Base, Ethereum, Arbitrum, Polygon or Optimism: from, to, value, nonce, gas and fee fields, block, confirmations, method id and input (first 1 KB). Returns the paid x402 request for your input (GET /evm/tx, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Raw transaction fields (from, to, value, input); to know whether it succeeded (status, gas used, logs) use evm_receipt; to check a payment amount use pay_check. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
chainstring–Chain to look the transaction up on; default base
hashstringyesTransaction hash (0x + 64 hex); looked up on the chosen chain only; not found there: refused before any charge

No output schema declared.

No examples provided.

pay_check ~254

Use when you need to confirm that a transaction paid at least an amount of an asset to an address: pass tx, to, amount and asset. Returns the paid x402 request for your input (GET /pay/check, $0.003 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Checks a payment against an expected recipient and amount; for raw transaction fields use evm_transaction, for status and logs use evm_receipt. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
amountstringyesMinimum amount in asset units (not base units), e.g. 0.01; paid >= amount gives verified=true
assetstringyesUSDC, USDT, DAI, WETH, WBTC, cbBTC, ETH, POL or a listed token address
chainstring–ethereum, base, arbitrum or polygon (optional for EVM)
tostringyesExpected recipient; transfers to other addresses do not count
txstringyestransaction hash (0x + 64 hex for EVM)

No output schema declared.

No examples provided.

quote_swap ~378

Use for a DEX swap quote with a ready unsigned transaction: best route from Velora (ParaSwap), KyberSwap as fallback, on Base, Arbitrum, Ethereum, Optimism, Polygon, BNB Chain. Returns the paid x402 request for your input (GET /quote/swap, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Quote only: nothing is signed or sent, and the reply discloses P0's integrator fee. To check balances first use wallet_balance. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
amountstringyesInteger string, amount to sell in base units (10 USDC = 10000000)
chainstringyesbase, arbitrum, ethereum, optimism, polygon or bsc (or chain id)
fromstringyestoken to sell: symbol (USDC, WETH, ETH...) or 0x address
from_decimalsinteger–Decimals of the sell token; needed only when it is an address P0 does not know
slippage_bpsinteger–max slippage in basis points (50 = 0.5%). The alias 'slippage' is read as basis points too (Velora's unit); a 'slippage' below 10 is refused as ambiguous
takerstringyesWallet that will sign and send; the returned calldata and approval are built for it
tostringyestoken to buy: symbol or 0x address
to_decimalsinteger–Decimals of the buy token; needed only when it is an address P0 does not know

No output schema declared.

No examples provided.

wallet_balance ~216

Use when you need a wallet's token balances on several chains in one call: native coin plus USDC, USDT, DAI, WETH, WBTC/cbBTC on Ethereum, Base, Arbitrum and Polygon. Returns the paid x402 request for your input (GET /wallet/balance, $0.003 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one token on one chain use evm_erc20_balance; for the native coin on one chain use evm_native_balance; for many wallets use wallet_balance_batch. First call each day returns the data itself, free; later calls return the paid request.

NameTypeReqDescription
addressstringyes0x address or ENS name (lowercase a-z, 0-9, hyphen)
chainsstring–comma list of ethereum, base, arbitrum, polygon (default: all EVM chains for a 0x address)

No output schema declared.

No examples provided.

wallet_balance_batch ~149

Use when you need native and stablecoin balances for a list of wallets: up to 25 addresses (0x or ENS names) in one POST. Returns the paid x402 request for your input (POST /wallet/balance/batch, $0.075 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one wallet use wallet_balance.

NameTypeReqDescription
addressesarrayyes1 to 25 addresses; duplicates are removed
chainsstring–Optional comma list applied to every address (ethereum, base, arbitrum, polygon); default all EVM chains

No output schema declared.

No examples provided.

Install

How do I install the P0: wallet balances and EVM reads MCP server?

P0: wallet balances and EVM reads is a hosted endpoint at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/evm-wallet-onchain, 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 · x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-x402-bazaar-rank-worker-x402-bazaar- 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/evm-wallet-onchain'
Common questions

What is the P0: wallet balances and EVM reads MCP server?

P0: wallet balances and EVM reads is an MCP server listed in the public MCP registry as dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/evm-wa…. Wallet balances, ERC-20, blocks, transactions, receipts, ENS and payment checks, pay per call. This page covers its hosted endpoint (https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/evm-wallet-onchain).

Is the P0: wallet balances and EVM reads MCP server safe to use?

P0: wallet balances and EVM reads scores 68 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 P0: wallet balances and EVM reads MCP server expose?

P0: wallet balances and EVM reads exposes 12 tools: wallet_balance, wallet_balance_batch, pay_check, quote_swap, evm_erc20_balance, and 7 more. Their descriptions and schemas cost roughly 2,546 tokens of context every time the server is loaded.

Does the P0: wallet balances and EVM reads MCP server require authentication?

No. We connected to P0: wallet balances and EVM reads without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the P0: wallet balances and EVM reads MCP server still maintained?

P0: wallet balances and EVM reads 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 P0: wallet balances and EVM reads MCP server?

VerifyMCP ran 13 checks on P0: wallet balances and EVM reads, 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.