chainwhisper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHAINWHISPER_COTI_RPC_URL | No | Custom COTI Mainnet RPC URL. | |
| CHAINWHISPER_PAIRING_FILE | No | Custom pairing file path. | |
| CHAINWHISPER_PAIRING_SECRET | No | Pairing secret, if not auto-generated. | |
| CHAINWHISPER_SIGNER_AES_KEY | No | The wallet-specific 128-bit COTI AES key returned by official account onboarding/recovery. | |
| CHAINWHISPER_STATE_DIRECTORY | No | Custom state directory path. | |
| CHAINWHISPER_SIGNER_CONFIG_FILE | No | Path to a local JSON configuration file containing signer credentials. Keep outside repository and restrict permissions. | |
| CHAINWHISPER_SIGNER_PRIVATE_KEY | No | The wallet private key for the signer. Required for full signing capabilities. | |
| CHAINWHISPER_SIGNER_EXPIRY_SKEW_MS | No | Expiry skew in milliseconds. | |
| CHAINWHISPER_SIGNER_EXPECTED_WALLET | No | Expected wallet address to verify against. | |
| CHAINWHISPER_SIGNER_STATE_DIRECTORY | No | Custom signer state directory. | |
| CHAINWHISPER_SIGNER_VAULT_PASSPHRASE | No | Passphrase for the encrypted signer vault. | |
| CHAINWHISPER_SIGNER_CONFIRMATION_CHANNEL | No | Confirmation channel: 'mcp' or 'local-web' (default). | local-web |
| CHAINWHISPER_SIGNER_CONFIRMATION_TIMEOUT_MS | No | Timeout in milliseconds for confirmation form. |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chainwhisper_order_typesA | List every canonical ChainWhisper order type, its access model, term and liquidity visibility, fill style, and whether the deployed route is currently safe to execute. Call this before asking the user to choose an orderType. |
| chainwhisper_statusA | Check the keyless ChainWhisper planner, COTI Mainnet registry snapshot, and write compatibility. This tool never connects a wallet. |
| chainwhisper_list_ordersB | List up to 20 safe ChainWhisper order summaries. Hidden amounts and access secrets are never returned. |
| chainwhisper_get_orderA | Read one ChainWhisper order using its verified contract-local identity or opaque trusted handle. |
| chainwhisper_compare_price_referencesA | Compare ChainWhisper and compatible market price references in quote-per-base orientation. Amount is optional. A best-execution ranking is returned only when an amount is supplied and executable liquidity was actually checked. |
| chainwhisper_privacy_bridge_statusA | Read and verify one allowlisted Privacy Portal bridge pair, live pause/deposit policy, wallet blacklist status, limits, and an optional exact amount fee quote. This is keyless and read-only. |
| chainwhisper_prepare_privacy_bridgeA | Prepare an exact shield (public-to-private) or unshield (private-to-public) transaction for one of the eight current allowlisted Privacy Portal pairs. The amount is necessarily public in the deployed bridge calldata. Exact approvals and the quoted portal fee are bound into the paired envelope; this planner never signs or broadcasts. |
| chainwhisper_prepare_create_tradeA | Validate and prepare an audited ChainWhisper one-off OTC order. Select an explicit orderType so public, unlisted, direct-recipient, and private-liquidity routes cannot be confused. Hidden amounts stay in the local signer. This tool never signs or submits. |
| chainwhisper_prepare_create_recurringA | Validate and prepare a public or fixed-recipient recurring ChainWhisper order with an explicit orderType. Visible and private-token inventory routes are supported. Prices use quote per base. |
| chainwhisper_prepare_fillA | Prepare a fill for an existing trusted ChainWhisper order. Public visible amounts remain planner input. Only confidential hidden-liquidity or Direct private-token inputs are collected inside the signer. |
| chainwhisper_prepare_counterB | Prepare a canonical Direct counterorder against a trusted one-off order. Counter terms are recipient-bound to the original maker; confidential token amounts stay in the local signer. Existing recipient-bound Standard orders use an explicitly labeled legacy compatibility route and cannot be confused with newly created Direct orders. |
| chainwhisper_prepare_editC | Prepare an edit to a trusted owned ChainWhisper order. Only allowlisted order terms are accepted. |
| chainwhisper_prepare_order_updateC | Prepare an allowlisted lifecycle update for a trusted ChainWhisper order. Administrative and arbitrary contract actions are unavailable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| chainwhisper_compare_prices | A short workflow for comparing price references without making an unsupported liquidity claim. |
| chainwhisper_prepare_order | Validate an order request and produce a paired action envelope without signing or broadcasting. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| chainwhisper-coti-mainnet-runtime | Repository-owned addresses, bytecode hashes, selectors, and verified asset references used by the keyless planner. |
| chainwhisper-security-boundary | The planning MCP is keyless. Only the paired local signer may materialize private inputs or broadcast. |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: order types, status, listing, reading, price comparison, bridge status, bridge preparation, and various order preparation actions (create trade, create recurring, fill, counter, edit, update). No overlapping functionality.
All tools follow a consistent snake_case pattern with the prefix 'chainwhisper_' followed by a verb_noun structure (e.g., list_orders, get_order, prepare_create_trade). The verb 'prepare' is used uniformly for transaction-preparation tools.
With 13 tools, the server covers a complex domain (orders, bridges, price references, lifecycle) without being overwhelming. Each tool serves a necessary function, and the count is well-scoped for the intended functionality.
The tool set covers essential operations: understanding order types, status checks, listing, reading, creating (one-off and recurring), filling, countering, editing, and lifecycle updates. Missing explicit deletion or cancellation, though lifecycle update may cover it. Minor gap, but otherwise comprehensive.