Arbitrum MCP Server

118

Overview InspectNew Endpoints Schema Related Servers Reviews Score

arbtrace_call

Trace individual Arbitrum network calls by specifying trace types, RPC URLs, and call arguments to analyze transaction details and state changes.

Instructions

Trace individual calls with specified trace types (requires trace API)

Input Schema

Name	Required	Description
`blockNumOrHash`	No	Block number or hash (defaults to 'latest')
`callArgs`	Yes	Call arguments (to, from, data, etc.)
`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)
`traceTypes`	No	Array of trace types (e.g., ['trace', 'stateDiff'])

Input Schema (JSON Schema)

{
  "properties": {
    "blockNumOrHash": {
      "description": "Block number or hash (defaults to 'latest')",
      "type": "string"
    },
    "callArgs": {
      "description": "Call arguments (to, from, data, etc.)",
      "type": "object"
    },
    "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"
    },
    "traceTypes": {
      "description": "Array of trace types (e.g., ['trace', 'stateDiff'])",
      "items": {
        "type": "string"
      },
      "type": "array"
    }
  },
  "required": [
    "callArgs"
  ],
  "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