Skip to main content
Glama

Arbitrum MCP Server

batch_posting_status

Track batch posting activity to monitor sequencer inbox updates and backlog size. Essential for chain data availability insights on Arbitrum networks using RPC URLs and contract addresses.

Instructions

Monitor batch posting activity. Tracks when batches were last posted to the sequencer inbox and current backlog size. Essential for PM and support teams to understand chain data availability status.

Input Schema

NameRequiredDescriptionDefault
bridgeAddressYesBridge contract address
chainNameNoChain name (e.g., 'Xai', 'Arbitrum One') - will auto-resolve to RPC URL
parentRpcUrlYesParent chain RPC URL (e.g., Ethereum mainnet RPC)
rpcUrlNoThe RPC URL of the Arbitrum chain (optional if default is set)
sequencerInboxAddressYesSequencer inbox contract address

Input Schema (JSON Schema)

{ "properties": { "bridgeAddress": { "description": "Bridge contract address", "type": "string" }, "chainName": { "description": "Chain name (e.g., 'Xai', 'Arbitrum One') - will auto-resolve to RPC URL", "type": "string" }, "parentRpcUrl": { "description": "Parent chain RPC URL (e.g., Ethereum mainnet RPC)", "type": "string" }, "rpcUrl": { "description": "The RPC URL of the Arbitrum chain (optional if default is set)", "type": "string" }, "sequencerInboxAddress": { "description": "Sequencer inbox contract address", "type": "string" } }, "required": [ "parentRpcUrl", "sequencerInboxAddress", "bridgeAddress" ], "type": "object" }

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dewanshparashar/arbitrum-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server