Skip to main content
Glama
Bankless

Bankless Onchain MCP Server

Official
by Bankless
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BANKLESS_API_TOKENYesYour Bankless API token. Obtain from https://docs.bankless.com/bankless-api/other-services/onchain-mcp

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
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"}]
get_proxyB

Gets the proxy address for a given network and contract

get_abiC

Gets the ABI for a given contract on a specific network

get_sourceB

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

get_eventsC

Fetches event logs for a given network and filter criteria

build_event_topicC

Builds an event topic signature based on event name and arguments

get_transaction_history_for_userC

Gets transaction history for a user and optional contract

get_transaction_infoB

Gets detailed information about a specific transaction

get_token_balances_on_networkB

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

get_block_infoC

Gets detailed information about a specific block by number or hash

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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
ResponsivenessUnresponsive

Resources