Ethereum Toolkit

Provides read-only Ethereum JSON-RPC access for Mainnet and Sepolia to fetch live blockchain data for AI agents.
  • javascript

0

GitHub Stars

javascript

Language

2 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

This MCP server provides read-only access to a subset of Ethereum JSON-RPC services for Mainnet and Sepolia, enabling real-time blockchain information retrieval for LLMs, AI agents, and automated workflows without exposing write operations.

How to use

You connect your MCP-enabled client to the Ethereum Toolkit MCP server to query read-only Ethereum data. Once connected, you can ask for current prices, gas costs, account balances, and recent transactions on both the mainnet and Sepolia testnet. Use your API key to authenticate, and let your client translate natural-language prompts into precise reads from the Ethereum network. The toolkit handles the data retrieval and returns structured results that you can present in a natural language format.

Typical usage patterns include: retrieving the latest Ethereum price in USD on both networks, checking the current gas price, getting an account balance, and listing transactions from the latest block. These capabilities are designed to empower your AI agents to answer prompts that require up-to-date blockchain information, while preserving read-only access for safety and reliability.

How to install

Prerequisites: you only need an MCP client and a valid API key from the Teckel service. No server installation is required on your side since the Ethereum Toolkit MCP server is accessed remotely.

  1. Install your MCP client of choice (for example Cursor or n8n) according to its standard procedures.

  2. Prepare your API key in the Teckel app. Copy or securely store the API key as you will use it to authenticate requests.

  3. Configure your MCP client with one or more server entries shown below. Use your actual API key in place of the placeholders.

Additional notes

Security and access: all calls require a Bearer token in the Authorization header. Protect your API key and rotate it if you suspect compromise.

Rate limits apply per API key. If you exceed the limit, you may receive a 429 error. If a request fails due to a client error (4xx), a base call fee may be charged for that outer call. Server errors (5xx) incur no charge. Nested calls follow the outer-call charging rule.

If you need to replace your API key, use the API Key Manager in the Teckel App to generate a new key; the old key becomes disabled immediately.

HTTP MCP server configurations

The following HTTP MCP server entry is provided for authenticated access to the Ethereum Toolkit MCP endpoints.

{
  "mcpServers": {    
    "teckel-ethereum-toolkit": {
      "url": "https://mcp-servers.bh.tkllabs.io:9780/ethereum-mcp",
      "headers": {
        "Authorization": "Bearer d1e12345-c234-45a6-9b76-1234567891ff"
      }
    }   
  }
}
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational