Neo N3 MCP Server
Related Servers
Alternatives to Neo N3 MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that enables Claude and other AI assistants to interact with NEAR Protocol wallets and blockchain data.13MIT
- AlicenseNot 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.MIT
- FlicenseCqualityDmaintenanceAn MCP server that connects Claude to BrianKnows' blockchain knowledge base, allowing users to search for blockchain/DeFi information and interact with a specialized agent across multiple knowledge bases.3-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables token listing, trading, and interaction with the Kaia blockchain via Claude Desktop.1Apache 2.0
- AlicenseAqualityCmaintenanceMCP Server for the Notion API, enabling Claude to interact with Notion workspaces.311,700 npm924MIT
- AlicenseBqualityDmaintenanceAn MCP server that allows querying MON token balances and NFT counts on the Monad testnet, enabling Claude Desktop to interact with the Monad blockchain.2ISC
TDQS
Scored across 19 tools
Most tools target distinct resources, but get_balance and get_nep17_balances overlap since get_balance already includes NEP-17 balances. get_blockchain_info and get_network_mode also share active-network information, and get_contract_info vs get_contract_status could be confused without careful reading.
The naming is mostly consistent with clear get_* prefixes and snake_case verbs. Minor deviations exist with list_famous_contracts, wait_for_transaction, invoke_contract, and estimates, but they are still predictable and readable.
At 19 tools, the server sits in the heavier range and feels borderline for a focused toolkit. Each tool is individually reasonable, but the set could be tightened by consolidating overlapping query tools.
The server covers a solid range of read-only Neo N3 operations: balances, transfers, blocks, transactions, contracts, fees, and network info. However, there are notable gaps for a full blockchain MCP surface, such as sending transfers, claiming GAS, or performing signed contract invocations.