keygenix-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEYGENIX_ORG_CODE | Yes | Your organization code | |
| KEYGENIX_WALLET_CODE | Yes | Your wallet code | |
| KEYGENIX_API_PRIV_KEY | Yes | Your API auth private key hex | |
| KEYGENIX_AUTH_PRIV_KEY | Yes | Your authkey private key hex |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| keygenA | Generate a new secp256k1 keypair locally (no network call). Use this to create API Auth keypairs or AuthKey keypairs before registering with Keygenix. |
| list_keysC | List all keys in the wallet. |
| get_keyC | Get details of a specific key by keyCode. |
| update_keyC | Update a key's name or remark. |
| get_public_keyA | Get the derived public key for a key. For mnemonic keys, provide curve/path/deriveType. For private/secret keys, omit all deriving params. |
| create_keyB | Create a new key in the TEE. Supports mnemonic (HD wallet), private key, or secret key types. curve is required for private (secp256k1 or ed25519) and secret (ed25519 only) key types. |
| export_keyA | Export a key from TEE. The key material is returned encrypted with your ephemeral public key (ECIES). Generates a local keypair, sends the public key to the server, receives encrypted key, decrypts locally. |
| import_keyA | Import an existing key (mnemonic or private key) into Keygenix TEE. The key material is encrypted with ECIES before leaving the local machine — it is never transmitted in plaintext. Provide either 'mnemonic' (12/24 words) or 'privateKey' (hex), not both. |
| list_addressesB | List all derived addresses for a key. |
| create_addressA | Derive a new address from a key for a specific chain. Idempotent — returns the existing address if already derived for the same path. |
| sign_transactionB | Sign a blockchain transaction using a TEE-stored key. Supports EVM (RLP hex), SOL (base58/base64/hex), SUI, and other chains. keyCode is always required. Optionally provide address to skip HD derivation. |
| sign_messageA | Sign an arbitrary message (hex-encoded sha256 hash) using a TEE-stored key. keyCode is always required. Optionally provide address to skip HD derivation. |
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 12 tools
Most tools target a distinct action (import/export/sign/list/get/update), but a few boundaries require careful reading: keygen (local keypair generation) vs create_key (TEE-stored key), and export_key vs get_public_key both retrieve key material. The descriptions do clarify the distinction (local vs TEE, encrypted export vs derived public key), so misselection is unlikely but possible.
Nearly all tools follow a clean verb_noun snake_case pattern (export_key, import_key, create_address, sign_transaction, list_keys, get_key, update_key, create_key). The lone outlier is 'keygen', which drops the verb_noun convention and slightly breaks the pattern.
12 tools is well-scoped for a key management and signing server. Each tool covers a distinct lifecycle stage (generate, import, export, derive addresses, sign, CRUD) with no redundant filler.
Key lifecycle covers create, import, export, list, get, and update, plus address derivation and signing, but there is no delete_key or address removal operation, leaving a notable gap. Agents can create and manage keys but cannot clean up or revoke them.