Arbitrum

You can query Arbitrum networks using a dedicated MCP server that exposes natural language-like commands for monitoring chain health, batch posting, assertions, and gas prices across core and Orbit networks. This MCP server lets you interact with Arbitrum Nitro nodes and chains in an approachable, chat-like style while returning real-time data.

How to use

Use a compatible MCP client to connect to the Arbitrum MCP Server. The server provides commands you can invoke to check comprehensive chain status, monitor batch posting, track assertions, and observe gas prices across Arbitrum networks such as Arbitrum One, Arbitrum Nova, and Orbit chains. You can also query ArbOS versions and resolve contract addresses automatically from chain names. Most interactions are invoked through clearly named tools, each returning up-to-date results that help you troubleshoot and monitor health and performance.

How to install

Prerequisites: Install Docker to run the MCP server in a container. Optionally, you can run the MCP server directly with Node.js if you prefer a local build.

# Optional: run MCP server via Docker (recommended for maximum compatibility)
docker run -i --rm dewanshparashar/arbitrum-mcp

Configuration for clients

Configure your MCP client to connect to the Arbitrum MCP Server using a stdio command that runs the MCP container. This example shows how to register the server under a client configuration, using Docker to start the MCP server.

{
  "mcpServers": {
    "arbitrum_mcp": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "dewanshparashar/arbitrum-mcp"]
    }
  }
}

Useful commands you can run inside the MCP client

The MCP server exposes a set of tools you can call to get current chain health, batch status, gas prices, and more. Use the client to execute these tools and receive structured results in real time.

Examples you might use include querying comprehensive chain status, batch posting status, gas pricing, and ArbOS version across chains. The exact command names may look like comprehensive_chain_status, batch_posting_status, gas_status, and arbos_version.

Notes on networking and environments

If you run the MCP server in a container and connect from a different host, ensure network access and any required ports are open according to your deployment environment. When you are connecting to local test nodes from within containers, ensure you reference the correct RPC URL as needed by your setup.

Foundational concepts and capabilities

The server integrates with Arbitrum ecosystems to provide real-time visibility into health, batch flow, assertions, and costs. It supports core chains (Arbitrum One, Arbitrum Nova) and Orbit chains, and can resolve contract addresses automatically from chain names. It offers health checks, sync status, transaction tracing, debug and validation endpoints, maintenance operations, and time-optimized routes for faster access.

Examples of supported actions

Query examples you can adapt to your MCP client include: checking chain health and status across a chain, monitoring whether batches are being posted, tracking assertion events, and inspecting gas price levels.

Security and best practices

Limit access to the MCP server to trusted clients. Use network segmentation, strong authentication where possible, and keep the MCP server up to date with security patches. When running in Docker, prefer the official image and avoid exposing management interfaces beyond your trusted network.

Troubleshooting tips

If the MCP server does not respond, verify that the container is running and that your client is configured to reach it. Check network connectivity between the client and the MCP server and review any firewall rules that might block the connection.

Examples of available tools and actions you can call

comprehensive_chain_status — Get a complete health overview for a given chain batch_posting_status — Monitor sequencer batch delivery and backlog assertion_status — Track NodeCreated vs NodeConfirmed events gas_status — Monitor current gas prices and detect spikes arbos_version — Retrieve ArbOS version for any chain list_chains — Show all available Edges/Chains search_chains — Find chains by name or ID chain_info — Get detailed information about a chain node_health — Check node health status sync_status — Get synchronization status latest_block — Retrieve the latest block information get_balance — Check account balances get_balance_ether — Check Ether balance for an account get_transaction — Retrieve transaction details get_transaction_receipt — Get transaction receipts is_contract — Determine if an address is a contract "

Available tools

comprehensive_chain_status

Query the complete health overview for a specified Arbitrum chain.

batch_posting_status

Monitor batch posting activity, including delivery status and backlog.

assertion_status

Track NodeCreated versus NodeConfirmed events to verify progress.

gas_status

Retrieve current gas prices and detect price spikes.

arbos_version

Fetch the ArbOS version running on any given chain.

list_chains

Show all available Arbitrum chains that MCP can interact with.

search_chains

Find chains by name or ID to narrow down your monitoring scope.

chain_info

Get detailed information about a specific chain.

node_health

Check the health status of an Arbitrum node.

sync_status

Get the synchronization status for a node.

latest_block

Retrieve information about the latest block on a chain.

get_balance

Check the balance of an account in the native token.

get_balance_ether

Check the balance of an account in Ether (or equivalent unit across chains).

get_transaction

Obtain details for a specific transaction.

get_transaction_receipt

Retrieve the receipt for a given transaction.

is_contract

Determine whether a given address is a contract.