# Ankr Agent RPC (remote · mcp.ankr.com)

Read chain data on 200+ networks and Sui: transactions, logs, balances, objects, ABI-decoded.

- Trust score: not yet scored
- Registry status: active
- Liveness: live
- Owner verified: no

## Components

- remote · `mcp.ankr.com`: not yet scored (this document), [markdown](https://verifymcp.io/servers/w3tech-agent-rpc-mcp/mcp.md), [page](https://verifymcp.io/servers/w3tech-agent-rpc-mcp/mcp)
- npm · `@w3tech.io/agent-rpc-mcp`: not yet scored, [markdown](https://verifymcp.io/servers/w3tech-agent-rpc-mcp/w3tech-io-agent-rpc-mcp.md), [page](https://verifymcp.io/servers/w3tech-agent-rpc-mcp/w3tech-io-agent-rpc-mcp)

## Channel facts

- Endpoint: `https://mcp.ankr.com/rpc`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.4`

## Trust breakdown

No category breakdown is available for this channel yet.

## Install

### How do I install the Ankr Agent RPC MCP server?

Ankr Agent RPC is a hosted endpoint at https://mcp.ankr.com/rpc, 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.

### Claude

```bash
claude mcp add --transport http w3tech-agent-rpc-mcp 'https://mcp.ankr.com/rpc'
```

### Cursor

```json
{
  "mcpServers": {
    "w3tech-agent-rpc-mcp": {
      "url": "https://mcp.ankr.com/rpc"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "w3tech-agent-rpc-mcp": {
      "type": "http",
      "url": "https://mcp.ankr.com/rpc"
    }
  }
}
```

### Codex

```toml
[mcp_servers.w3tech-agent-rpc-mcp]
url = "https://mcp.ankr.com/rpc"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "w3tech-agent-rpc-mcp": {
      "type": "remote",
      "url": "https://mcp.ankr.com/rpc",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add w3tech-agent-rpc-mcp --url 'https://mcp.ankr.com/rpc' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  w3tech-agent-rpc-mcp:
    url: "https://mcp.ankr.com/rpc"
```

### Netclaw

```json
{
  "McpServers": {
    "w3tech-agent-rpc-mcp": {
      "Transport": "http",
      "Url": "https://mcp.ankr.com/rpc"
    }
  }
}
```

### Vellum

```bash
assistant mcp add w3tech-agent-rpc-mcp -t streamable-http -u 'https://mcp.ankr.com/rpc'
```

### Other

```json
{
  "mcpServers": {
    "w3tech-agent-rpc-mcp": {
      "type": "http",
      "url": "https://mcp.ankr.com/rpc"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

We have not recorded any changes for this component yet.

## MCP tools (25)

### `getAccountBalance` (~339 tokens)

Account balance by chain

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.

Input parameters:

- `address` (string, required)
- `blockchains` (array): The blockchains to get the balance for.  If not provided, the balance will be fetched for all blockchains.  Specify only if you want to get the balance for a specific blockchain.
- `maxTokens` (integer): Max assets to list, sorted by USD value descending (default 20, max 100).
- `minUsd` (number): Only list assets worth at least this many USD; the rest are summarised as dust.

### `getTokenPrice` (~168 tokens)

Token price

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.

Input parameters:

- `blockchain` (string): DEPRECATED alias for `chain`. Use `chain`.
- `chain` (string): Chain slug, e.g. eth, bsc, polygon.
- `contractAddress` (string): Contract address of the token. Leave empty for native coin.

### `getTransaction` (~261 tokens)

Transaction by hash

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.

Input parameters:

- `chain` (string, required): Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)
- `include` (string): Which parts to fetch. "all" (default) returns both the transaction and the receipt; "transaction" returns only eth_getTransactionByHash; "receipt" returns only eth_getTransactionReceipt.
- `txHash` (string, required): Transaction hash (0x + 64 hex) or Sui digest

### `getLogs` (~446 tokens)

Event logs

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.

Input parameters:

- `address` (string): Emitting contract; Sui: package[::module]
- `chain` (string, required): Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)
- `eventType` (string): Sui: Move event type 0xpkg::module::Name
- `fromBlock`: From block: decimal, 0x-hex, or tag (default latest)
- `maxLogs` (integer): Max logs to DISPLAY (default 50, max 1000). The scan stops once this is filled, so it also bounds how much is fetched upstream.
- `sender` (string): Sui: the emitting transaction's sender, 0x + 64 hex
- `toBlock`: To block: decimal, 0x-hex, or tag (default latest)
- `topics` (array): Topic filters (0x + 64 hex, or null to wildcard); topics[0] is the event signature hash. Max 4 slots.

### `getBlock` (~210 tokens)

Block by number or tag

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 can exceed the compression budget, so check tier_degraded before reading decimal header fields or decoded transactions.
Sui: `block` is a checkpoint number or digest.

Input parameters:

- `block` (required): 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` (string, required): Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)
- `includeTxs` (boolean): Include full (decoded) transactions instead of just hashes (default false)

### `getBalances` (~404 tokens)

Wallet balances, native and tokens

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.

Input parameters:

- `address` (string, required): Address (0x...) or ENS name
- `chain` (string, required): Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)
- `includeTokens` (boolean): Include ERC-20 token balances via AAPI (default true)
- `maxTokens` (integer): 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.
- `minUsd` (number): Only list tokens worth at least this many USD; everything below is bucketed into `dust`. Defaults to excluding only exactly-zero-value tokens.

### `getWalletActivity` (~298 tokens)

Wallet transaction activity

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.

Input parameters:

- `address` (string, required): Wallet address (0x...) or ENS name
- `chain` (string, required): Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)
- `pageSize` (integer): Items per page (default 25, max 100)

### `resolveContract` (~128 tokens)

Identify a contract

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.

Input parameters:

- `address` (string, required): Contract or account address
- `chain` (string, required): Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)

### `searchChain` (~255 tokens)

Search a chain

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.

Input parameters:

- `chain` (string): Chain (default eth)
- `query` (string, required): 0x tx/block hash, 0x address, or block number. ENS names are NOT resolved: they come back as kind:"ens" with a note.

### `expandResult` (~112 tokens)

Expand a truncated result

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.

Input parameters:

- `cursor` (string, required): The opaque cursor string from a previous tool result

### `rpcCall` (~598 tokens)

Raw JSON-RPC call, reads only

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 y…

Input parameters:

- `chain` (string, required): Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)
- `method` (string, required): JSON-RPC method, e.g. eth_call, eth_estimateGas, Filecoin.ChainHead
- `params` (array): Positional JSON-RPC params (default [])
- `tier` (number): Requested TORPC tier (default 2)

### `suiGetObjects` (~155 tokens)

Sui objects by id

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.

Input parameters:

- `ids` (array, required): Object ids to read, 50 at most. Order is preserved and a failure keeps its position.
- `version` (string): Read this past version instead of the live object. A decimal string, because an object version is a u64. Single id only.

### `suiListOwnedObjects` (~169 tokens)

Objects owned by a Sui address

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.

Input parameters:

- `owner` (string, required): The owning address.
- `pageSize` (integer): How many objects to return (default 50, max 200). The tail is reachable through the returned cursor.
- `type` (string): Move type filter, with or without its type parameters. Omit to list every owned object.

### `suiListDynamicFields` (~166 tokens)

Dynamic fields of a Sui object

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.

Input parameters:

- `pageSize` (integer): How many fields to return (default 50, max 200). The tail is reachable through the returned cursor.
- `parent` (string, required): The id of the object whose dynamic fields are listed.

### `suiGetPackage` (~209 tokens)

Move modules in a Sui package

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.

Input parameters:

- `maxModules` (integer): Rows the index lists before it truncates (default 50). Ignored when `module` is given.
- `module` (string)
- `package` (string, required)

### `suiGetFunction` (~120 tokens)

Move function signature

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.
Complete and never capped. A single signature is a small response, so nothing here truncates and nothing here pages.
Take the package and module names from suiGetPackage. A name the package does not declare is refused by the node rather than approximated.

Input parameters:

- `function` (string, required)
- `module` (string, required)
- `package` (string, required)

### `suiResolveName` (~185 tokens)

SuiNS name and address

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.

Input parameters:

- `address` (string)
- `name` (string)

### `suiSimulateTransaction` (~164 tokens)

Simulate a Sui transaction

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.

Input parameters:

- `transactionBytes` (string, required): The transaction to simulate: a base64 BCS TransactionData.

### `suiWatchEvents` (~264 tokens)

Watch Sui Move events

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.

Input parameters:

- `address` (string): Emitting Move code: package, or package::module
- `eventType` (string): Move event type 0xpkg::module::Name
- `maxLogs` (integer): Max events to DISPLAY per poll (default 50, max 1000).
- `sender` (string): The emitting transaction's sender, 0x + 64 hex

### `getNFTs` (~110 tokens)

NFTs held by an address

NFTs owned by an address on a chain, via the Ankr Advanced API indexer: collection, name, token id, contract, standard (ERC721/1155), image. Paged via pageToken.

Input parameters:

- `address` (string, required): Owner wallet address (0x...) or ENS name
- `chain` (string, required)
- `pageSize` (integer): Items per page (default 20, max 50)
- `pageToken` (string): Continuation token from a previous call

### `getTokenHolders` (~102 tokens)

Holders of a token

Holders of an ERC-20 token contract on a chain, via the Ankr Advanced API indexer: holder address with balance, total holder count, token decimals. Paged via pageToken.

Input parameters:

- `chain` (string, required)
- `contractAddress` (string, required): ERC-20 token contract address
- `pageSize` (integer): Holders per page (default 20)
- `pageToken` (string): Continuation token from a previous call

### `getTokenPriceHistory` (~221 tokens)

Token price history

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.

Input parameters:

- `chain` (string, required)
- `contractAddress` (string, required): ERC-20 token contract address
- `fromTimestamp` (integer): Start UNIX timestamp (seconds)
- `interval` (integer): Interval between quotes, in seconds
- `limit` (integer): Max quotes (default 100)
- `toTimestamp` (integer): End UNIX timestamp (seconds)

### `getInteractions` (~65 tokens)

Chains an address has used

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.

Input parameters:

- `address` (string, required): Address (0x...) or ENS name

### `listChains` (~212 tokens)

List supported chains

Discover chain support. Returns the chains where the Ankr Advanced API indexer is available (token balances, NFTs, holders, transfers, prices). IMPORTANT: the raw-RPC tools (getTransaction, getLogs, getBlock) and rpcCall are NOT limited to this list — they reach ANY chain Ankr serves (200+ EVM mainnets/testnets plus non-EVM like solana, btc, xrp, ton, near, aptos, and cosmos chains); just pass the chain slug as it appears in rpc.ankr.com/<chain>. suiChains are served over gRPC rather than by the proxy and have their own sui* tools. TORPC tier-2 compression is applied by the proxy on supported EVM chains, and other proxy chains pass through unchanged; suiChains are shaped in this server instead, so a Sui reply can be tier 1 or 2 with no proxy involved — check _meta.tier and _meta.tier_source for what was applied and by whom.

### `describeMethods` (~226 tokens)

Describe JSON-RPC method shapes and availability

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.

Input parameters:

- `chain` (string, required): Chain slug as in rpc.ankr.com/<chain> — any chain Ankr serves (see listChains)
- `methods` (array): Methods to describe (max 12); omit for the whole catalogue
- `probe` (boolean): Ask the node whether each method is served (needs methods)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/w3tech-agent-rpc-mcp/mcp#diagnostics

## Common questions

### What is the Ankr Agent RPC MCP server?

Ankr Agent RPC is an MCP server listed in the public MCP registry as io.github.w3tech/agent-rpc-mcp. Read chain data on 200+ networks and Sui: transactions, logs, balances, objects, ABI-decoded. This page covers its hosted endpoint (https://mcp.ankr.com/rpc).

### What tools does the Ankr Agent RPC MCP server expose?

Ankr Agent RPC exposes 25 tools: getAccountBalance, getTokenPrice, getTransaction, getLogs, getBlock, and 20 more. Their descriptions and schemas cost roughly 5,587 tokens of context every time the server is loaded.

### Does the Ankr Agent RPC MCP server require authentication?

No. We connected to Ankr Agent RPC without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

## Links

- Remote endpoint: https://mcp.ankr.com/rpc
- Repository: https://github.com/w3tech/agent-rpc-mcp-public
- Website: https://www.ankr.com/web3-api/agent-rpc/
- Changelog RSS feed: https://verifymcp.io/servers/w3tech-agent-rpc-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/w3tech-agent-rpc-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/w3tech-agent-rpc-mcp/mcp