arcium-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOLANA_RPC_URL | No | Solana RPC endpoint | https://api.mainnet-beta.solana.com |
| ARCIUM_MCP_PORT | No | HTTP port (when transport=http) | 3000 |
| ARCIUM_RPS_PROGRAM | No | RPS MXE program ID | |
| ARCIUM_MCP_TRANSPORT | No | Transport mode: stdio or http | stdio |
| ARCIUM_CLUSTER_OFFSET | No | Cluster offset | 0 |
| ARCIUM_VOTING_PROGRAM | No | Voting MXE program ID | |
| ARCIUM_AUCTION_PROGRAM | No | Auction MXE program ID | |
| ARCIUM_COINFLIP_PROGRAM | No | Coinflip MXE program ID | |
| ARCIUM_WALLET_PRIVATE_KEY | No | Base58 or JSON array Solana keypair (none = read-only mode) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| arcium_list_mxesA | List all MXE (Multi-party computation eXecution Environments) on the Arcium network. Returns addresses, authorities, cluster assignments, and computation definitions. |
| arcium_get_mxe_infoB | Get detailed information about a specific MXE including authority, cluster, and computation definitions. |
| arcium_list_clustersA | List all computation clusters. Clusters are groups of ARX nodes that execute MPC computations together. |
| arcium_get_cluster_infoB | Get detailed info about a specific cluster including its nodes and capacity. |
| arcium_list_nodesB | List all ARX nodes in the Arcium network. ARX nodes process encrypted data. |
| arcium_get_node_infoA | Get detailed info about a specific ARX node including its encryption pubkey and cluster memberships. |
| arcium_network_statsA | Get aggregate network statistics: total MXEs, clusters, nodes. |
| arcium_generate_keypairA | Generate a new x25519 encryption keypair for Arcium. IMPORTANT: The private key is returned once — store it securely. |
| arcium_get_mxe_pubkeyB | Fetch the public encryption key of a specific MXE program for ECDH key exchange. |
| arcium_encrypt_valuesB | Encrypt numeric values using Arcium's RescueCipher via ECDH shared secret. Returns ciphertext ready for MPC computation. |
| arcium_decrypt_resultA | Decrypt an encrypted computation result using your private key and the result nonce. |
| arcium_get_comp_definitionA | Get details about a computation definition (circuit) including finalization authority and callback settings. |
| arcium_check_computationB | Check computation status by analyzing the Solana transaction signature. |
| arcium_await_finalizationA | Wait for an encrypted computation to finalize. Returns the finalization transaction signature. Requires wallet (ARCIUM_WALLET_PRIVATE_KEY env var). |
| arcium_list_mempoolB | List pending computations in an MXE program's mempool. Shows computations waiting to be processed by ARX nodes. |
| arcium_play_coinflipB | Play an encrypted coin flip. Your choice is encrypted and compared against MPC randomness. |
| arcium_play_rpsB | Play encrypted rock-paper-scissors. Moves are compared inside MPC — neither player sees the other's move. |
| arcium_sealed_bidA | Submit an encrypted sealed bid to an onchain auction. Bid stays hidden until close. |
| arcium_private_voteA | Cast an encrypted vote in a DAO governance proposal. Hidden until voting period ends. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Arcium Overview | What is Arcium and how confidential computing works |
| SDK Quick Start | How to use the Arcium TypeScript SDK |
| Computation Lifecycle | How encrypted computations flow through the network |
TDQS
Scored across 19 tools
Each tool targets a distinct resource or action: key generation, encryption/decryption, network info (clusters, nodes, MXEs), computation status, and specific applications (coinflip, RPS, vote, bid). No two tools have overlapping purposes; even similar-sounding tools like get vs list are clearly scoped to individual vs aggregate.
All tool names follow a consistent `arcium_verb_noun` pattern using snake_case. Verbs are informative (encrypt, decrypt, generate, get, list, play, await, check) and nouns clearly indicate the target. No mixed conventions or vague names.
19 tools is well-scoped for a platform offering key management, encryption/decryption, network queries, computation monitoring, and interactive MPC games. Each tool serves a clear purpose without redundancy, and the count feels complete for the advertised features.
The tool surface covers querying network state, encryption/decryption, and predefined games/voting, but lacks explicit tools to initiate custom computations or submit encrypted data for MPC processing. This gap means agents cannot perform the full lifecycle of a custom computation using the server alone.