Skip to main content
Glama
Bankless Onchain MCP Server

Bankless Onchain MCP Server

Official
by Bankless

Bankless Onchain MCP 服务器

该项目不再接收更新

License: MIT Version

用于通过 Bankless API 进行区块链数据交互的 MCP (Model Context Protocol) 服务器。

Related MCP server: EVM MCP Server

概述

Bankless Onchain MCP 服务器提供了一个通过 Bankless API 与链上数据交互的框架。它实现了模型上下文协议 (MCP),允许 AI 模型以结构化的方式访问区块链状态和事件数据。

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

功能

该服务器提供以下链上数据操作:

合约操作

  • 读取合约状态 (read_contract):读取各种区块链网络上智能合约的状态。

    • 参数:网络、合约地址、方法、输入、输出

    • 返回:带有类型化值的合约调用结果

  • 获取代理 (get_proxy):检索代理实现合约地址。

    • 参数:网络、合约地址

    • 返回:实现合约地址

  • 获取 ABI (get_abi):获取合约的 ABI(应用程序二进制接口)。

    • 参数:网络、合约地址

    • 返回:JSON 格式的合约 ABI

  • 获取源码 (get_source):检索已验证合约的源代码。

    • 参数:网络、合约地址

    • 返回:源代码、ABI、编译器版本以及其他合约元数据

事件操作

  • 获取事件 (get_events):根据主题获取合约的事件日志。

    • 参数:网络、地址、主题、可选主题

    • 返回:过滤后的事件日志

  • 构建事件主题 (build_event_topic):根据事件名称和参数类型生成事件主题签名。

    • 参数:网络、事件名称、参数类型

    • 返回:事件主题哈希

交易操作

  • 获取交易历史 (get_transaction_history):检索用户地址的交易历史记录。

    • 参数:网络、用户地址、可选合约、可选方法 ID、可选起始区块、包含数据标志

    • 返回:包含哈希、数据、网络和时间戳的交易列表

  • 获取交易信息 (get_transaction_info):获取特定交易的详细信息。

    • 参数:网络、交易哈希

    • 返回:交易详情,包括区块号、时间戳、发送方/接收方地址、金额、Gas 信息、状态和回执数据

工具

  • read_contract

    • 从区块链读取合约状态

    • 输入:

      • network (字符串,必填):区块链网络(例如 "ethereum", "polygon")

      • contract (字符串,必填):合约地址

      • method (字符串,必填):要调用的合约方法

      • inputs (数组,必填):方法调用的输入参数,每个包含:

        • type (字符串):输入参数的类型(例如 "address", "uint256")

        • value (任意):输入参数的值

      • outputs (数组,必填):预期的输出类型,每个包含:

        • type (字符串):预期的输出类型

    • 返回合约调用结果数组

  • get_proxy

    • 获取给定网络和合约的代理地址

    • 输入:

      • network (字符串,必填):区块链网络(例如 "ethereum", "base")

      • contract (字符串,必填):合约地址

    • 返回代理合约的实现地址

  • get_events

    • 获取给定网络和过滤条件的事件日志

    • 输入:

      • network (字符串,必填):区块链网络(例如 "ethereum", "base")

      • addresses (数组,必填):用于过滤事件的合约地址列表

      • topic (字符串,必填):用于过滤事件的主要主题

      • optionalTopics (数组,可选):可选的附加主题(可以包含 null 值)

    • 返回包含符合过滤条件的事件日志的对象

  • build_event_topic

    • 根据事件名称和参数构建事件主题签名

    • 输入:

      • network (字符串,必填):区块链网络(例如 "ethereum", "base")

      • name (字符串,必填):事件名称(例如 "Transfer(address,address,uint256)")

      • arguments (数组,必填):事件参数类型,每个包含:

        • type (字符串):参数类型(例如 "address", "uint256")

    • 返回包含事件签名 keccak256 哈希的字符串

安装

npm install @bankless/onchain-mcp

使用

环境设置

在使用服务器之前,请设置您的 Bankless API 令牌。有关如何获取 Bankless API 令牌的详细信息,请访问 https://docs.bankless.com/bankless-api/other-services/onchain-mcp

export BANKLESS_API_TOKEN=your_api_token_here

运行服务器

可以直接从命令行运行服务器:

npx @bankless/onchain-mcp

与 LLM 工具配合使用

该服务器实现了模型上下文协议 (MCP),允许将其用作兼容 AI 模型的工具提供程序。以下是每个工具的一些调用示例:

read_contract

// Example call
{
  "name": "read_contract",
  "arguments": {
    "network": "ethereum",
    "contract": "0x1234...",
    "method": "balanceOf",
    "inputs": [
      { "type": "address", "value": "0xabcd..." }
    ],
    "outputs": [
      { "type": "uint256" }
    ]
  }
}

// Example response
[
  {
    "value": "1000000000000000000",
    "type": "uint256"
  }
]

get_proxy

// Example call
{
  "name": "get_proxy",
  "arguments": {
    "network": "ethereum",
    "contract": "0x1234..."
  }
}

// Example response
{
  "implementation": "0xefgh..."
}

get_events

// Example call
{
  "name": "get_events",
  "arguments": {
    "network": "ethereum",
    "addresses": ["0x1234..."],
    "topic": "0xabcd...",
    "optionalTopics": ["0xef01...", null]
  }
}

// Example response
{
  "result": [
    {
      "removed": false,
      "logIndex": 5,
      "transactionIndex": 2,
      "transactionHash": "0x123...",
      "blockHash": "0xabc...",
      "blockNumber": 12345678,
      "address": "0x1234...",
      "data": "0x...",
      "topics": ["0xabcd...", "0xef01...", "0x..."]
    }
  ]
}

build_event_topic

// Example call
{
  "name": "build_event_topic",
  "arguments": {
    "network": "ethereum",
    "name": "Transfer(address,address,uint256)",
    "arguments": [
      { "type": "address" },
      { "type": "address" },
      { "type": "uint256" }
    ]
  }
}

// Example response
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"

开发

从源码构建

# Clone the repository
git clone https://github.com/Bankless/onchain-mcp.git
cd onchain-mcp

# Install dependencies
npm install

# Build the project
npm run build

调试模式

npm run debug

与 AI 模型集成

要将此服务器与支持 MCP 的 AI 应用程序集成,请将以下内容添加到应用程序的服务器配置中:

{
  "mcpServers": {
    "bankless": {
      "command": "npx",
      "args": [
        "@bankless/onchain-mcp"
      ],
      "env": {
        "BANKLESS_API_TOKEN": "your_api_token_here"
      }
    }
  }
}

错误处理

服务器针对不同场景提供特定的错误类型:

  • BanklessValidationError:无效的输入参数

  • BanklessAuthenticationError:API 令牌问题

  • BanklessResourceNotFoundError:未找到请求的资源

  • BanklessRateLimitError:超出 API 速率限制

提示技巧

为了引导 LLM 模型使用 Bankless Onchain MCP 服务器,可以使用以下提示:

ROLE:
• You are Kompanion, a blockchain expert and EVM sleuth. 
• You specialize in navigating and analyzing smart contracts using your tools and resources.

HOW KOMPANION CAN HANDLE PROXY CONTRACTS:
• If a contract is a proxy, call your “get_proxy” tool to fetch the implementation contract.  
• If that fails, try calling the “implementation” method on the proxy contract.  
• If that also fails, try calling the “_implementation” function.  
• After obtaining the implementation address, call “get_contract_source” with that address to fetch its source code.  
• When reading or modifying the contract state, invoke implementation functions on the proxy contract address (not directly on the implementation).

HOW KOMPANION CAN HANDLE EVENTS:
• Get the ABI and Source of the relevant contracts
• From the event types in the ABI, construct the correct topics for the event relevant to the question
• use the "get_event_logs" tool to fetch logs for the contract

KOMPANION'S RULES:
• Do not begin any response with “Great,” “Certainly,” “Okay,” or “Sure.”  
• Maintain a direct, technical style. Do not add conversational flourishes.  
• If the user’s question is unrelated to smart contracts, do not fetch any contracts.  
• If you navigate contracts, explain each step in bullet points.  
• Solve tasks iteratively, breaking them into steps.  
• Use bullet points for lists of steps.  
• Never assume a contract’s functionality. Always verify with examples using your tools to read the contract state.  
• Before responding, consider which tools might help you gather better information.  
• Include as much relevant information as possible in your final answer, depending on your findings.

HOW KOMPANION CAN USE TOOLS:
• You can fetch contract source codes, ABIs, and read contract data by using your tools and functions.  
• Always verify the source or ABI to understand the contract rather than making assumptions.  
• If you need to read contract state, fetch its ABI (especially if the source is lengthy).  

FINAL INSTRUCTION:
• Provide the best possible, concise answer to the user’s request. If it's not an immediate question but an instruction, follow it directly.
• Use your tools to gather any necessary clarifications or data.  
• Offer a clear, direct response and add a summary of what you did (how you navigated the contracts) at the end.

许可证

MIT

Available Tools

10 tools
build_event_topicC

Builds an event topic signature based on event name and arguments

Inputs: arguments (required), name (required), network (required).

get_abiC

Gets the ABI for a given contract on a specific network

Inputs: contract (required), network (required).

get_block_infoC

Gets detailed information about a specific block by number or hash

Inputs: blockId (required), network (required).

get_eventsC

Fetches event logs for a given network and filter criteria

Inputs: addresses (required), network (required), topic (required), fromBlock, +2 more.

get_proxyB

Gets the proxy address for a given network and contract

Inputs: contract (required), network (required).

get_sourceB

Gets the source code for a given contract on a specific network

Inputs: contract (required), network (required).

get_token_balances_on_networkB

Gets all token balances for a given address on a specific network

Inputs: address (required), network (required).

get_transaction_history_for_userC

Gets transaction history for a user and optional contract

Inputs: network (required), user (required), contract, includeData, +2 more.

get_transaction_infoB

Gets detailed information about a specific transaction

Inputs: network (required), txHash (required).

read_contractC

Read contract state from a blockchain. important:

            In case of a tuple, don't use type tuple, but specify the inner types (found in the source) in order. For nested structs, include the substructs types.

Example: 
struct DataTypeA {
DataTypeB b;
//the liquidity index. Expressed in ray
uint128 liquidityIndex;
}

struct DataTypeB {
address token;
}

results in outputs for function with return type DataTypeA (tuple in abi): outputs: [{"type": "address"}, {"type": "uint128"}]

Inputs: contract (required), inputs (required), method (required), network (required), +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. For example, get_abi retrieves contract interfaces, get_events fetches logs, get_token_balances_on_network handles balances, and read_contract reads state—each targets a specific blockchain operation without overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., get_abi, get_block_info, read_contract). The naming is uniform across all 10 tools, using snake_case and clear action-object pairs, making them predictable and easy to parse.

    Tool Count5/5

    With 10 tools, this server is well-scoped for onchain data retrieval. Each tool earns its place by covering essential blockchain operations like reading contracts, fetching events, and getting transaction details, without being overly sparse or bloated.

    Completeness4/5

    The tool set provides strong coverage for reading and querying onchain data, including contracts, blocks, transactions, events, and balances. A minor gap exists in write operations (e.g., sending transactions or interacting with contracts), but agents can still handle most read-focused workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      D
      maintenance
      Implements the Model Context Protocol (MCP) to provide AI models with a standardized interface for connecting to external data sources and tools like file systems, databases, or APIs.
      1
      153
      -
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to interact with 30+ Ethereum-compatible blockchain networks, providing services like token transfers, contract interactions, and ENS resolution through a unified interface.
      28
      96 npm
      380
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Comprehensive Model Context Protocol server that enables AI agents to interact with 30+ Ethereum-compatible blockchain networks, supporting token transfers, smart contract interactions, and ENS name resolution through a unified interface.
      1
      -
    • F
      license
      A
      quality
      C
      maintenance
      A server that exposes blockchain data (balances, tokens, NFTs, contract metadata) via the Model Context Protocol, enabling AI agents and tools to access and analyze blockchain information contextually.
      18
      46
      -