VeChain MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host where your MCP server will run when using streamable-http. | |
| PORT | No | Port where your MCP server will run when using streamable-http. | |
| ENVIRONMENT | Yes | Working environment, either mainnet or test. | |
| AGENT_SECRET_KEY | Yes | Secret key in string format that allows your MCP server to use the signatures tools. | |
| USE_STREAMABLE_HTTP | No | Specifies whether your MCP server will run on stdio or streamable-http. |
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_addressC | Get the address of the wallet |
| get_chainB | Get the chain of the wallet |
| sign_messageC | Sign a message with the wallet |
| get_balanceC | Get the balance of the wallet for native currency or a specific ERC20 token. |
| get_token_info_by_tickerC | Get information about a configured token (like contract address and decimals) by its ticker symbol. |
| convert_to_base_unitsC | Convert a token amount from human-readable units to its smallest unit (e.g., wei). |
| convert_from_base_unitsC | Convert a token amount from its smallest unit (e.g., wei) to human-readable units. |
| sign_typed_data_evmC | Sign an EIP-712 typed data structure (EVM) |
| get_token_allowance_evmC | Get the allowance of an ERC20 token for a spender (returns amount in base units) |
| send_tokenC | Send native currency or an ERC20 token to a recipient, in base units. |
| approve_token_evmC | Approve an amount (specified in base units) of an ERC20 token for a spender |
| revoke_token_approval_evmA | Revoke approval for an ERC20 token from a spender (sets allowance to 0) |
| search_documentationA | Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about VeChain Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. |
| get_accountA | Get information about a VeChain account/contract by address. Optionally specify a revision (best | justified | finalized | block number | block ID). |
| get_transactionA | Get a VeChain transaction by its ID. Optionally include pending txs (meta may be null), return raw hex, or pin to a specific head block. |
| get_blockB | Retrieve information about a VeChain block by its revision (block ID, number, or keywords: best | justified | finalized). |
| get_priority_feeB | Fetch a suggested priority fee for including a transaction in the next blocks from VeChain mainnet. |
| create_walletA | Generate a BIP-39 mnemonic (12/15/18/21/24 words) and derive the account-level secp256k1 key at path m/44'/818'/0'/0 (VET coin type = 818). By default, the private key is REDACTED in the response. Set includeSecret=true to include it (handle with care). |
| sign_certificateC | Create and sign a canonical certificate. Includes purpose, payload, domain, timestamp, nonce, and expiresAt. |
| sign_raw_transactionC | Decode and sign a raw transaction. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Most tools have distinct purposes, such as get_account for account info, send_token for transfers, and sign_message for signing. However, there is some overlap between sign_raw_transaction and sign_typed_data_evm, which both involve signing but for different data formats, potentially causing minor confusion. Overall, the descriptions help clarify differences, but the signing tools could be slightly ambiguous.
The tool names follow a consistent snake_case pattern with clear verb_noun structures, such as get_balance, send_token, and sign_message. Minor deviations exist, like convert_from_base_units and convert_to_base_units being more descriptive but still adhering to the pattern. The naming is mostly predictable and readable, with only slight variations in verb usage.
With 20 tools, the count is slightly high but reasonable for a blockchain server covering wallet management, token operations, signing, and documentation search. It includes essential functions like account queries, transfers, and approvals, though it borders on being heavy. The tools are well-scoped for the VeChain domain, but some consolidation might improve efficiency.
The tool set provides comprehensive coverage for the VeChain blockchain domain, including CRUD-like operations for accounts, tokens, and transactions, as well as wallet creation, signing, and documentation search. There are no obvious gaps; it supports core workflows from querying balances to executing transactions and managing approvals, ensuring agents can handle typical tasks without dead ends.