LQWD Gateway

lqwdtech/lqwdclawnode

This is a Lightning Network faucet that helps AI agents bootstrap their own LDK nodes. It handles the cold start problem: agents register through the MCP interface, receive an inbound channel with liquidity, and get everything they need to start transacting on Lightning. You'd reach for this when your agent needs to accept Lightning payments but doesn't have existing channels or inbound capacity. The streamable HTTP transport means it works with Claude and other MCP clients out of the box. Think of it as training wheels for agents learning to handle real bitcoin micropayments without requiring manual channel management or upfront capital.

tools: 3
auth: Secret needed
transport: HTTP
last updated: May 21, 2026

View on GitHub

Install

From registry metadata

$ npx add-mcp https://api.lqwdclaw.bot/v1/mcp --name gateway --header 'Authorization: Bearer ${API_TOKEN}'

Run in your terminal. add-mcp asks which agents to add it to, then asks for each value it needs. Add -g to install it for every project.

Review the command, arguments and environment values before installing. MCP servers run with your local permissions.

Other ways

Claude Code

$ claude mcp add --transport http gateway https://api.lqwdclaw.bot/v1/mcp --header 'Authorization: YOUR_AUTHORIZATION'

Run in your terminal. Add --scope user to make it available in every project.

Tools

Verified live · 3 tools

Verified live against the running server on Nov 6, 2026.

lqwd_check_balanceCheck your LQWD agent account profile. Returns your account tier, status, and registration date. Always free. Authenticate by sending the HTTP header `Authorization: Bearer <your_api_key>` on MCP requests (where <your_api_key> is the `lqwd_...` key returned by lqwd_register).

Check your LQWD agent account profile. Returns your account tier, status, and registration date. Always free. Authenticate by sending the HTTP header `Authorization: Bearer <your_api_key>` on MCP requests (where <your_api_key> is the `lqwd_...` key returned by lqwd_register).

No parameters. Call it with no arguments.

lqwd_check_channel_statusCheck the status of an inbound channel LQWD granted to your node during registration. Returns the current state (pending, active, failed), funding txid (when confirmed), and balances. Only meaningful if you registered with pubkey+node_uri; agents without a channel grant will g...

Check the status of an inbound channel LQWD granted to your node during registration. Returns the current state (pending, active, failed), funding txid (when confirmed), and balances. Only meaningful if you registered with pubkey+node_uri; agents without a channel grant will g...

No parameters. Call it with no arguments.

lqwd_registerRegister a new AI agent account with LQWD. Returns an API key and, when you supply a Lightning node's pubkey + node_uri, a one-time inbound channel on mainnet as part of the tier-1 faucet grant. Always free; no authentication required — this tool is how you GET your API key. T...3 params

Register a new AI agent account with LQWD. Returns an API key and, when you supply a Lightning node's pubkey + node_uri, a one-time inbound channel on mainnet as part of the tier-1 faucet grant. Always free; no authentication required — this tool is how you GET your API key. T...

Parameters* required

name*string

Agent name (1-100 characters). Choose a descriptive name for your agent.

node_uristring

Optional. Your node's public URI in the form `pubkey@host:port` (port 9735 must be publicly reachable). Required alongside pubkey. The response will include `channel_granted` and `next_steps.channe...

pubkeystring

Optional. Your LND node's public key (66-char hex string). When provided alongside node_uri, LQWD opens a one-time inbound channel to your node as part of the tier-1 faucet grant. Omit if you don't...

Readme

Details

Repository: github.com/lqwdtech/lqwdclawnode
Transport: HTTP
Auth: Required
Registry: MCP registry, active
Tools verified: Nov 6, 2026