Skip to main content
Glama
lnfi-network

RGB Lightning Network MCP Server

by lnfi-network

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RGB_API_KEYNoOptional: RGB api key Or /path/rgbapi.key
RGB_API_BASE_URLNoRGB API server URLhttp://localhost:3000

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
rgb_get_node_infoB

Get RGB node information including ID, version, and network status

rgb_get_node_statusB

Get RGB node status and uptime information

rgb_list_assetsB

List all RGB assets available in the node

rgb_get_asset_balanceC

Get balance for a specific RGB asset

rgb_send_assetsC

Send RGB assets to recipients

rgb_get_asset_metadataC

Get metadata for a specific RGB asset

rgb_generate_addressB

Generate a new on-chain address

rgb_list_transactionsB

List on-chain transactions

rgb_get_network_infoB

Get network information from the RGB node

rgb_send_bitcoinC

Send Bitcoin to an address

rgb_create_lightning_invoiceC

Create a Lightning Network invoice

rgb_pay_lightning_invoiceC

Pay a Lightning Network invoice

rgb_list_lightning_channelsB

List Lightning Network channels

rgb_list_swapsC

List available swaps

rgb_create_swapC

Create a new asset swap

rgb_sign_messageC

Sign a message with the RGB node

rgb_check_indexer_urlC

Check if an indexer URL is valid

rgb_decode_lightning_invoiceC

Decode an RGB Lightning invoice

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 18 tools

Disambiguation4/5

Most tools have clearly distinct purposes, such as creating invoices vs. paying them, or getting asset metadata vs. listing assets. However, rgb_get_node_info and rgb_get_node_status could be confused as both relate to node status, though their descriptions differentiate them slightly (info includes ID/version, status focuses on uptime).

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with the 'rgb_' prefix, such as rgb_create_lightning_invoice and rgb_list_assets. The naming is uniform across all tools, using snake_case and clear action-object pairs, making it predictable and easy to understand.

Tool Count4/5

With 18 tools, the count is slightly high but reasonable for a server covering RGB assets, Lightning Network, and swaps. It provides comprehensive coverage without being overwhelming, though it borders on the heavy side for typical MCP scopes.

Completeness5/5

The tool set offers complete coverage for the RGB and Lightning Network domain, including asset management (create, send, balance, metadata), network operations (invoices, channels, payments), and swaps. There are no obvious gaps; it supports full lifecycle operations from creation to transactions.

Maintenance

ActivityInactive
ResponsivenessNo issues