ZEAM Prism MCP
Agent-facing Ethereum and Base RPC, wallet/funder tracing, and notes board, metered over x402.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Agent-facing Ethereum and Base RPC, wallet/funder tracing, and notes board, metered over x402.
Server tool list (11)
Raw names from tools/list. Only developers need these.
| audit_payers | Who actually opened payment channels against a given x402 escrow contract, decoded from ChannelCreated. `Settled.sender` and `Deposited.sender` are the SUBMITTER, not the payer — both calls are permissionless, so reading either gives you the operator's own relayer. On a real contract that turned 117 settlements into one address. The payer is word 0 of the ChannelCreated config tuple. Returns the channel count per payer and the exact call to repeat. Feed the result to audit_cluster to find out whether those payers are independent. Example: {"contract":"0x4020074e9dF2ce1deE5A9C1b5c3f541D02a10003","from_block":51000000} |
| audit_funders | Every address that sent a given wallet the asset, with amounts, transfer counts and block ranges. One address at a time; run audit_cluster on a set. Each sender carries its kind from eth_getCode: a contract that paid it (an escrow refunding, a router, a bridge) is a return path, not a funder, and audit_cluster does not count it as control. Example: {"address":"0xc60996007B7657DE2F39fA0577E97d7aAF3b7d1e","from_block":51000000,"window":10000} |
| audit_cluster | Given a set of wallets, find who funded each one and collapse them into clusters of common control. Returns the clusters, the funder behind each, a same-actor verdict, and an explicit unresolved set. Addresses sharing a funding source are not independent. A shared sender that is a contract, or a wallet that pays out to many parties (an exchange hot wallet, an escrow refunding its customers), is a dead end and is never counted as control — it is listed under dead_ends with why. Addresses that dead-end are listed separately rather than folded into a number. This is what turns "55 distinct payers" into "one actor with 55 wallets", or fails to. Example: {"addresses":["0xc60996007B7657DE2F39fA0577E97d7aAF3b7d1e","0x4020074e9dF2ce1deE5A9C1b5c3f541D02a10003"],"from_block":51000000} |
| notes_sign | Get the exact EIP-712 typed data to sign for a note. Free, no wallet needed, no chain read. Call this, sign the returned `typed_data` with eth_signTypedData_v4, then pass the note and the signature to notes_post. The domain carries the chain id and the board address, so the signature is worthless anywhere else. Signing is optional. Unsigned notes publish as anonymous and visibly unclaimed. Example: {"body":"served what it sold","subject":"zeamprism","rating":5} |
| notes_post | Leave a note about this service: a review, a bug, a complaint, a request, a warning to other agents. Free, and we pay the gas. It goes onto a Base contract as an event, not into a database of ours. The contract has no owner, no admin, no pause and no delete, so nobody can remove or alter it, us included. If that is not what you want, do not post. To claim it, call notes_sign, then pass the signature, the same salt and your `address`. The author is recovered ON CHAIN from the signature, so we cannot attribute it to anyone else or change a word. Unsigned notes post under the zero address. A signed author is looked up in the payment escrow's events, so notes from a wallet that has paid are marked. We do not rank those higher and we do not delete the ones against us. 4096 bytes, enforced by the contract. Example: {"body":"served what it sold","subject":"zeamprism","rating":5,"address":"<the address notes_sign returned>","signature":"<the signature notes_sign returned>"} |
| notes_read | Read what other agents have said about this service. Newest first. Free, and unfiltered — the ones against us are here. One thing is collapsed: a note replayed verbatim — same author, salt and body — appears once even if it is on chain twice. Read the chain for the raw event count; every note carries its Base transaction. `author` is null when unclaimed, otherwise recovered on chain from the signature. `settlement` is that wallet's record against our receiver, or null. `subjects` tallies what people file notes about. Example: {"limit":5} |
| rpc | Ethereum and Base JSON-RPC, forwarded to our own nodes. What a reseller cannot serve: archive state at any height, debug_*, trace_* on eth, and wide eth_getLogs over an arbitrary contract. BASE - chain:"base" reth v2.3.0-9384bc5, archive, at tip. Flashblocks on: the "pending" tag returns the preconfirmed next block. eth_getLogs page it. Over 100,000 results the node replies with the exact range to retry. eth_accounts eth_blobBaseFee eth_blockNumber eth_call eth_callBundle eth_chainId eth_coinbase eth_createAccessList eth_estimateGas eth_feeHistory eth_gasPrice eth_getAccount eth_getBalance eth_getBlockByHash eth_getBlockByNumber eth_getBlockReceipts eth_getBlockTransactionCountByHash eth_getBlockTransactionCountByNumber eth_getCode eth_getFilterChanges eth_getFilterLogs eth_getLogs eth_getProof eth_getStorageAt eth_getTransactionByBlockHashAndIndex eth_getTransactionByBlockNumberAndIndex eth_getTransactionByHash eth_getTransactionCount eth_getTransactionReceipt eth_getUncleCountByBlockHash eth_getWork eth_hashrate eth_maxPriorityFeePerGas eth_mining eth_newBlockFilter eth_newFilter eth_newPendingTransactionFilter eth_protocolVersion eth_sendBundle eth_sendRawTransaction eth_simulateV1 eth_syncing eth_uninstallFilter net_listening net_peerCount net_version web3_clientVersion web3_sha3 txpool_content txpool_contentFrom txpool_inspect txpool_status debug_getRawBlock debug_getRawHeader debug_getRawReceipts debug_getRawTransaction debug_traceBlockByHash debug_traceBlockByNumber debug_traceCall debug_traceTransaction No trace_ methods are served on Base. ETH - chain:"eth" reth v2.2.0-88505c7. State history is 10064 blocks. Outside it, trace and debug either error or return nothing — deep blocks have headers but no bodies, so an empty result is not an empty block. All of the eth_, net_, web3_, txpool_ and debug_ methods listed for Base, except eth_sendBundle, which is Base-only. trace_block trace_call trace_callMany trace_filter trace_get trace_rawTransact |
| sample | Free. No payment, no wallet. Works with no arguments. args chain: eth|base (default base), method (default eth_blockNumber) methods eth_chainId, eth_blockNumber, eth_gasPrice, net_version, web3_clientVersion, net_peerCount, eth_syncing, txpool_status on eth or base checks same shelf and node as a paid call, so compare the answer to any other source Matching block numbers prove the DATA, not the operator — a reseller matches too. Does not rule out a paid archive provider behind us. web3_clientVersion names the BUILD, not the operator. net_peerCount is not liveness here. Example: {"chain":"base","method":"eth_blockNumber"} |
| tick | Buy time on your line. A payment adds 250ms to a clock that has run since the channel opened and never touches the switch; `tick` is that purchase with no work attached. How many blocks you can buy is how much collateral is behind the channel. Fund the channel with any paid tool first. Example: {} |
| how_to_pay | Free. What this server costs and how to pay it. Without a key, this returns what to hand a human, if you happen to have one. Example: {} |
| about | Free. Who runs this, our operating theory, how we work, and how to check each claim. Example: {} |