Skip to main content
Connect your coding assistant to Tavchain’s public RPC through the community evm-rpc-mcp reader. It can inspect blockchain data without a wallet, private key or node installation.

Connect your agent

The examples below cover four clients. For another MCP-compatible application or agent framework, use Other clients to enter the connection settings manually. Install uv and make sure uvx is available to your client. The setup below requests Python 3.12 and pins the reader and MCP SDK to compatible versions. uv may download Python and packages on first use.
Run this command in your terminal:
Run codex mcp list to check the configuration.
This launches a local stdio process when your client connects. It is not a hosted MCP URL. The client examples use the same reader configuration; Tavchain’s runtime acceptance covers Linux x64 with Python 3.12.
Keep the SDK pin. Reader version 0.1.0 uses the MCP SDK 1.x API and fails to start with SDK 2.x. The commands pin the reader and SDK; other dependencies are resolved by uv.

Check the connection

Ask your assistant:
Check the result against Network information. This reader does not enforce an expected chain ID automatically. Try these tasks next: Replace the transaction hash, public address or contract input in your request with the value you want to inspect.

What the reader can access

The reader exposes 13 tools for network identity, blocks, transactions, receipts, balances, nonces, code, storage, logs, gas price and contract calls. It has no signing or transaction-submission tool. Some tool descriptions use Ethereum’s term wei. On Tavchain, the base unit is atav: 1 TAV = 10^18 atav. Use an explicit block number when comparing several state queries. A missing receipt is not proof of success, and an error object must not be treated as data. Requests use the public RPC limits. Keep log ranges small and back off on HTTP 429. Your AI client and RPC provider receive the queries you send; keep secrets out of prompts and configuration.

Build your own agent

Any agent with an HTTP tool or an EVM library can query Tavchain’s Ethereum JSON-RPC endpoint directly. MCP is optional. Start by checking eth_chainId returns 0xbc3ba, then use the documented methods for balances, receipts and contract calls. If your agent framework has an MCP client, give it the same stdio command and arguments shown under Other clients. These connection settings do not grant wallet access or signing authority.

Troubleshooting

  • uvx not found: install uv and restart your editor so it picks up the updated PATH.
  • FastMCP import error: check that the setup includes --with mcp==1.30.0.
  • Wrong chain ID: stop using the results and check the configured RPC URL.
  • No result or RPC error: inspect the returned error and RPC troubleshooting.
Use Docs for AI alongside this reader when you want your assistant to consult Tavchain’s guides. The documentation connection searches pages; this connection reads live blockchain data. Upstream package · Ethereum JSON-RPC