Bankless Onchain MCP Server

MCP (Model Context Protocol) server for blockchain data interaction through the Bankless API.

Overview

The Bankless Onchain MCP Server provides a framework for interacting with on-chain data via the Bankless API. It implements the Model Context Protocol (MCP) to allow AI models to access blockchain state and event data in a structured way.

https://github.com/user-attachments/assets/95732dff-ae5f-45a6-928a-1ae17c0ddf9d

Related MCP server: Flow MCP Server

Features

The server provides the following onchain data operations:

Contract Operations

• Read Contract State (read_contract): Read state from smart contracts on various blockchain networks.

  • Parameters: network, contract address, method, inputs, outputs

  • Returns: Contract call results with typed values

• Get Proxy (get_proxy): Retrieve proxy implementation contract addresses.

  • Parameters: network, contract address

  • Returns: Implementation contract address

• Get ABI (get_abi): Fetch the ABI (Application Binary Interface) for a contract.

  • Parameters: network, contract address

  • Returns: Contract ABI in JSON format

• Get Source (get_source): Retrieve the source code for a verified contract.

  • Parameters: network, contract address

  • Returns: Source code, ABI, compiler version, and other contract metadata

Event Operations

• Get Events (get_events): Fetch event logs for a contract based on topics.

  • Parameters: network, addresses, topic, optional topics

  • Returns: Filtered event logs

• Build Event Topic (build_event_topic): Generate an event topic signature from event name and argument types.

  • Parameters: network, event name, argument types

  • Returns: Event topic hash

Transaction Operations

• Get Transaction History (get_transaction_history): Retrieve transaction history for a user address.

  • Parameters: network, user address, optional contract, optional method ID, optional start block, include data flag

  • Returns: List of transactions with hash, data, network, and timestamp

• Get Transaction Info (get_transaction_info): Get detailed information about a specific transaction.

  • Parameters: network, transaction hash

  • Returns: Transaction details including block number, timestamp, from/to addresses, value, gas info, status, and receipt data

Tools

• read_contract

  • Read contract state from a blockchain

  • Input:

    • network (string, required): The blockchain network (e.g., "ethereum", "polygon")

    • contract (string, required): The contract address

    • method (string, required): The contract method to call

    • inputs (array, required): Input parameters for the method call, each containing:

      • type (string): The type of the input parameter (e.g., "address", "uint256")

      • value (any): The value of the input parameter

    • outputs (array, required): Expected output types, each containing:

      • type (string): The expected output type

  • Returns an array of contract call results

• get_proxy

  • Gets the proxy address for a given network and contract

  • Input:

    • network (string, required): The blockchain network (e.g., "ethereum", "base")

    • contract (string, required): The contract address

  • Returns the implementation address for the proxy contract

• get_events

  • Fetches event logs for a given network and filter criteria

  • Input:

    • network (string, required): The blockchain network (e.g., "ethereum", "base")

    • addresses (array, required): List of contract addresses to filter events

    • topic (string, required): Primary topic to filter events

    • optionalTopics (array, optional): Optional additional topics (can include null values)

  • Returns an object containing event logs matching the filter criteria

• build_event_topic

  • Builds an event topic signature based on event name and arguments

  • Input:

    • network (string, required): The blockchain network (e.g., "ethereum", "base")

    • name (string, required): Event name (e.g., "Transfer(address,address,uint256)")

    • arguments (array, required): Event arguments types, each containing:

      • type (string): The argument type (e.g., "address", "uint256")

  • Returns a string containing the keccak256 hash of the event signature

Installation

Usage

Environment Setup

Before using the server, set your Bankless API token. For details on how to obtain your Bankless API token, head to https://docs.bankless.com/bankless-api/other-services/onchain-mcp

Running the Server

The server can be run directly from the command line:

Usage with LLM Tools

This server implements the Model Context Protocol (MCP), which allows it to be used as a tool provider for compatible AI models. Here are some example calls for each tool:

read_contract

get_proxy

get_events

build_event_topic

Development

Building from Source

Debug Mode

Integration with AI Models

To integrate this server with AI applications that support MCP, add the following to your app's server configuration:

Error Handling

The server provides specific error types for different scenarios:

• BanklessValidationError: Invalid input parameters

• BanklessAuthenticationError: API token issues

• BanklessResourceNotFoundError: Requested resource not found

• BanklessRateLimitError: API rate limit exceeded

Prompting Tips

In order to guide an LLM model to use the Bankless Onchain MCP Server, the following prompts can be used:

License

MIT