Bankless Onchain MCP Server

npm install @bankless/onchain-mcp

export BANKLESS_API_TOKEN=your_api_token_here

npx @bankless/onchain-mcp

// 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"
 }
]

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

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

// 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..."]
 }
 ]
}

// 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

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

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.

Looking for Admin?