How do I use Zetrix MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Zetrix MCP Server what's the balance of account ZETRIX1234567890abcdef?" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

Zetrix MCP Server

Official

by Zetrix-Chain

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Zetrix MCP Server

A comprehensive Model Context Protocol (MCP) server for interacting with the Zetrix blockchain. Provides 55 tools across 7 categories — HTTP RPC, WebSocket (protobuf), SDK transactions, cryptography, and smart contract development. Supports both stdio and HTTP transport modes.

Zetrix Currency Information

Native Coin: ZETRIX

Main Unit: ZETRIX
Base Unit: ZETA
Conversion: 1 ZETRIX = 1,000,000 ZETA
Gas Price: Evaluated dynamically via testTransaction

Related MCP server: MCP Crypto Wallet EVM

Quick Start

npx zetrix-mcp-server

Or install globally:

npm install -g zetrix-mcp-server

Guides:

QUICKSTART.md — Get set up in 5 minutes
EXAMPLES.md — Learn through 20+ examples
TEST_REPORT.md — Comprehensive test results for all 55 tools

Features (56 Tools)

General (1 tool)

Tool	Description
`zetrix_version`	Get MCP server version and network info

HTTP RPC (16 tools)

Tool	Description
`zetrix_check_health`	Check node health status
`zetrix_get_account`	Get account info including balance and metadata
`zetrix_get_block`	Get block by height
`zetrix_get_latest_block`	Get latest block
`zetrix_get_transaction`	Get transaction by hash
`zetrix_get_balance`	Get balance in ZETA and ZETRIX
`zetrix_create_keypair`	Generate new keypair (testing only)
`zetrix_get_account_base`	Get basic account info
`zetrix_get_account_assets`	Get asset holdings
`zetrix_get_account_metadata`	Get account metadata
`zetrix_get_transaction_history`	Get completed transactions
`zetrix_get_transaction_cache`	Get pending transactions
`zetrix_get_ledger`	Get ledger/block info
`zetrix_multi_query`	Execute multiple queries
`zetrix_get_transaction_blob`	Serialize transaction to hex
`zetrix_submit_transaction`	Submit signed transaction

Contract Query (2 tools)

Tool	Description
`zetrix_call_contract`	Call contract in sandbox (read-only)
`zetrix_test_transaction`	Evaluate fees without submitting

WebSocket — Real-time (5 tools)

Uses protobuf binary encoding for communication with Zetrix nodes.

Tool	Description
`zetrix_ws_connect`	Connect and register via protobuf CHAIN_HELLO
`zetrix_ws_submit_transaction`	Submit transaction with real-time status
`zetrix_ws_subscribe_tx`	Subscribe to transaction notifications
`zetrix_ws_disconnect`	Disconnect from WebSocket
`zetrix_ws_status`	Check connection status

SDK Query (5 tools)

Tool	Description
`zetrix_sdk_create_account`	Create new account
`zetrix_sdk_get_balance`	Get balance via SDK
`zetrix_sdk_is_activated`	Check if account is activated
`zetrix_sdk_get_nonce`	Get account nonce
`zetrix_sdk_call_contract`	Call contract via SDK (read-only)

SDK Transactions (11 tools)

All transaction tools use evaluateFee (testTransaction) for dynamic gas pricing. Optional gasPrice/feeLimit overrides supported on all operations.

Tool	Description
`zetrix_sdk_send_gas`	Send native ZETRIX to another address
`zetrix_sdk_activate_account`	Activate a new account with initial balance
`zetrix_sdk_set_metadata`	Set key-value metadata on an account
`zetrix_sdk_set_privilege`	Set account weights, thresholds, and signers
`zetrix_sdk_issue_asset`	Issue a new custom token
`zetrix_sdk_send_asset`	Transfer a custom token
`zetrix_sdk_create_contract`	Deploy a smart contract (with optional owner)
`zetrix_sdk_invoke_contract`	Invoke contract with gas payment
`zetrix_sdk_invoke_contract_by_asset`	Invoke contract with asset transfer
`zetrix_sdk_upgrade_contract`	Upgrade contract code and/or transfer ownership
`zetrix_sdk_create_log`	Create an on-chain event log

Cryptography (8 tools)

Tool	Description
`zetrix_crypto_generate_keypair`	Generate new keypair (address, private key, public key)
`zetrix_crypto_get_public_key`	Derive public key from private key
`zetrix_crypto_get_address`	Get address from public key
`zetrix_crypto_validate_key`	Validate private key, public key, or address format
`zetrix_crypto_sign`	Sign a message (hex) with a private key
`zetrix_crypto_verify`	Verify a signature
`zetrix_crypto_encrypt_key`	Encrypt private key with password
`zetrix_crypto_decrypt_key`	Decrypt encrypted private key

Smart Contract Development (7 tools)

Tool	Description
`zetrix_contract_get_chain_functions`	Chain object function documentation
`zetrix_contract_get_utils_functions`	Utils object function documentation
`zetrix_contract_get_structure_guide`	Contract structure and ES5 patterns guide
`zetrix_contract_get_token_standard`	Token standard specs (ZTP20, ZTP721, ZTP1155)
`zetrix_contract_init_dev_environment`	Initialize dev project via `create-zetrix-tool`
`zetrix_contract_generate_advanced`	Generate multi-class contract architecture
`zetrix_contract_get_testing_guide`	Testing guide (TEST_INVOKE, TEST_QUERY)

Supported Networks

Network	HTTP RPC	WebSocket
Mainnet	`https://node.zetrix.com`	`wss://ws-node.zetrix.com`
Testnet	`https://test-node.zetrix.com`	`wss://test-ws-node.zetrix.com`

Configuration

Environment Variables

Variable	Description	Default
`ZETRIX_NETWORK`	Network selection (`mainnet` or `testnet`)	`mainnet`
`ZETRIX_RPC_URL`	Custom HTTP RPC endpoint (overrides network default)	—
`ZETRIX_WS_URL`	Custom WebSocket endpoint (overrides network default)	—
`ZETRIX_TRANSPORT`	Transport mode (`stdio` or `http`)	`stdio`
`ZETRIX_PORT`	HTTP server port (only used when `ZETRIX_TRANSPORT=http`)	`3000`
`ZETRIX_PRIVATE_KEY`	Default private key for signing transactions (optional, keeps key out of conversation)	—
`ZETRIX_SOURCE_ADDRESS`	Default source address for transactions (optional)	—

Secure Transactions (Recommended)

By setting ZETRIX_PRIVATE_KEY and ZETRIX_SOURCE_ADDRESS as environment variables, your private key is never exposed in the conversation. The LLM can execute transactions like "send 0.01 ZETRIX to ZTX3..." without ever seeing your key.

{
  "mcpServers": {
    "zetrix": {
      "command": "npx",
      "args": ["-y", "zetrix-mcp-server"],
      "env": {
        "ZETRIX_NETWORK": "testnet",
        "ZETRIX_PRIVATE_KEY": "your-private-key-here",
        "ZETRIX_SOURCE_ADDRESS": "your-zetrix-address-here"
      }
    }
  }
}

Note: These are optional. If not set, the LLM will need to ask for or be given the private key and source address in the conversation. If set, they are used as defaults — you can still override them per-tool call if needed.

Claude Code (CLI)

Add the MCP server directly from the command line:

Mainnet:

claude mcp add zetrix-mainnet -s user -- npx -y zetrix-mcp-server -e ZETRIX_NETWORK=mainnet

Testnet:

claude mcp add zetrix-testnet -s user -- npx -y zetrix-mcp-server -e ZETRIX_NETWORK=testnet

With custom RPC and WebSocket URLs:

claude mcp add zetrix-testnet -s user -- npx -y zetrix-mcp-server \
  -e ZETRIX_NETWORK=testnet \
  -e ZETRIX_RPC_URL=https://your-node.example.com \
  -e ZETRIX_WS_URL=wss://your-ws-node.example.com

Claude Desktop

Edit your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Windows (Microsoft Store): %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json

Testnet:

{
  "mcpServers": {
    "zetrix": {
      "command": "npx",
      "args": ["-y", "zetrix-mcp-server"],
      "env": {
        "ZETRIX_NETWORK": "testnet"
      }
    }
  }
}

Mainnet:

{
  "mcpServers": {
    "zetrix": {
      "command": "npx",
      "args": ["-y", "zetrix-mcp-server"],
      "env": {
        "ZETRIX_NETWORK": "mainnet"
      }
    }
  }
}

Both networks (mainnet + testnet):

{
  "mcpServers": {
    "zetrix-mainnet": {
      "command": "npx",
      "args": ["-y", "zetrix-mcp-server"],
      "env": {
        "ZETRIX_NETWORK": "mainnet"
      }
    },
    "zetrix-testnet": {
      "command": "npx",
      "args": ["-y", "zetrix-mcp-server"],
      "env": {
        "ZETRIX_NETWORK": "testnet"
      }
    }
  }
}

With custom RPC and WebSocket URLs:

{
  "mcpServers": {
    "zetrix": {
      "command": "npx",
      "args": ["-y", "zetrix-mcp-server"],
      "env": {
        "ZETRIX_NETWORK": "testnet",
        "ZETRIX_RPC_URL": "https://your-node.example.com",
        "ZETRIX_WS_URL": "wss://your-ws-node.example.com"
      }
    }
  }
}

After saving the config file, restart Claude Desktop for changes to take effect.

Note: ZETRIX_RPC_URL and ZETRIX_WS_URL override the default endpoints for the selected network. You can override just one or both. If not set, the defaults from the table above are used.

HTTP Transport (API Server)

Run the MCP server as an HTTP API server using the Streamable HTTP transport. This allows remote MCP clients to connect over the network.

Start the server (defaults to mainnet):

ZETRIX_TRANSPORT=http ZETRIX_PORT=3000 npx zetrix-mcp-server

With testnet:

ZETRIX_TRANSPORT=http ZETRIX_PORT=3000 ZETRIX_NETWORK=testnet npx zetrix-mcp-server

Endpoints:

Endpoint	Method	Description
`/mcp`	POST	MCP protocol endpoint (Streamable HTTP)
`/health`	GET	Health check — returns `{ status, version, network }`

Connect from an MCP client:

{
  "mcpServers": {
    "zetrix": {
      "type": "http",
      "url": "http://localhost:3000/mcp"
    }
  }
}

Both networks (mainnet + testnet):

Run two servers on different ports:

ZETRIX_TRANSPORT=http ZETRIX_PORT=3000 ZETRIX_NETWORK=mainnet npx zetrix-mcp-server &
ZETRIX_TRANSPORT=http ZETRIX_PORT=3001 ZETRIX_NETWORK=testnet npx zetrix-mcp-server &

Then configure your MCP client:

{
  "mcpServers": {
    "zetrix-mainnet": {
      "type": "http",
      "url": "http://localhost:3000/mcp"
    },
    "zetrix-testnet": {
      "type": "http",
      "url": "http://localhost:3001/mcp"
    }
  }
}

Note: The HTTP transport uses the MCP Streamable HTTP specification. Any MCP client that supports StreamableHTTP transport can connect to it.

Server logs:

The server logs to stderr. To view logs, run in the foreground or redirect to a file:

# Foreground — logs show directly in terminal
ZETRIX_TRANSPORT=http ZETRIX_PORT=3000 npx zetrix-mcp-server

# Background with logs to file
ZETRIX_TRANSPORT=http ZETRIX_PORT=3000 npx zetrix-mcp-server 2> server.log &
tail -f server.log

Development

Project Structure

zetrix-mcp-server/
├── src/
│   ├── index.ts                  # MCP server (55 tool definitions + handlers)
│   ├── zetrix-client.ts          # HTTP RPC client
│   ├── zetrix-sdk.ts             # SDK wrapper (11 transaction operations)
│   ├── zetrix-websocket.ts       # WebSocket client (protobuf binary)
│   ├── zetrix-encryption.ts      # Crypto operations
│   ├── zetrix-contract-docs.ts   # Contract documentation
│   └── zetrix-contract-generator.ts # Contract code generator
├── tests/
│   ├── test-server.js            # HTTP RPC tests
│   ├── test-sdk.js               # SDK tests
│   └── test-encryption.js        # Crypto tests
├── docs/
│   ├── TEST_REPORT.md            # Comprehensive test results
│   ├── DEVELOPER_GUIDE.md        # Developer documentation
│   ├── ZETRIX_CONTRACT_DEVELOPMENT_RULES.md
│   ├── QUICKSTART.md             # 5-minute setup guide
│   └── EXAMPLES.md               # 20+ usage examples
└── dist/                         # Compiled output

Build

npm install
npm run build

Test

npm test                           # HTTP RPC tests
ZETRIX_NETWORK=testnet npm test    # Run on testnet
npm run test:sdk                   # SDK tests
npm run test:encryption            # Crypto tests

License

MIT

Available Tools

44 tools

zetrix_call_contractB

Call smart contract in sandbox environment for debugging

Name	Required	Description
`contractAddress`	No	Deployed contract address (optional)
`code`	No	Contract source code (optional)
`input`	No	Function parameters (optional)
`contractBalance`	No	Contract balance (optional)
`feeLimit`	No	Fee limit (optional)
`gasPrice`	No	Gas price (optional)
`optType`	No	Operation type (optional)
`sourceAddress`	No	Source address (optional)

zetrix_check_healthB

Check the health status of the Zetrix node

Name	Required	Description	Default
No parameters

zetrix_contract_generate_advancedA

Generate advanced multi-class Zetrix smart contract with interfaces, libraries, utilities, main contract, and comprehensive test specs. MANDATORY WORKFLOW: (1) First call zetrix_contract_init_dev_environment with contractName (e.g., 'CertificateContract'). (2) Then call this tool with the SAME contractName and outputDirectory set to './{contractName}'. Calling this tool WITHOUT initializing the project first will result in an error. Supports complex architectures with inheritance, composition, and modular design.

Name	Required	Description
`contractName`	Yes	Name of the main contract (e.g., 'StableCoin', 'NFTMarketplace')
`contractType`	Yes	Type of contract to generate
`features`	No	Advanced features to include
`tokenStandard`	No	Token standard (required if contractType is 'token' or 'nft')
`includeTests`	No	Generate comprehensive test specifications (default: true)
`outputDirectory`	No	Directory to output the contract files (defaults to current directory)

zetrix_contract_get_chain_functionsA

Get documentation for all built-in Chain object functions available in Zetrix smart contracts

Name	Required	Description	Default
No parameters

zetrix_contract_get_structure_guideB

Get guide on how to structure Zetrix smart contracts with ES5 patterns, classes, and inheritance

Name	Required	Description	Default
No parameters

zetrix_contract_get_testing_guideB

Get guide on testing Zetrix smart contracts with TEST_INVOKE and TEST_QUERY

Name	Required	Description	Default
No parameters

zetrix_contract_get_token_standardC

Get token standard specification (ZTP20, ZTP721, or ZTP1155)

Name	Required	Description	Default
`standard`	Yes	Token standard to get documentation for

zetrix_contract_get_utils_functionsB

Get documentation for all built-in Utils object functions available in Zetrix smart contracts

Name	Required	Description	Default
No parameters

zetrix_contract_init_dev_environmentB

Initialize a new Zetrix smart contract development environment using create-zetrix-tool. This creates a complete project structure with testing framework, examples, and utilities.

Name	Required	Description	Default
`contractName`	Yes	Name of the contract project to create (alphanumeric and hyphens only)
`workingDirectory`	No	Directory where to create the project (defaults to current directory)

zetrix_create_keypairB

Generate a new public-private key pair (for testing only)

Name	Required	Description	Default
No parameters

zetrix_crypto_decrypt_keyC

Decrypt an encrypted private key with a password

Name	Required	Description	Default
`encryptedData`	Yes	The encrypted keystore data
`password`	Yes	The password used for encryption

zetrix_crypto_encrypt_keyC

Encrypt a private key with a password for secure storage

Name	Required	Description	Default
`privateKey`	Yes	The private key to encrypt
`password`	Yes	The password to use for encryption

zetrix_crypto_generate_keypairB

Generate a new Zetrix key pair with private key, public key, and address

Name	Required	Description	Default
No parameters

zetrix_crypto_get_addressC

Get Zetrix address from public key

Name	Required	Description	Default
`publicKey`	Yes	The public key

zetrix_crypto_get_public_keyC

Derive public key from private key

Name	Required	Description	Default
`privateKey`	Yes	The encrypted private key

zetrix_crypto_signC

Sign a message with a private key

Name	Required	Description	Default
`message`	Yes	The message to sign (hex string)
`privateKey`	Yes	The private key to sign with

zetrix_crypto_validate_keyC

Validate private key, public key, or address format

Name	Required	Description	Default
`type`	Yes	Type of key to validate
`value`	Yes	The key or address to validate

zetrix_crypto_verifyC

Verify a signature against a message and public key

Name	Required	Description
`message`	Yes	The original message (hex string)
`signature`	Yes	The signature to verify
`publicKey`	Yes	The public key to verify against

zetrix_get_accountC

Get Zetrix account information including balance and metadata

Name	Required	Description	Default
`address`	Yes	The Zetrix account address

zetrix_get_account_assetsB

Get asset holdings for an account

Name	Required	Description
`address`	Yes	The Zetrix account address
`code`	No	Asset code (optional, must be used with issuer)
`issuer`	No	Asset issuer address (optional, must be used with code)

zetrix_get_account_baseB

Get basic account information without assets and metadata

Name	Required	Description	Default
`address`	Yes	The Zetrix account address

zetrix_get_account_metadataC

Get metadata associated with an account

Name	Required	Description	Default
`address`	Yes	The Zetrix account address
`key`	No	Specific metadata key (optional)

zetrix_get_balanceB

Get the ZETRIX balance of an account. Returns balance in both ZETA (micro units) and ZETRIX (main units). Note: 1 ZETRIX = 1,000,000 ZETA

Name	Required	Description	Default
`address`	Yes	The Zetrix account address

zetrix_get_blockC

Get information about a specific block by height

Name	Required	Description	Default
`blockNumber`	Yes	The block height/number to query

zetrix_get_latest_blockB

Get the latest block information from Zetrix blockchain

Name	Required	Description	Default
No parameters

zetrix_get_ledgerC

Get block/ledger information with optional details

Name	Required	Description
`seq`	No	Block sequence number (optional)
`withValidator`	No	Include validator list (optional)
`withConsValue`	No	Include consensus value (optional)
`withFee`	No	Include fee configuration (optional)

zetrix_get_transactionC

Get transaction details by transaction hash

Name	Required	Description	Default
`hash`	Yes	The transaction hash

zetrix_get_transaction_blobC

Serialize transaction data into hexadecimal format

Name	Required	Description	Default
`transaction`	Yes	Transaction object with source_address, nonce, fee_limit, gas_price, operations

zetrix_get_transaction_cacheC

Get pending transactions not yet executed

Name	Required	Description	Default
`hash`	No	Transaction hash (optional)
`limit`	No	Number of pending transactions to return (optional)

zetrix_get_transaction_historyC

Get completed transaction records

Name	Required	Description	Default
`hash`	No	Transaction hash (optional)
`ledgerSeq`	No	Block sequence number (optional)

zetrix_multi_queryC

Execute multiple API queries simultaneously

Name	Required	Description	Default
`items`	Yes	Array of query objects

zetrix_sdk_call_contractA

Call a smart contract function (query only, no state change) using SDK

Name	Required	Description
`contractAddress`	Yes	The deployed smart contract address
`input`	No	JSON string with method and params
`sourceAddress`	No	Optional source address for the call

zetrix_sdk_create_accountB

Create a new Zetrix account using the official SDK

Name	Required	Description	Default
No parameters

zetrix_sdk_get_balanceC

Get account balance using the official SDK

Name	Required	Description	Default
`address`	Yes	The Zetrix account address

zetrix_sdk_get_nonceC

Get account nonce (transaction sequence number)

Name	Required	Description	Default
`address`	Yes	The Zetrix account address

zetrix_sdk_invoke_contractB

Invoke a smart contract function with state change (requires private key)

Name	Required	Description
`sourceAddress`	Yes	The account address initiating the transaction
`privateKey`	Yes	Private key for signing the transaction
`contractAddress`	Yes	The smart contract address to invoke
`amount`	Yes	Amount of ZTX to send with invocation (in micro-ZTX)
`input`	Yes	JSON string with method and params
`metadata`	No	Optional transaction description

zetrix_sdk_is_activatedC

Check if an account is activated on the blockchain

Name	Required	Description	Default
`address`	Yes	The Zetrix account address

zetrix_submit_transactionC

Submit signed transaction to blockchain for execution

Name	Required	Description	Default
`transactionBlob`	Yes	Serialized transaction blob
`signatures`	Yes	Array of signature objects with sign_data and public_key

zetrix_test_transactionB

Evaluate transaction fees without blockchain submission

Name	Required	Description	Default
`items`	Yes	Array of test transaction items

zetrix_ws_connectC

Connect and register to Zetrix WebSocket for real-time updates

Name	Required	Description	Default
`apiList`	No	Optional list of API message types to register (numbers)

zetrix_ws_disconnectB

Disconnect from WebSocket

Name	Required	Description	Default
No parameters

zetrix_ws_statusB

Check WebSocket connection status

Name	Required	Description	Default
No parameters

zetrix_ws_submit_transactionB

Submit transaction via WebSocket and get real-time status updates

Name	Required	Description
`transaction`	Yes	Transaction object
`signatures`	Yes	Array of signature objects with public_key and sign_data
`trigger`	No	Optional trigger object

zetrix_ws_subscribe_txC

Subscribe to transaction notifications for specific addresses

Name	Required	Description	Default
`addresses`	Yes	Array of account addresses to subscribe to

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

44 tool updatesDec 29, 2025
- First observedzetrix_call_contract
- First observedzetrix_check_health
- First observedzetrix_contract_generate_advanced
- First observedzetrix_contract_get_chain_functions
- First observedzetrix_contract_get_structure_guide
- First observedzetrix_contract_get_testing_guide
- First observedzetrix_contract_get_token_standard
- First observedzetrix_contract_get_utils_functions
- First observedzetrix_contract_init_dev_environment
- First observedzetrix_create_keypair
- First observedzetrix_crypto_decrypt_key
- First observedzetrix_crypto_encrypt_key
- First observedzetrix_crypto_generate_keypair
- First observedzetrix_crypto_get_address
- First observedzetrix_crypto_get_public_key
- First observedzetrix_crypto_sign
- First observedzetrix_crypto_validate_key
- First observedzetrix_crypto_verify
- First observedzetrix_get_account
- First observedzetrix_get_account_assets
- First observedzetrix_get_account_base
- First observedzetrix_get_account_metadata
- First observedzetrix_get_balance
- First observedzetrix_get_block
- First observedzetrix_get_latest_block
- First observedzetrix_get_ledger
- First observedzetrix_get_transaction
- First observedzetrix_get_transaction_blob
- First observedzetrix_get_transaction_cache
- First observedzetrix_get_transaction_history
- First observedzetrix_multi_query
- First observedzetrix_sdk_call_contract
- First observedzetrix_sdk_create_account
- First observedzetrix_sdk_get_balance
- First observedzetrix_sdk_get_nonce
- First observedzetrix_sdk_invoke_contract
- First observedzetrix_sdk_is_activated
- First observedzetrix_submit_transaction
- First observedzetrix_test_transaction
- First observedzetrix_ws_connect
- First observedzetrix_ws_disconnect
- First observedzetrix_ws_status
- First observedzetrix_ws_submit_transaction
- First observedzetrix_ws_subscribe_tx

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored 2026-04-18 07:31 across 44 tools

Disambiguation3/5

The tool set has clear thematic grouping (e.g., crypto, account, contract, SDK, WebSocket), but there is notable overlap within groups. For example, zetrix_get_account, zetrix_get_account_base, and zetrix_get_balance all retrieve account-related data with subtle distinctions that could confuse agents. Similarly, multiple contract call tools (zetrix_call_contract, zetrix_sdk_call_contract) and transaction submission tools (zetrix_submit_transaction, zetrix_ws_submit_transaction) have overlapping purposes, though descriptions provide some guidance.

Naming Consistency5/5

Tool names follow a highly consistent pattern throughout: all start with 'zetrix_' prefix, use snake_case uniformly, and employ a verb_noun structure (e.g., zetrix_get_balance, zetrix_create_keypair). Minor deviations like 'zetrix_multi_query' (adjective_verb_noun) are rare and do not disrupt readability, maintaining excellent predictability across all 44 tools.

Tool Count2/5

With 44 tools, the server is overly broad and heavy for a single MCP server, likely covering multiple domains (blockchain interaction, smart contract development, cryptography, WebSocket management). This high count increases complexity and cognitive load for agents, making it difficult to navigate efficiently. A more modular approach with separate servers for distinct functionalities would be more appropriate.

Completeness4/5

The tool surface is extensive and covers core blockchain operations comprehensively, including account management, transaction handling, contract development, and real-time updates. However, there are minor gaps: for instance, tools for updating or deleting accounts are missing, and some advanced contract management features (e.g., contract deployment or upgrade) are not explicitly covered, though the provided guides and generation tools mitigate this.

Resources

Related MCP Connectors

WhereItGoesA
money.whereitgoes
Read-only access to your own crypto portfolio across 11+ exchanges and 20+ chains: holdings, full history, FIFO cost basis and P&L, fees and income. Ask Claude or ChatGPT about your portfolio; the connector can never trade, move funds or act as a login.
Cryptocurrency Data Visualization Finance
1511
https://api.whereitgoes.money/api/mcp
constants
io.github.constants-ai
One workspace of tools for Claude and ChatGPT: connect 600+ apps, generate media, build tools.
App Automation Developer Tools Multimedia Processing
1
https://www.constants.io/api/mcp
platform7n
tech.p7n
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Communication Project Management Workplace & Productivity
2
https://api.p7n.tech/mcp
EngramB
ro.rootcause
A second brain for Claude: remembers your work, plans your day, encrypted under a key only you hold.
Knowledge & Memory Note Taking Workplace & Productivity
441
https://engram.rootcause.ro/mcp/directory

Related MCP Servers

Adamik MCP Serverofficial
Blockchain Web3 & Decentralized Tech
AdamikHQ
A
license
A
quality
D
maintenance
Enables 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.
Updated a year ago (2025-06-24 07:52 UTC)
12
25 npm
1
MIT
MCP Crypto Wallet EVM
Blockchain Web3 & Decentralized Tech Cryptocurrency
dcSpark
A
license
B
quality
D
maintenance
Provides Claude with access to Ethereum and EVM-compatible blockchain operations, enabling wallet management, transaction handling, contract interactions, and blockchain queries through natural language.
Updated 2 years ago (2025-03-26 03:12 UTC)
35
169 npm
10
MIT
Stacks MCP Server
Blockchain Web3 & Decentralized Tech
khoa-solo
A
license
Not graded
quality
D
maintenance
Enables 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.
Updated 10 months ago (2026-01-25 05:32 UTC)
30 npm
6
MIT
VeChain AI Terminal MCP Server
Blockchain Cryptocurrency Web3 & Decentralized Tech
VeChain-AI-Terminal
A
license
C
quality
D
maintenance
Enables Claude Desktop to interact with the VeChain blockchain through natural language commands for token transfers, DEX trading, cross-chain bridges, NFT management, and VeBetter DAO operations.
Updated a year ago (2025-10-06 01:27 UTC)
93
4
MIT

Zetrix MCP Server

Zetrix Currency Information

Quick Start

Features (56 Tools)

General (1 tool)

HTTP RPC (16 tools)

Contract Query (2 tools)

WebSocket — Real-time (5 tools)

SDK Query (5 tools)

SDK Transactions (11 tools)

Cryptography (8 tools)

Smart Contract Development (7 tools)

Supported Networks

Configuration

Environment Variables

Secure Transactions (Recommended)

Claude Code (CLI)

Claude Desktop

HTTP Transport (API Server)

Development

Project Structure

Build

Test

License

Available Tools

Tool Schema Changelog

TDQS

Resources

Related MCP Connectors

Related MCP Servers

Adamik MCP Serverofficial

MCP Crypto Wallet EVM

Stacks MCP Server

VeChain AI Terminal MCP Server