wdk-wallet-rln-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RLN_NODE_URL | No | RLN daemon HTTP API URL | http://localhost:3001 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wdk_get_node_infoA | Get the RLN node identity and network summary: pubkey, number of channels, Lightning balance, connected peers. Call this first to confirm the node is reachable. |
| wdk_get_balancesA | Get current wallet balances: BTC on-chain (vanilla and colored UTXOs). For RGB asset balances use wdk_get_asset_balance with a specific asset_id. |
| wdk_get_asset_balanceA | Get the balance of a specific RGB asset (e.g. USDT, XAUT) by its asset_id. Returns settled, future, spendable, and off-chain amounts. |
| wdk_list_assetsA | List all RGB assets held by the node (NIA, UDA, CFA schemas). Returns asset IDs, names, tickers, and precision. |
| wdk_get_addressA | Get the node on-chain BTC address for receiving Bitcoin deposits. |
| wdk_create_rgb_invoiceA | Create an RGB invoice to receive an RGB asset (e.g. USDT from a KaleidoSwap). Pass the returned invoice string as receiver_address when calling kaleidoswap_place_order with receiver_address_format="RGB_INVOICE". |
| wdk_create_ln_invoiceB | Create a BOLT11 Lightning invoice to receive BTC via Lightning Network. |
| wdk_pay_invoiceA | Pay a BOLT11 Lightning invoice. Use this to send payment to a KaleidoSwap deposit_address after placing a swap order. |
| wdk_send_btcB | Send BTC on-chain to a Bitcoin address. |
| wdk_send_assetA | Send an RGB asset (e.g. USDT) on-chain to a recipient identified by their RGB recipient_id. Use this to fund a KaleidoSwap order whose deposit_address.format is "RGB_INVOICE" — pass the deposit_address.address as recipient_id. |
| wdk_list_channelsA | List all Lightning channels: capacity, local balance, usability status, and any RGB asset allocated to the channel. |
| wdk_open_channelB | Open a new Lightning channel to a peer. Optionally allocate an RGB asset to the channel for off-chain asset transfers. |
| wdk_list_paymentsA | List recent Lightning payments (sent and received). Useful for confirming that a swap deposit was sent successfully. |
| wdk_refresh_transfersA | Refresh pending RGB asset transfers. Call this after a swap is reported FILLED to update on-chain asset balances. |
| wdk_connect_peerA | Connect the RLN node to a Lightning peer. Required before requesting an LSPS1 channel from the KaleidoSwap LSP — call this first if the LSP is not already a connected peer. Format: "@:". |
| wdk_atomic_takerA | Step 2 of atomic swap: whitelist the incoming HTLC on the RLN node. Must be called with the swapstring from kaleidoswap_atomic_init BEFORE calling kaleidoswap_atomic_execute. This locks the HTLC on the node so it is ready to receive the atomic payment. |
| wdk_list_swapsA | List all atomic swaps on the RLN node, split by maker and taker side. Useful for monitoring active and historical atomic swap activity. |
| wdk_get_swapA | Get atomic swap status by payment_hash from the RLN node. Use after kaleidoswap_atomic_execute to confirm the node-side swap state. Optionally filter by taker=true to check taker-side swaps. |
| wdk_mpp_payA | Pay an MPP (Machine Payments Protocol) Lightning challenge using the RLN wallet. Pass the invoice from mpp_request_challenge. Returns a credential JSON string to pass directly to mpp_submit_credential. Also returns the payment_hash for auditing. Supports optional macaroon and challenge_id fields from the challenge for L402-compatible credential construction. |
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 19 tools
Each tool targets a specific operation with clear boundaries: atomic swap steps, connection management, invoice creation, balance queries (separate for BTC and RGB), node info, payment handling, channel operations, asset transfers. No overlapping purposes.
All tools start with 'wdk_' and mostly follow verb_noun pattern (e.g., wdk_create_ln_invoice, wdk_send_asset). Minor deviations like 'wdk_atomic_taker' (noun) and 'wdk_mpp_pay' (noun_verb) but overall consistent snake_case.
19 tools cover a broad scope (wallet, lightning, RGB assets, atomic swaps). Slightly above typical range but each tool serves a distinct purpose; no obvious bloat.
Core workflows are covered: connect, node info, balances, invoices, payments, channels, RGB assets, atomic swaps, on-chain sends. Minor gaps like channel closure or wallet backup, but nothing critical.