NEAR Wallet MCP Server
Related Servers
Alternatives to NEAR Wallet MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude for Desktop with blockchain functionality, allowing users to check balances and send tokens on EVM and Solana chains through natural language interactions.-
- AlicenseAqualityDmaintenanceThe NEAR MCP Server enables AI agents to interact with the NEAR Protocol blockchain, providing smart contract interaction, transaction handling, and event listening with AI-driven processing.38 npm1ISC
- AlicenseBqualityAmaintenanceAn MCP server that provides seamless integration with the Neo N3 blockchain, allowing Claude to interact with blockchain data, manage wallets, transfer assets, and invoke smart contracts.194 npm4MIT
- -licenseNot gradedqualityNot gradedmaintenanceAn MCP server that allows Claude Desktop to query Monad testnet for MON token balances of accounts.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop and MCP clients to interact with NEAR blockchain accounts for balance checks, account info, access keys, transaction status, and sending signed transactions.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for ClawVault - an AI agent payment security layer that enables Claude to request payments, check limits, and manage transactions with configurable rules.52 npmMIT
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.