Skip to main content
Glama

getContractCode

Retrieve smart contract bytecode from Ethereum networks by providing a contract address and optional network details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe contract's address
providerNoOptional. Either a network name or custom RPC URL. Use getAllNetworks to see available networks and their details, or getNetwork to get info about a specific network. You can use any network name returned by these tools as a provider value.
chainIdNoOptional. The chain ID to use. If provided with a named network and they don't match, the RPC's chain ID will be used.

Implementation Reference

  • Registration of the 'getContractCode' MCP tool, including schema and handler function.
    server.tool(
      "getContractCode",
      {
        address: z.string().describe(
          "The contract's address"
        ),
        provider: z.string().optional().describe(PROVIDER_DESCRIPTION),
        chainId: z.number().optional().describe(
          "Optional. The chain ID to use. If provided with a named network and they don't match, the RPC's chain ID will be used."
        )
      },
      async ({ address, provider, chainId }) => {
        try {
          const code = await ethersService.getContractCode(address, provider, chainId);
          
          return {
            content: [{ 
              type: "text", 
              text: code
            }]
          };
        } catch (error) {
          return {
            isError: true,
            content: [{ 
              type: "text", 
              text: `Error getting contract code: ${error instanceof Error ? error.message : String(error)}`
            }]
          };
        }
      }
    );
  • The main handler function for the getContractCode tool. It retrieves the contract bytecode using ethersService.getContractCode and returns it as text content, handling errors appropriately.
    async ({ address, provider, chainId }) => {
      try {
        const code = await ethersService.getContractCode(address, provider, chainId);
        
        return {
          content: [{ 
            type: "text", 
            text: code
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{ 
            type: "text", 
            text: `Error getting contract code: ${error instanceof Error ? error.message : String(error)}`
          }]
        };
      }
    }
  • Input schema using Zod for validating address (required string), provider (optional string), and chainId (optional number).
      address: z.string().describe(
        "The contract's address"
      ),
      provider: z.string().optional().describe(PROVIDER_DESCRIPTION),
      chainId: z.number().optional().describe(
        "Optional. The chain ID to use. If provided with a named network and they don't match, the RPC's chain ID will be used."
      )
    },
  • Top-level registration function that calls registerCoreTools (which registers getContractCode) among other tool sets.
    export function registerAllTools(server: McpServer, ethersService: any) {
      // Register tool categories
      registerCoreTools(server, ethersService);
      registerERC20Tools(server, ethersService);
      registerERC721Tools(server, ethersService);
      registerERC1155Tools(server, ethersService);
      registerNetworkTools(server);
      registerPromptTools(server);
      
      silentLogger.info("All tools registered successfully");
    } 

Latest Blog Posts

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/crazyrabbitLTC/mcp-ethers-server'

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