qubic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_PORT | No | Set a port to run as an HTTP server instead of stdio | |
| QUBIC_API_URL | No | Override the Query API endpoint | |
| QUBIC_RPC_URL | No | Override the RPC endpoint (takes priority over saved networks) | |
| QUBIC_NETWORK_LABEL | No | Friendly label shown when using QUBIC_RPC_URL override |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceA | Get the current balance of a Qubic address or saved wallet. Accepts a 60-character Qubic address OR a saved wallet name (e.g., "my-main"). Use save_wallet to save addresses for quick access. |
| get_tick_infoA | Get the current Qubic network tick information. Returns the current tick number, epoch, and tick duration. Qubic processes transactions in ticks (~5 seconds each) organized into epochs (~1 week each). |
| get_network_statusA | Get comprehensive Qubic network status including current tick, epoch progress, circulating supply, burned QUs, active addresses, price, and market cap. |
| get_transactionA | Look up a Qubic transaction by its transaction ID. Returns source, destination, amount, tick, and execution status. Transaction IDs are 60 lowercase letters. |
| get_token_priceA | Get the current QUBIC token price compared across multiple sources (CoinGecko, Qubic Official API, CryptoCompare). Shows price, 24h change, market cap, and volume with source-by-source comparison. |
| get_transfer_historyA | Get the transfer history for a Qubic address or saved wallet within a tick range. Returns incoming and outgoing transfers with details. Use get_tick_info first to find the current tick number. |
| get_mining_phaseA | Get the current Qubic mining phase (MINING or IDLE) and whether it's an XMR marathon day. The network alternates between mining and idle phases every ~1,353 ticks, and between Qubic AI solution days and XMR mining days every 24 hours. |
| get_rich_listA | Get the Qubic rich list — top addresses ranked by balance for the current epoch. Supports pagination. |
| convert_qu_usdA | Convert between QU (Qubic Units) and USD using the current live price. Specify either a QU amount to get USD value, or a USD amount to get the equivalent in QU. |
| validate_addressA | Validate a Qubic address format and check if it exists on-chain with balance or transfer activity. |
| get_explorer_linksA | Get links to Qubic block explorers for an address or transaction ID. Accepts saved wallet names. |
| get_token_listA | Get a list of all registered Qubic tokens with their name, issuer address, and website. Useful for finding token issuers needed for QX orderbook queries. |
| get_qx_orderbookA | Query the QX decentralized exchange orderbook for a Qubic token. Returns current ask (sell) and bid (buy) orders with price and quantity. IMPORTANT: You MUST call get_token_list first to find the exact issuer address. NEVER guess or fabricate an issuer address. If the token is not in the registry, tell the user it was not found and ask them to provide the issuer address. |
| save_walletA | Save a Qubic wallet address with a friendly name for quick access. Only saves the public address — never stores seeds or private keys. Stored locally in ~/.qubic-mcp/wallets.json. |
| list_walletsA | List all saved Qubic wallet addresses. These are public addresses only — no private keys are ever stored. |
| remove_walletA | Remove a saved wallet by name. This only removes the local reference — it does not affect the actual blockchain address in any way. |
| add_networkA | Save a custom Qubic network (e.g., a local lite node). Stored in ~/.qubic-mcp/networks.json. Use switch_network to activate it. |
| switch_networkA | Switch the active Qubic network. All subsequent tool calls will use the new endpoint. Built-in networks: "mainnet", "testnet". Use add_network to save custom networks. |
| list_networksA | List all available Qubic networks (built-in and custom) and show which is currently active. |
| remove_networkA | Remove a saved custom network. Cannot remove built-in networks (mainnet, testnet). If the removed network was active, switches back to mainnet. |
| query_smart_contractB | Query a Qubic smart contract (read-only). Returns the contract's response data as base64-encoded bytes. Known contracts: 1: QX (Decentralized Exchange) 2: Quottery (Betting & Oracles) 3: Random (Random Number Generation) 4: QUTIL (Utility Functions) 5: MLM (My Last Match - Gaming) This is a low-level query tool. Use inputType to specify which contract function to call, and inputHex for the function parameters (hex-encoded bytes). If unsure about parameters, start with inputType=0 and empty input to get contract info. |
| register_contractA | Register a custom smart contract definition for use with query_contract. Provide the contract's on-chain index and a JSON array of function definitions describing the binary input/output layout. Once registered, you can query the contract by name with automatic encoding and decoding. Supported field types: uint8, uint16, uint32, uint64, int8, int16, int32, int64, identity (32-byte pubkey ↔ 60-char address), padding (skipped bytes). Fields support "count" for arrays (e.g., 8 recipients) and "enum" for value→label mapping. Example functions JSON: [{ "name": "getGateCount", "inputType": 6, "input": [], "output": [ { "name": "totalGates", "type": "uint64" }, { "name": "activeGates", "type": "uint64" } ] }] |
| list_contractsA | List all registered custom smart contract definitions with their functions and field schemas. |
| remove_contractB | Remove a registered smart contract definition by name. |
| query_contractA | Query a registered smart contract function with automatic binary encoding/decoding. Use register_contract first to define the contract's functions and their field schemas. Then call this tool by contract name and function name. Input values are provided as a JSON object with field names as keys. For example: {"gateId": 1} The response is automatically decoded into human-readable named fields. |
| get_epoch_computorsA | List the computor identities for a given epoch. Computors are the 676 nodes that validate transactions on the Qubic network. Defaults to the current epoch if none is specified. |
| get_versionA | Get the current qubic-mcp server version |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| qubic-portfolio | Analyze your Qubic portfolio: wallet balances, token holdings, and USD values |
| qubic-market | Comprehensive Qubic market overview: price, network stats, mining phase, and top token orderbooks |
| qubic-research | Research a specific Qubic token: orderbook analysis, spread, depth, and price context |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs-network | Qubic network: epochs, ticks, quorum consensus, computor ranking |
| docs-tokenomics | Qubic tokenomics: $QUBIC as energy, supply cap, emission schedule, burning |
| docs-smart-contracts | Qubic smart contracts: governance, execution, IPO process |
| docs-address-format | Qubic identity system: seed → private key → public key → 60-char address |
| docs-oracles | Qubic Oracle Machines: bridging smart contracts with real-world data via QPI |
| docs-sc-architecture | Qubic smart contract architecture: state, procedures, functions, logging |
| docs-sc-lifecycle | Smart contract lifecycle: from research through proposal, IPO, deployment, and maintenance |
| docs-ticks-concurrency | Qubic ticks and concurrency: tick lifecycle, parallel execution, transaction ordering |
| docs-interact-sc | Interacting with Qubic smart contracts: calling functions, invoking procedures |
| docs-execution-fees | Qubic contract execution fees: fee reserves, invocation costs, burn mechanics |
| docs-rpc | Qubic RPC API: endpoints, smart contract queries, transaction broadcasting |
| docs-qpi | Qubic Protocol Interface (QPI): the API available to smart contracts |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/fyllepo/qubic-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server