Ankr Agent RPC MCP Server
Registry code: 5a2dbc75d7f7cecc
Blockchain READ tools for ONE Ankr API key: the key presented when this session was opened. Six contracts apply across every tool here, so they are stated once instead of in each description.
1. THE BOUND KEY. That binding is fixed for the life of the session, so a key obtained later, for example one created through the Ankr management MCP server, is not reachable from these tools until a NEW session is opened presenting it. There is deliberately no per-call key argument: the bound key is part of this session's identity and is re-checked on every request, so a session that could be repointed…
- endpoint
- https://mcp.ankr.com/rpc
- protocol
- http-sse ·2025-06-18
- authentication
- bearer
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Ankr Agent RPC MCP Server live?
- No — it has stopped answering the hub's checks (checked 4h ago). It answered 97% of checks over the last 30 days.
- Is Ankr Agent RPC MCP Server free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does Ankr Agent RPC MCP Server have?
- 25 tools: suiGetObjects, describeMethods, searchChain, suiGetFunction, expandResult, getAccountBalance, suiListDynamicFields, getBalances, ….
- Is Ankr Agent RPC MCP Server safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 97.9%· all time 97.9%
last good check
of 25 tools
- degraded → down· fetch failed
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- query blockchain data via rpc
- decode contract call results
- get token balances
- takes → gives
- text, data → data
- note
- resells another provider
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
suiWatchEvents 0.001 0x7547…b603 paid 3d ago
Follow Move events from now on, by POLLING — nothing is pushed. This first call only establishes a start position: it reads the executed tip from a Sui event subscription, returns NO events, and hands back a cursor. Each expandResult on that cursor lists what has been emitted since and returns the next one, so no event falls in the gap between two polls. That is the whole difference from getLogs, which scans a checkpoint range you name and cannot resume across calls. Filter by address (the emitting package[::module]), eventType and sender; rows and body keys are getLogs'. Sui executes about 4 checkpoints a second, so poll on that scale; `more_available: true` means the cap was already full, so poll again at once. 50 events a poll unless asked otherwise, 1000 at the outside. Reads only.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "sender": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$", "description": "The emitting transaction's sender, 0x + 64 hex" }, "address": { "type": "string", "pattern": "^0x[a-fA-F0-9]{1,64}(::\\w+)?$", "description": "Emitting Move code: package, or package::module" }, "maxLogs": { "type": "integer", "maximum": 1000, "description": "Max events to DISPLAY per poll (default 50, max 1000).", "exclusiveMinimum": 0 }, "eventType": { "type": "string", "maxLength": 300, "description": "Move event type 0xpkg::module::Name" } }, "additionalProperties": false }arguments 28 linesgetTokenPrice 0.001 0x7547…b603 paid 3d ago
USD price of a token on one blockchain: pass a contract address for an ERC-20, or leave it empty for the native coin. Returns { chain, asset, usd, priced_via_contract, as_of: { timestamp, blockNumber, lag, status } }. Read as_of before reporting a price; it says how stale the indexer's view is. A native-coin query is priced from the WRAPPED token, which is why priced_via_contract is a wrapped-token address rather than the coin itself.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "chain": { "enum": [ "arbitrum", "avalanche", "avalanche_fuji", "base", "base_sepolia", "bsc", "eth", "eth_sepolia", "fantom", "flare", "gnosis", "linea", "optimism", "optimism_sepolia", "polygon", "polygon_amoy", "rollux", "scroll", "story_aeneid_testnet", "story_mainnet", "syscoin", "taiko", "telos", "xai", "xlayer" ], "type": "string", "description": "Chain slug, e.g. eth, bsc, polygon." }, "blockchain": { "enum": [ "arbitrum", "avalanche", "avalanche_fuji", "base", "base_sepolia", "bsc", "eth", "eth_sepolia", "fantom", "flare", "gnosis", "linea", "optimism", "optimism_sepolia", "polygon", "polygon_amoy", "rollux", "scroll", "story_aeneid_testnet", "story_mainnet", "syscoin", "taiko", "telos", "xai", "xlayer" ], "type": "string", "description": "DEPRECATED alias for `chain`. Use `chain`." }, "contractAddress": { "type": "string", "pattern": "^0x[a-fA-F0-9]{40}$", "description": "Contract address of the token. Leave empty for native coin." } }, "additionalProperties": false }arguments 74 linessuiResolveName 0.001 0x7547…b603 paid 3d ago
Resolve a SuiNS name (something.sui) to the address it points at, or an address back to its name. Give exactly one of `name` or `address`. READ `status` BEFORE the record. It is one of: resolved, the registration is live and the record is good; expired, the registration lapsed and the record — target address included — is returned but must not be trusted as a destination; no_target_address, the name is registered and points nowhere; not_registered, the registry holds no record. All four are answers, not errors. Reverse is NOT the inverse: an address answers with its OWN default name, which need not be a name pointing at it. One record comes back, so nothing is capped, truncated or paged. Only .sui names.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "name": { "type": "string", "pattern": "^[a-z0-9][a-z0-9.-]{0,251}\\.sui$", "maxLength": 255, "description": "Forward: a .sui name" }, "address": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$", "description": "Reverse: a Sui address" } }, "additionalProperties": false }arguments 18 lineslistChains open 3d ago
Which chains each tool family reaches. aapiChains is where the indexer tools work (getAccountBalance, getWalletActivity, getNFTs, getTokenHolders, getTokenPrice, getTokenPriceHistory); call this before one of them on an unfamiliar chain. suiChains are answered over gRPC, by the sui* tools and the generic tools the reply's suiNote names. Raw-RPC tools (getTransaction, getLogs, getBlock) and rpcCall are not limited to these lists: they take any rpc.ankr.com/<chain> slug, 200+ chains. Each reply reports how it was shaped in _meta.tier and _meta.tier_source.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {}, "additionalProperties": false }arguments 6 linessuiGetObjects unknown 3d ago
Move objects by id, in ONE batch call: each answer carries the object's id, type, version, owner and its decoded Move fields under json. Up to 50 ids per request and nothing is trimmed from the reply, so no cursor is issued. An id the node cannot serve is reported POSITIONALLY under failed, with its request index, the id asked for and the gRPC status, never dropped in silence. Reads only.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "ids" ], "properties": { "ids": { "type": "array", "items": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$" }, "maxItems": 50, "minItems": 1, "description": "Object ids to read, 50 at most. Order is preserved and a failure keeps its position." }, "version": { "type": "string", "pattern": "^\\d+$", "description": "Read this past version instead of the live object. A decimal string, because an object version is a u64. Single id only." } }, "additionalProperties": false }arguments 25 linesdescribeMethods unknown 3d ago
What a JSON-RPC method takes, and whether this key can actually call it on this chain. Returns the positional param shape and a worked example for every method rpcCall can validate, plus rpcCall's own verdict (permitted, or refused as a write path). Pass probe:true with an explicit methods list (max 12) to also ask the node, so served reflects your key, your tenant and the chain's blockchain schema instead of a guess: yes, no, restricted, or unknown. A refused method is never sent. Without methods it returns the whole catalogue and does not probe. The catalogue is SHAPE guidance, not a coverage list: a method missing from it may still be served, and the chain's schema is the authority.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain" ], "properties": { "chain": { "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$", "maxLength": 64, "description": "Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)" }, "probe": { "type": "boolean", "description": "Ask the node whether each method is served (needs methods)" }, "methods": { "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z][A-Za-z0-9_.]*$", "description": "JSON-RPC method, e.g. eth_call, eth_estimateGas, Filecoin.ChainHead" }, "maxItems": 12, "minItems": 1, "description": "Methods to describe (max 12); omit for the whole catalogue" } }, "additionalProperties": false }arguments 31 linessearchChain unknown 3d ago
Resolve an on-chain IDENTIFIER to the object it names. Accepts exactly THREE shapes, and nothing else: - 0x + 64 hex -> transaction (falls back to block hash if there is no such tx) - 0x + 40 hex -> address (reports contract vs EOA) - all digits -> block number NOT SUPPORTED: ticker symbols, token or contract NAMES, labels, or any other free-form text. "USDC", "uniswap" and "the biggest holder" all return kind:"unknown" with a note, because that needs a label registry this server does not have. ENS names (*.eth) are also NOT resolved; they return kind:"ens" with a note. Do not call this tool to look up an asset by name; get the contract address another way first. A transaction or block resolution requests tier-2 decoding; an address lookup is passthrough. Defaults to eth when no chain is given.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "chain": { "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$", "maxLength": 64, "description": "Chain (default eth)" }, "query": { "type": "string", "description": "0x tx/block hash, 0x address, or block number. ENS names are NOT resolved: they come back as kind:\"ens\" with a note." } }, "additionalProperties": false }arguments 20 linessuiGetFunction unknown 3d ago
One Move function's signature: visibility, whether it is an entry function, its type parameters, its parameter types and its return types — what a programmable transaction block needs in order to call it. Never capped or paged. Take the package and module names from suiGetPackage. A name the package does not declare is refused by the node rather than approximated.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "package", "module", "function" ], "properties": { "module": { "type": "string", "pattern": "^[A-Za-z]\\w{0,127}$", "description": "Module name" }, "package": { "type": "string", "pattern": "^0x[0-9a-fA-F]{1,64}$", "description": "Package id (0x2 is the framework)" }, "function": { "type": "string", "pattern": "^[A-Za-z]\\w{0,127}$", "description": "Function name" } }, "additionalProperties": false }arguments 27 linesexpandResult unknown 2d ago
Continue a paged result using the opaque cursor returned by a previous tool call. Supported cursor sources: getWalletActivity, getLogs (a block range, or a Sui checkpoint scan), getBalances (asset offset), Sui views (tier 0 re-reads the view unshaped: a fresh upstream call, never a replay of the earlier answer). Returns the next page of compact items plus a new cursor if more remains.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "cursor" ], "properties": { "cursor": { "type": "string", "description": "The opaque cursor string from a previous tool result" } }, "additionalProperties": false }arguments 14 linesgetAccountBalance unknown 2d ago
Balance of an account across many blockchains, by 0x address or ENS name, via the Ankr Advanced API indexer. Assets are ranked by USD value descending and only the top 20 are listed by default (a real wallet can hold 1000+ assets, over half of them priced at $0); tune that with maxTokens/minUsd, or call getBalances for structured JSON. Anything the indexer PRICED at zero or below minUsd is summarised as a dust count instead of being listed. An asset with NO indexer price is not dust: it reads "USD value unknown" and ranks after every priced asset, so on a wallet holding more priced assets than maxTokens none appear here and the note says how many exist off-page. Unknown is not zero. An implausibly large raw balance (typical of scam tokens minting max-uint) is flagged and its balance is withheld; never add it to a total. Each line names the chain the asset is held on, which matters because omitting `blockchains` queries EVERY chain and interleaves the result across them.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "address" ], "properties": { "minUsd": { "type": "number", "minimum": 0, "description": "Only list assets worth at least this many USD; the rest are summarised as dust." }, "address": { "type": "string", "description": "Wallet address (0x...) or ENS name (*.eth)" }, "maxTokens": { "type": "integer", "maximum": 100, "description": "Max assets to list, sorted by USD value descending (default 20, max 100).", "exclusiveMinimum": 0 }, "blockchains": { "type": "array", "items": { "enum": [ "arbitrum", "avalanche", "avalanche_fuji", "base", "base_sepolia", "bsc", "eth", "eth_sepolia", "fantom", "flare", "gnosis", "linea", "optimism", "optimism_sepolia", "polygon", "polygon_amoy", "rollux", "scroll", "story_aeneid_testnet", "story_mainnet", "syscoin", "taiko", "telos", "xai", "xlayer" ], "type": "string" }, "description": "Chains to query; omit to query every chain" } }, "additionalProperties": false }arguments 59 linessuiListDynamicFields unknown 2d ago
Whatever a Move package stored under one object's UID: tables, bags and dynamic object fields, listed from the parent id. A row names the field's own object id, its kind, the name it is keyed by and the Move type of its value. The value itself is a BCS blob and is left out of this answer; hand that field id to suiGetObjects and it comes back decoded. 50 rows unless asked otherwise and 200 at the outside, with a cursor for as long as the parent has more. Reads only.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "parent" ], "properties": { "parent": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$", "description": "The id of the object whose dynamic fields are listed." }, "pageSize": { "type": "integer", "maximum": 200, "description": "How many fields to return (default 50, max 200). The tail is reachable through the returned cursor.", "exclusiveMinimum": 0 } }, "additionalProperties": false }arguments 21 linesgetBalances unknown 2d ago
An address's balances on ONE chain: native via eth_getBalance plus, by default, ERC-20 balances with USD from the Ankr Advanced API indexer (tier 0). ENS resolves for the token lookup only; a raw-RPC-only chain returns native alone. Tokens rank by USD descending, top 20 by default; tune with maxTokens/minUsd. Anything PRICED at zero or below minUsd goes to `dust` (count + USD total); `full_count` is how many assets exist. UNPRICED assets are not dust: usd: null, unpriced: true, ranked after every priced one, counted by `unpriced_on_page`/`unpriced_total`, never summed. A raw balance >=2^128 is `implausible: true`, formatted balance WITHHELD. Sui: none of that applies. Balances come from the node, RAW in base units; `decimals`/`symbol` only where the coin publishes metadata (first 10 types). No USD, dust or ENS; `native` is SUI, maxTokens caps the token rows, minUsd/includeTokens do nothing.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "address" ], "properties": { "chain": { "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$", "maxLength": 64, "description": "Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)" }, "minUsd": { "type": "number", "minimum": 0, "description": "Only list tokens worth at least this many USD; everything below is bucketed into `dust`. Defaults to excluding only exactly-zero-value tokens." }, "address": { "type": "string", "description": "Address (0x...) or ENS name" }, "maxTokens": { "type": "integer", "maximum": 100, "description": "Max entries in `tokens` (default 20, max 100). EVM ranks them by USD, tail behind the cursor, and counts the native coin as one of them (repeating `native`); Sui does not, so all are other coin types.", "exclusiveMinimum": 0 }, "includeTokens": { "type": "boolean", "description": "Include ERC-20 token balances via AAPI (default true)" } }, "additionalProperties": false }arguments 36 linessuiSimulateTransaction unknown 4d ago
Run a transaction against current state and report what it WOULD do, without submitting it: whether it succeeds or which Move abort stops it and in which command, the gas it consumes, the objects it creates, mutates and deletes, the balance changes per address and coin, each command's return values decoded, and any events it would emit. Takes the base64 BCS TransactionData your wallet or SDK produces — the same argument sui_dryRunTransactionBlock takes; no signature, and none is accepted. Nothing is broadcast: this server cannot reach Sui's execute rpc at all. `cursor` re-runs it unshaped through expandResult. Reads only.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "transactionBytes" ], "properties": { "transactionBytes": { "type": "string", "pattern": "^[A-Za-z0-9+/]+={0,2}$", "maxLength": 174764, "minLength": 1, "description": "The transaction to simulate: a base64 BCS TransactionData." } }, "additionalProperties": false }arguments 17 linesgetTokenHolders unknown 3d ago
Who holds an ERC-20 token on one chain, largest balance first, plus the total holder count. `balance` already has decimals applied, so do not divide it again. For one wallet's tokens use getBalances.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "contractAddress" ], "properties": { "chain": { "enum": [ "arbitrum", "avalanche", "avalanche_fuji", "base", "base_sepolia", "bsc", "eth", "eth_sepolia", "fantom", "flare", "gnosis", "linea", "optimism", "optimism_sepolia", "polygon", "polygon_amoy", "rollux", "scroll", "story_aeneid_testnet", "story_mainnet", "syscoin", "taiko", "telos", "xai", "xlayer" ], "type": "string", "description": "Chain, from listChains aapiChains" }, "pageSize": { "type": "integer", "maximum": 100, "description": "Holders per page (default 20)", "exclusiveMinimum": 0 }, "pageToken": { "type": "string", "description": "nextPageToken from the previous page" }, "contractAddress": { "type": "string", "pattern": "^0x[a-fA-F0-9]{40}$", "description": "ERC-20 token contract address" } }, "additionalProperties": false }arguments 57 linesgetTokenPriceHistory unknown 3d ago
Historical USD price series for a token contract on a chain, via the Ankr Advanced API indexer: a list of { timestamp, usd, block } quotes. `limit_applied` reports the cap the call was actually made with (default 100, max 1000). When `count` reaches that cap the response sets `possibly_truncated: true`: this endpoint returns NO continuation token, so a clipped series and a series that simply ends are indistinguishable, and there is no cursor to page with. Treat such a series as incomplete-of-unknown-length rather than the full history; raise `limit` or walk `fromTimestamp`/`toTimestamp` yourself.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "contractAddress" ], "properties": { "chain": { "enum": [ "arbitrum", "avalanche", "avalanche_fuji", "base", "base_sepolia", "bsc", "eth", "eth_sepolia", "fantom", "flare", "gnosis", "linea", "optimism", "optimism_sepolia", "polygon", "polygon_amoy", "rollux", "scroll", "story_aeneid_testnet", "story_mainnet", "syscoin", "taiko", "telos", "xai", "xlayer" ], "type": "string", "description": "Chain, from listChains aapiChains" }, "limit": { "type": "integer", "maximum": 1000, "description": "Max quotes (default 100)", "exclusiveMinimum": 0 }, "interval": { "type": "integer", "maximum": 9007199254740991, "description": "Interval between quotes, in seconds", "exclusiveMinimum": 0 }, "toTimestamp": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "End UNIX timestamp (seconds)" }, "fromTimestamp": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "Start UNIX timestamp (seconds)" }, "contractAddress": { "type": "string", "pattern": "^0x[a-fA-F0-9]{40}$", "description": "ERC-20 token contract address" } }, "additionalProperties": false }arguments 71 linessuiGetPackage unknown 3d ago
What a published Move package declares, so a caller can pick what to inspect next. By default this answers with an INDEX: one row per module carrying its name and how many functions and datatypes it holds, capped at 50 rows (raise it with maxModules). Pass `module` to get that one module in full instead — every function signature and every datatype it declares. The whole package is never returned; the 0x2 framework alone is around 484 KB. This method has no upstream paging, so a truncated index carries no cursor: the way past the cap is maxModules, then `module`, then suiGetFunction for a single signature. Repeated addresses arrive as `$n`/`@n` handles, resolved by the ids and packages tables beside them.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "package" ], "properties": { "module": { "type": "string", "pattern": "^[A-Za-z]\\w{0,127}$", "description": "One module to return in full" }, "package": { "type": "string", "pattern": "^0x[0-9a-fA-F]{1,64}$", "description": "Package id (0x2 is the framework)" }, "maxModules": { "type": "integer", "maximum": 500, "description": "Rows the index lists before it truncates (default 50). Ignored when `module` is given.", "exclusiveMinimum": 0 } }, "additionalProperties": false }arguments 26 linessuiListOwnedObjects unknown 2d ago
Every object an address owns, page by page, out of the node's own owner index. Narrow it with type: a bare Move type such as 0x2::coin::Coin matches any type parameter, while a fully applied one matches only that instantiation. A page holds 50 entries by default and 200 at most; when the node holds more, an opaque cursor comes back and expandResult returns the following page in this same shape. Reads only.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "owner" ], "properties": { "type": { "type": "string", "maxLength": 300, "minLength": 3, "description": "Move type filter, with or without its type parameters. Omit to list every owned object." }, "owner": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$", "description": "The owning address." }, "pageSize": { "type": "integer", "maximum": 200, "description": "How many objects to return (default 50, max 200). The tail is reachable through the returned cursor.", "exclusiveMinimum": 0 } }, "additionalProperties": false }arguments 27 linesrpcCall unknown 3d ago
Call ANY JSON-RPC method on a supported chain: the escape hatch beyond the routed tools (eth_call, eth_estimateGas, eth_getCode, debug_trace*, trace_*). Prefer getTransaction/getLogs/getBlock where they fit. TORPC tier is negotiated per call (contract 2); check _meta.tier. This is a read/data tool, never a wallet. It REFUSES anything that would change state, on every chain family: transaction broadcast and signing (eth_sendRawTransaction, MEV bundle/private-tx, personal_*/eth_sign*, Solana sendTransaction/requestAirdrop, BTC sendrawtransaction and bumpfee/psbtbumpfee, Sui sui_executeTransactionBlock, XRPL submit, Tron broadcasttransaction/createtransaction/triggersmartcontract, Cosmos broadcast_tx_*); transaction BUILDING, which returns an unsigned transaction rather than sending one (Sui's unsafe_* namespace); node administration and dev-node state (admin_*, miner_*, personal_*, hardhat_*, anvil_*, evm_*, engine_*); any mutating verb (set*, write*, start*, stop*, compact*), which refuses settxfee, debug_setHead and debug_writeBlockProfile; the node-operation half of geth's debug namespace (profilers, chaindb compaction, file-writing traces), which the verb rule cannot reach when the mutating word sits mid-camelCase; bitcoind's node and wallet state controls (invalidateblock, reconsiderblock, preciousblock, pruneblockchain, rescanblockchain, abortrescan, generateblock); and, on dot-namespaced chains, mempool submission and the node's own wallet, multisig and administration families (Filecoin.MpoolPush, Filecoin.WalletExport). Sign and send with your own wallet or signer. On sui this tool speaks gRPC, not JSON-RPC: a bridged method is answered there, any other is REFUSED rather than sent to Sui's JSON-RPC, which Sui removes in mid-October 2026. describeMethods says which are bridged. Everything else is FORWARDED: this tool keeps no list of permitted reads, because which methods exist is decided per chain by the endpoint's blockchain schema and what you may call by your tenant. A forwarded read can still come back refused ("Method disabled, reason: restricted by blockchain schema") — that is the authoritative answer. Call listChains for coverage.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "method" ], "properties": { "tier": { "enum": [ 0, 1, 2 ], "type": "number", "description": "Requested TORPC tier (default 2)" }, "chain": { "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$", "maxLength": 64, "description": "Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)" }, "method": { "type": "string", "pattern": "^[a-zA-Z][A-Za-z0-9_.]*$", "description": "JSON-RPC method, e.g. eth_call, eth_estimateGas, Filecoin.ChainHead" }, "params": { "type": "array", "items": {}, "description": "Positional JSON-RPC params (default [])" } }, "additionalProperties": false }arguments 36 linesgetInteractions unknown 4d ago
List the blockchains an address has interacted with, via the Ankr Advanced API indexer. Cross-chain, so there is no chain argument. Useful as a first step before fetching balances or activity per chain.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "address" ], "properties": { "address": { "type": "string", "description": "Address (0x...) or ENS name" } }, "additionalProperties": false }arguments 14 linesgetBlock unknown 2d ago
Get a block by a 0x-64 hash, a block number (decimal or 0x-hex), or a tag (latest, finalized, safe, earliest, pending). Tier 2 drops the verbose header roots and bloom and, with includeTxs, ABI-decodes and compacts the embedded transactions. A large block with includeTxs may come back raw (hex); _meta.tier says which, and dropping includeTxs gets the header decoded. Sui: `block` is a checkpoint number or digest.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "block" ], "properties": { "block": { "anyOf": [ { "type": "integer", "maximum": 9007199254740991, "minimum": 0 }, { "type": "string" } ], "description": "Block number (decimal or 0x-hex), a 0x-64 block hash, or a tag. Above 2^53 pass a STRING — a JSON number that large is not exact." }, "chain": { "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$", "maxLength": 64, "description": "Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)" }, "includeTxs": { "type": "boolean", "description": "Include full (decoded) transactions instead of just hashes (default false)" } }, "additionalProperties": false }arguments 34 linesgetLogs unknown 4d ago
Event logs on one chain, filtered by address and/or topics over a block range. Tier 2 emits each log as { contract, event, args }, dropping logsBloom and per-log block duplication; an undecodable one stays raw as { address, topics, data, _event_unknown }. Check tier_degraded before reading `event` or `args`. With both bounds concrete block NUMBERS (toBlock may be omitted/"latest") the range is walked in ascending chunks, stopping once the display cap fills: the reply says `range_fully_scanned: false`, carries a cursor, and `note` says why. `more_available` means more logs were seen than shown; `full_count` appears only when the whole range was scanned. Any other bound is ONE unbounded eth_getLogs: no chunking, no cursor, liable to tier 0. Sui: Move events over a CHECKPOINT range. fromBlock is required; `address` is the emitting package[::module]; eventType and sender narrow it; `topics` is refused, not ignored. Same body; rows add checkpoint/digest/index.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain" ], "properties": { "chain": { "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$", "maxLength": 64, "description": "Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)" }, "sender": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$", "description": "Sui: the emitting transaction's sender, 0x + 64 hex" }, "topics": { "type": "array", "items": { "anyOf": [ { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$" }, { "type": "null" } ] }, "maxItems": 4, "description": "Topic filters (0x + 64 hex, or null to wildcard); topics[0] is the event signature hash. Max 4 slots." }, "address": { "type": "string", "pattern": "^0x[a-fA-F0-9]{1,64}(::\\w+)?$", "description": "Emitting contract; Sui: package[::module]" }, "maxLogs": { "type": "integer", "maximum": 1000, "description": "Max logs to DISPLAY (default 50, max 1000). The scan stops once this is filled, so it also bounds how much is fetched upstream.", "exclusiveMinimum": 0 }, "toBlock": { "anyOf": [ { "type": "integer", "maximum": 9007199254740991, "minimum": 0 }, { "type": "string" } ], "description": "To block: decimal, 0x-hex, or tag (default latest)" }, "eventType": { "type": "string", "maxLength": 300, "description": "Sui: Move event type 0xpkg::module::Name" }, "fromBlock": { "anyOf": [ { "type": "integer", "maximum": 9007199254740991, "minimum": 0 }, { "type": "string" } ], "description": "From block: decimal, 0x-hex, or tag (default latest)" } }, "additionalProperties": false }arguments 79 linesgetNFTs unknown 4d ago
NFTs one wallet holds on one chain: collection, name, token id, contract, standard (ERC721/1155), image URL. For fungible tokens use getBalances.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "address" ], "properties": { "chain": { "enum": [ "arbitrum", "avalanche", "avalanche_fuji", "base", "base_sepolia", "bsc", "eth", "eth_sepolia", "fantom", "flare", "gnosis", "linea", "optimism", "optimism_sepolia", "polygon", "polygon_amoy", "rollux", "scroll", "story_aeneid_testnet", "story_mainnet", "syscoin", "taiko", "telos", "xai", "xlayer" ], "type": "string", "description": "Chain, from listChains aapiChains" }, "address": { "type": "string", "description": "Owner wallet address (0x...) or ENS name" }, "pageSize": { "type": "integer", "maximum": 50, "description": "Items per page (default 20, max 50)", "exclusiveMinimum": 0 }, "pageToken": { "type": "string", "description": "nextPageToken from the previous page" } }, "additionalProperties": false }arguments 56 linesgetTransaction unknown 3d ago
Get a transaction by its hash on one blockchain, with tier-2 decoding requested. Check tier_degraded before reading `function` or `args`. By default the receipt is fetched too (status, gas used, decoded logs). Set include to "transaction" to skip it and halve the cost. Tier-2 field names: tx, block, block_hash, from, to, value, gas_limit, gas_price, gas_used, status ("success"|"failed"), function, args (named object), logs[] ({ contract, event, args } when decoded, else { address, topics, data, _event_unknown }). All numeric values are decimal strings and all addresses are EIP-55 checksummed. Sui: pass the digest; `include` is ignored.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "txHash" ], "properties": { "chain": { "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$", "maxLength": 64, "description": "Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)" }, "txHash": { "type": "string", "pattern": "^(0x[a-fA-F0-9]{64}|[1-9A-HJ-NP-Za-km-z]{32,44})$", "description": "Transaction hash (0x + 64 hex) or Sui digest" }, "include": { "enum": [ "transaction", "receipt", "all" ], "type": "string", "description": "Which parts to fetch. \"all\" (default) returns both the transaction and the receipt; \"transaction\" returns only eth_getTransactionByHash; \"receipt\" returns only eth_getTransactionReceipt." } }, "additionalProperties": false }arguments 31 linesgetWalletActivity unknown 3d ago
An address's recent transactions on one blockchain, newest first, via the Ankr Advanced API indexer. Items are returned under `activity`, exactly once per page, on this first page and on every continuation alike. There is no second alias key. Each item: hash, from, to, value_wei (decimal string, RAW WEI, not ether and not token units), block (decimal), time { unix_seconds, iso }, status ("success"/"failed"), and selector (the raw 4-byte function selector, e.g. "0xa9059cbb"). The selector is NOT a resolved function name: this indexer does not return one, and mapping a selector to a name needs a signature registry this server does not have. A field is omitted rather than guessed when the upstream value is missing. `time.unix_seconds` is always the authoritative value; `time.iso` is present ONLY when the timestamp is a real calendar instant, and otherwise `time.iso_unavailable` says why, so new Date(time.iso) never yields an Invalid Date. Sui: transactions SENT BY the address.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "address" ], "properties": { "chain": { "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$", "maxLength": 64, "description": "Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)" }, "address": { "type": "string", "description": "Wallet address (0x...) or ENS name" }, "pageSize": { "type": "integer", "maximum": 100, "description": "Items per page (default 25, max 100)", "exclusiveMinimum": 0 } }, "additionalProperties": false }arguments 27 linesresolveContract unknown 3d ago
Inspect an address on a chain: whether it is a contract, best-effort ERC-20 token metadata (name, symbol, decimals), and EIP-1967 proxy detection (implementation address). Built from eth_getCode / eth_call / eth_getStorageAt, which are plain JSON-RPC passthrough. The metadata is best-effort and may be absent on a non-standard contract.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "chain", "address" ], "properties": { "chain": { "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$", "maxLength": 64, "description": "Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)" }, "address": { "type": "string", "pattern": "^0x[a-fA-F0-9]{40}$", "description": "Contract or account address" } }, "additionalProperties": false }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id5a2dbc75d7f7cecc.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5a2dbc75d7f7cecc/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5a2dbc75d7f7cecc?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.