VeChain AI Terminal MCP Server
Related Servers
Alternatives to VeChain AI Terminal MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables AI assistants to search VeChain documentation, query blockchain data (blocks, transactions, accounts), and interact with tokens, NFTs, and VeBetterDAO tools through the Model Context Protocol.7626 npm5MIT- AlicenseBqualityDmaintenanceProvides Claude with access to Ethereum and EVM-compatible blockchain operations, enabling wallet management, transaction handling, contract interactions, and blockchain queries through natural language.43541 npm10MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with the Stacks blockchain through Claude Desktop. Manage wallets, trade tokens on DEXs, stack STX for Bitcoin rewards, and track portfolio—all through natural conversation.30 npm6MIT
- AlicenseBqualityDmaintenanceEnables interaction with the VeChain blockchain network, providing access to documentation search, Thor REST API queries for accounts/transactions/blocks, and wallet management with cryptographic signing capabilities for both Mainnet and Testnet.205MIT

Adamik MCP Serverofficial
AlicenseAqualityDmaintenanceEnables read and write interactions with 60+ blockchain networks through Claude Desktop, providing a standardized multi-chain API for transaction management, account insights, staking, and token interactions.128 npm1MIT
Zetrix MCP Serverofficial
AlicenseBqualityDmaintenanceEnables comprehensive interaction with the Zetrix blockchain including account operations, transactions, smart contracts, WebSocket real-time updates, and contract development tools through Claude Desktop.4425 npmMIT
TDQS
Scored across 92 tools
Multiple tools have overlapping functionality, e.g., nft_get_transfer_history and vechainstats_get_nft_transfers both retrieve NFT transfer history, and get_token_info vs vechainstats_get_token_info are nearly identical. The sheer number of similar getters makes it difficult for an agent to select the correct tool.
Naming is inconsistent: some tools use a namespace prefix (vechainstats_, nft_, bridge_), others are bare verbs (stake_vet, sign_message, transfer_vet). No uniform verb_noun pattern, and similar operations are named differently across domains (e.g., get_user_stakes vs nft_get_owned_tokens).
With 92 tools, the server is dramatically over-scoped for a coherent toolkit. This is far beyond the typical 3-15 well-chosen tools and even exceeds the 25+ threshold for a heavy set.
The server covers many domains (stats, NFT, DEX, bridge, wallet, VeBetter), but each domain has gaps. For example, NFT operations lack metadata updates, and VeBetter lacks submission status or cancellation. The extraordinary breadth means depth suffers, leaving some workflows incomplete.