transfer_eth

Transfer native tokens like ETH or MATIC to any address using a private key for signing. Specify recipient, amount, and network for seamless EVM-compatible blockchain interactions.

Instructions

Transfer native tokens (ETH, MATIC, etc.) to an address

Input Schema

Name	Required	Description
`amount`	Yes	Amount to send in ETH (or the native token of the network), as a string (e.g., '0.1')
`network`	No	Network name (e.g., 'ethereum', 'optimism', 'arbitrum', 'base', etc.) or chain ID. Supports all EVM-compatible networks. Defaults to Ethereum mainnet.
`privateKey`	Yes	Private key of the sender account in hex format (with or without 0x prefix). SECURITY: This is used only for transaction signing and is not stored.
`to`	Yes	The recipient address or ENS name (e.g., '0x1234...' or 'vitalik.eth')

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "amount": {
      "description": "Amount to send in ETH (or the native token of the network), as a string (e.g., '0.1')",
      "type": "string"
    },
    "network": {
      "description": "Network name (e.g., 'ethereum', 'optimism', 'arbitrum', 'base', etc.) or chain ID. Supports all EVM-compatible networks. Defaults to Ethereum mainnet.",
      "type": "string"
    },
    "privateKey": {
      "description": "Private key of the sender account in hex format (with or without 0x prefix). SECURITY: This is used only for transaction signing and is not stored.",
      "type": "string"
    },
    "to": {
      "description": "The recipient address or ENS name (e.g., '0x1234...' or 'vitalik.eth')",
      "type": "string"
    }
  },
  "required": [
    "privateKey",
    "to",
    "amount"
  ],
  "type": "object"
}

EVM MCP Server

transfer_eth

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from EVM MCP Server

Related Tools

MCP directory API