bnbchain-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port number | 3001 |
| LOG_LEVEL | No | Set logging level (DEBUG, INFO, WARN, ERROR) | |
| PRIVATE_KEY | No | Your wallet private key (required for transaction operations) |
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
| Name | Description |
|---|---|
| get_block_by_hashC | Get a block by hash |
| get_block_by_numberC | Get a block by number |
| get_latest_blockC | Get the latest block |
| is_contractB | Check if an address is a smart contract or an externally owned account (EOA) |
| read_contractA | Read data from a smart contract by calling a view/pure function |
| write_contractC | Write data to a smart contract by calling a state-changing function |
| get_chain_infoC | Get chain information for a specific network |
| get_supported_networksB | Get list of supported networks |
| resolve_ensB | Resolve an ENS name to an EVM address (not supported on BSC) |
| get_erc20_token_infoC | Get ERC20 token information |
| get_native_balanceC | Get native token balance for an address |
| get_erc20_balanceC | Get ERC20 token balance for an address |
| get_transactionB | Get detailed information about a specific transaction by its hash. Includes sender, recipient, value, data, and more. |
| get_transaction_receiptC | Get a transaction receipt by its hash |
| estimate_gasC | Estimate the gas cost for a transaction |
| transfer_native_tokenC | Transfer native tokens (BNB, ETH, MATIC, etc.) to an address |
| approve_token_spendingA | Approve another address (like a DeFi protocol or exchange) to spend your ERC20 tokens. This is often required before interacting with DeFi protocols. |
| transfer_nftA | Transfer an NFT (ERC721 token) from one address to another. Requires the private key of the current owner for signing the transaction. |
| transfer_erc1155C | Transfer ERC1155 tokens to another address. ERC1155 is a multi-token standard that can represent both fungible and non-fungible tokens in a single contract. |
| transfer_erc20C | Transfer ERC20 tokens to an address |
| get_address_from_private_keyB | Get the EVM address derived from a private key |
| get_nft_infoA | Get detailed information about a specific NFT (ERC721 token), including collection name, symbol, token URI, and current owner if available. |
| check_nft_ownershipB | Check if an address owns a specific NFT |
| get_erc1155_token_uriA | Get the metadata URI for an ERC1155 token (multi-token standard used for both fungible and non-fungible tokens). The URI typically points to JSON metadata about the token. |
| get_nft_balanceA | Get the total number of NFTs owned by an address from a specific collection. This returns the count of NFTs, not individual token IDs. |
| get_erc1155_balanceB | Get the balance of a specific ERC1155 token ID owned by an address. ERC1155 allows multiple tokens of the same ID, so the balance can be greater than 1. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_block | Analyze a block and provide detailed information about its contents |
| interact_with_contract | Get guidance on interacting with a smart contract |
| explain_evm_concept | Get an explanation of an EVM concept |
| compare_networks | Compare different EVM-compatible networks |
| analyze_token | Analyze an ERC20 or NFT token |
| analyze_transaction | Analyze a specific transaction |
| analyze_address | Analyze an EVM address |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Most tools have distinct purposes targeting specific blockchain operations like balance checks, transfers, contract interactions, and network queries. Some overlap exists between get_erc20_balance/get_erc20_token_info and get_nft_balance/get_nft_info, but descriptions clarify their differences. No tools appear to do exactly the same thing.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case exclusively. The naming convention is predictable with clear action-object pairs like get_balance, transfer_token, read_contract, making the tool set easy to navigate and understand.
With 26 tools, the count feels heavy for a blockchain interaction server, though not extreme. The tools cover many specific operations, but some could potentially be consolidated or parameterized. The number is borderline high but still manageable given the comprehensive scope.
The tool set provides excellent coverage for blockchain operations including token transfers (native, ERC20, ERC1155, NFT), balance queries, contract interactions (read/write), network information, transaction details, and utility functions. All major blockchain interaction patterns are represented with no obvious gaps for the domain.