NEAR Wallet MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEAR_NETWORK | Yes | NEAR network (mainnet or testnet) | |
| NEAR_NODE_URL | No | Optional custom node URL, auto-detected from network if not set |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_balanceA | Get the NEAR balance of an account including available, staked, and storage-locked amounts |
| get_account_infoB | Get detailed account information including code hash, storage usage, and block height |
| get_transaction_statusC | Get the status and details of a NEAR transaction by its hash |
| get_access_keysA | List all access keys for an account (both full access and function call keys) |
| view_contract_methodB | Call a view (read-only) method on a NEAR smart contract. No gas required. |
| get_block_infoB | Get information about a specific block or the latest block |
| get_validatorsB | Get current validator set with stake amounts and status |
| get_gas_priceA | Get the current gas price on NEAR network |
| get_protocol_configB | Get NEAR protocol configuration including runtime and economics parameters |
| get_ft_balanceB | Get fungible token (FT/NEP-141) balance for an account on a specific token contract |
| get_ft_metadataB | Get metadata for a fungible token (name, symbol, decimals, icon) |
| get_staking_infoB | Get staking pool information and staked balance for an account |
| near_explorer_urlB | Generate NEAR Explorer URL for an account, transaction, or block |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| NEAR Network Info | Current NEAR testnet network information |
TDQS
Scored across 13 tools
Most tools target clearly distinct resources: account balance vs. FT balance vs. staking info, transaction status, access keys, contract view, block info, and validators. A few boundaries are slightly blurry, such as get_account_balance versus get_staking_info and get_account_info, since staked balance appears in multiple places.
The set is mostly consistent snake_case with a get_verb_noun pattern across 11 of 13 tools. Minor deviations are view_contract_method and near_explorer_url, which use different verb/noun conventions but remain readable and purposeful.
13 tools is well within the appropriate range and each tool appears to serve a distinct query need for NEAR account, token, staking, block, and network data. The server is not bloated, and no obvious redundant wrapper tools are present.
The read/query surface is broad, covering accounts, tokens, staking, blocks, validators, gas, protocol config, and explorer links. However, a wallet-oriented server lacks any write operations such as send/transfer, stake/unstake, access-key management, or transaction signing, which are notable gaps for a wallet domain.