Eth Security MCP

🚀 ETH Security MCP

A collection of MCP servers for security analysts, auditors, and incident responders.

🚀 Quick Start

✨ Features

• Provide access to Dune API endpoints, returning structured transaction results.
• Offer access to Foundry's cast command - line tool, enabling interaction with Ethereum nodes and smart contracts.

📦 Installation

Dependencies

eth - security - mcp requires the following dependencies to be installed:

• node and npm
• just

Environment Variable Setup

The MCP servers in eth - security - mcp may use environment variables to pass information, such as API keys. .env.example lists the relevant values required to run all MCP servers. To set up the .env file, run cp .env.example .env and fill in the relevant information.

Workspace

This repository uses npm workspaces to separate each operation. To interact with a specific workspace, use npm <action> -w src/<directory - name>.

Building and Debugging

This repo uses justfile to automate building and debugging, using MCP Inspector. For example, to build and debug the dune MCP server, you can run the following commands:

$ just -l
Available recipes:
    build workspace
    debug workspace

$ just debug dune

Installing MCP Servers to Claude Desktop

To install the MCP servers from this repository into Claude Desktop:

1. Run just setup - <machine> <mcp - server>, where <machine> is either linux or macos, and <mcp - server> is the directory name containing the MCP server.
2. This just command will generate a file claude.config.tmp.json in the MCP server directory, which can be copied and pasted under mcpServers in the following files:
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • linux: ~/.config/Claude/claude_desktop_config.json
3. After adding the configuration information, restart Claude Desktop for the changes to take effect.

💻 Usage Examples

MCP Servers

Dune

The Dune MCP server provides access to Dune API endpoints, returning structured transaction results.

Available Tools

• get_transactions_by_address
  • Overview: Retrieve transactions for an address using Dune's Echo API.
  • Parameters:
    • address (required): The address for which to retrieve transactions.
    • chain_ids (optional): A comma - separated list of chain IDs to filter transactions.
    • method_id (optional): Filter transactions to return those with the provided method ID (function selector).
    • log_address (optional): Filter transactions to return those with the address in the logs.
    • topic0 (optional): Filter transactions to return those with the provided primary event topic.
    • min_block_number (optional): Filter transactions to return those starting from and after this block number.
    • limit (optional): Limit the number of transactions returned.
    • is_sender (optional): Return transactions where the sender is the provided address.
    • is_receiver (optional): Return transactions where the receiver is the provided address.
  • Return: Returns an array of transaction objects, each containing the following relevant information:
    • address: The address involved in the contract or account.
    • block_number: The block number containing the transaction.
    • data: Transaction data.
    • from: The sender address of the transaction.
    • gas_used: The amount of gas used.
    • to: The receiver address of the transaction (null if it's a contract creation).
    • value: The amount of ETH transferred in wei.
    • receipt: The transaction receipt, containing information such as gas usage and status.

Cast

The Cast MCP server provides access to Foundry's cast command - line tool, allowing interaction with Ethereum nodes and smart contracts.

Available Tools

• run_transaction
  • Overview: Simulate a transaction using Foundry's cast run command.
  • Parameters:
    • transactionHash (required): The transaction hash to simulate.
    • rpcUrl (required): The RPC URL of the Ethereum node for simulation.
    • quick (optional): Whether to use quick mode to speed up the simulation (default: false).
  • Return: Returns the simulation result as a string, including:
    • Transaction execution details.
    • State changes.
    • Gas usage.
    • Any revert reasons (if any).