Best for
- Developers building AI agents that need on-chain data
- Smart contract auditing and data analysis
- Building DeFi dashboards or monitoring tools
B
Bankless Onchain MCP Server
Community
MCP server for blockchain data interactions via the Bankless API.
GitHub source repository ↗
35FMRS · D
The project is no longer receiving updates but core functionality remains usable. Suitable for developers needing quick access to on-chain data, but note its read-only nature and reliance on an external API.
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. It supports contract operations (read state, get proxy, ABI, source), event operations (get logs, build topic), and transaction operations (history and details).
Tools
read_contract
Read state from smart contracts on various blockchain networks.
get_proxy
Retrieve the implementation contract address for a proxy contract.
get_abi
Fetch the ABI (Application Binary Interface) for a contract.
get_source
Retrieve the source code, ABI, compiler version, and other metadata for a verified contract.
get_events
Fetch event logs for a contract based on topics.
build_event_topic
Generate an event topic signature from event name and argument types.
get_transaction_history
Retrieve transaction history for a user address.
get_transaction_info
Get detailed information about a specific transaction.
Setup
- Set the BANKLESS_API_TOKEN environment variable. See https://docs.bankless.com/bankless-api/other-services/onchain-mcp for details.
- Run the server with
npx @bankless/onchain-mcp. - Configure the server in an MCP-compatible client as shown in install_config.
claude_desktop_config.json
{
"mcpServers": {
"bankless": {
"command": "npx",
"args": [
"@bankless/onchain-mcp"
],
"env": {
"BANKLESS_API_TOKEN": "your_api_token_here"
}
}
}
}
Fit and risk
Not for
- Writing to or modifying blockchain state (read-only)
- Scenarios requiring private chains or custom RPCs
- Real-time transaction streaming (requires additional components)
Required permissions
- Requires BANKLESS_API_TOKEN environment variable
- Requires network access to call the Bankless API
- Requires permission to read contract and transaction data
Risks and side effects
- Using a third-party API may have availability and rate limit constraints
- Careful when supplying contract addresses or method names to avoid security issues
- API key leak could lead to costs or data misuse
Troubleshooting
- Check that BANKLESS_API_TOKEN is set correctly
- Ensure network connectivity to the Bankless API
- Verify contract address and network parameters are correct
Use cases
Reading Ethereum smart contract state in AI applications
Analyzing token transfers and event logs
Tracking transaction history for an address
Debugging contract interactions
Supported clients
Claude DesktopFull support