Arbitrum MCP Server

118

Overview InspectNew Endpoints Schema Related Servers Reviews Score

arbtrace_callMany

Batch trace multiple calls on Arbitrum nodes using the trace API. Streamlines analysis by resolving chain names and handling block-specific queries efficiently.

Instructions

Trace multiple calls in batch for efficiency (requires trace API)

Input Schema

Name	Required	Description
`blockNumOrHash`	No	Block number or hash (defaults to 'latest')
`calls`	Yes	Array of call objects to trace
`chainName`	No	Chain name (e.g., 'Xai', 'Arbitrum One') - will auto-resolve to RPC URL
`rpcUrl`	No	The RPC URL of the Arbitrum node (optional if default is set)

Input Schema (JSON Schema)

{
  "properties": {
    "blockNumOrHash": {
      "description": "Block number or hash (defaults to 'latest')",
      "type": "string"
    },
    "calls": {
      "description": "Array of call objects to trace",
      "items": {
        "type": "object"
      },
      "type": "array"
    },
    "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"
    }
  },
  "required": [
    "calls"
  ],
  "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