MCP Server

Native MCP server integration for AI-powered blockchain interactions

The 256 Blocks MCP (Model Context Protocol) server enables AI agents to interact with blockchain networks directly. All MCP tool calls are converted to standard RPC requests and evaluated against your existing policies.

How It Works

  1. AI agent calls an MCP tool (e.g., eth_getBalance)
  2. The request is reformatted as a standard RPC request
  3. Your policies are evaluated: Platform → Organization → API Key
  4. If allowed, the request is executed and results returned

This means any policies you've configured for RPC access also apply to MCP tool calls—no additional configuration required.


Supported Chains

See Blockchain Support for the full list of supported networks.


Available Tools

eth_blockNumber

Get the current block number.

ParameterTypeRequiredDefault
chainstringYes-

eth_call

Execute a read-only contract call.

ParameterTypeRequiredDefault
chainstringYes-
tostringYes-
datastringYes-
blockstringNolatest
fromstringNo-
gasstringNo-
gasPricestringNo-
valuestringNo-

eth_chainId

Get the chain ID.

ParameterTypeRequiredDefault
chainstringYes-

eth_gasPrice

Get the current gas price.

ParameterTypeRequiredDefault
chainstringYes-

eth_getBalance

Get the native token balance of an address.

ParameterTypeRequiredDefault
chainstringYes-
addressstringYes-
blockstringNolatest

eth_getBlockByHash

Get block information by block hash.

ParameterTypeRequiredDefault
chainstringYes-
block_hashstringYes-
full_transactionsbooleanNofalse

eth_getBlockByNumber

Get block information by block number.

ParameterTypeRequiredDefault
chainstringYes-
block_numberstringYes-
full_transactionsbooleanNofalse

eth_getCode

Get the bytecode of a contract.

ParameterTypeRequiredDefault
chainstringYes-
addressstringYes-
blockstringNolatest

eth_getLogs

Query event logs for a specific block. Only single-block queries are supported.

ParameterTypeRequiredDefault
chainstringYes-
block_hashstringOne of these-
block_numberstringOne of these-
addressstringNo-
topicsarrayNo-

Block specification:

  • block_hash and block_number are mutually exclusive—use one or the other
  • block_number accepts hex format (0x100) or tags (latest, finalized, safe, pending, earliest)

eth_getStorageAt

Read contract storage at a specific slot.

ParameterTypeRequiredDefault
chainstringYes-
addressstringYes-
positionstringYes-
blockstringNolatest

eth_getTransactionByHash

Get transaction details by hash.

ParameterTypeRequiredDefault
chainstringYes-
tx_hashstringYes-

eth_getTransactionCount

Get the transaction count (nonce) for an address.

ParameterTypeRequiredDefault
chainstringYes-
addressstringYes-
blockstringNolatest

eth_getTransactionReceipt

Get transaction receipt by hash.

ParameterTypeRequiredDefault
chainstringYes-
tx_hashstringYes-
MCP Server | 256 Blocks