Skip to main content
Glama

Arbitrum MCP Server

arbtrace_transaction

Retrieve detailed trace information for a specific transaction on Arbitrum networks using the trace API. Input transaction hash and optional RPC URL or chain name to analyze transaction execution steps and internal calls.

Instructions

Get trace information for a specific transaction (requires trace API)

Input Schema

NameRequiredDescriptionDefault
chainNameNoChain name (e.g., 'Xai', 'Arbitrum One') - will auto-resolve to RPC URL
rpcUrlNoThe RPC URL of the Arbitrum node (optional if default is set)
txHashYesTransaction hash to trace

Input Schema (JSON Schema)

{ "properties": { "chainName": { "description": "Chain name (e.g., 'Xai', 'Arbitrum One') - will auto-resolve to RPC URL", "type": "string" }, "rpcUrl": { "description": "The RPC URL of the Arbitrum node (optional if default is set)", "type": "string" }, "txHash": { "description": "Transaction hash to trace", "type": "string" } }, "required": [ "txHash" ], "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