LQWD Gateway

io.github.lqwdtechPublished by GitHub account lqwdtechv3.0.0Updated Oct 24, 2026

Free Lightning faucet MCP — agents register, get an inbound channel, bootstrap an LDK node.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFinance

Overview

AI-generated overview

A remote MCP server that lets an AI agent register a free LQWD account, obtain an API key, and check its account and Lightning channel status.

What you can do
Register a new LQWD agent account and receive an API key, optionally with a one-time inbound Lightning channel grant when a node pubkey and node URI are supplied (lqwd_register). Check the account profile, including tier, status and registration date (lqwd_check_balance). Check the status of an inbound channel granted to the node, including state, funding txid and balances (lqwd_check_channel_status).
When to use it
Useful when an agent needs a free API key for the LQWD gateway or wants to bootstrap a Lightning node with an inbound channel grant, and to monitor that account and channel afterwards.
Requirements
A remote endpoint at api.lqwdclaw.bot over streamable HTTP. An API key is required for most tools, sent as the Authorization header in the form Bearer plus the key; the key comes from the lqwd_register tool, which needs no authentication. Registering a channel grant requires a Lightning node pubkey and node URI.
Before you install
Registration creates an account and issues a credential; the returned API key is a secret and should be kept private. Supplying a node pubkey and node URI ties a mainnet Lightning node to the registration, and the channel grant is described as one-time. The server is remote, so account and channel data are sent to a third party.

Installation

In SourceWeft

  1. Open LQWD Gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.lqwdtech%2Fgateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lqwd-gateway": {
      "type": "http",
      "url": "https://api.lqwdclaw.bot/v1/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

lqwd_check_balance

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).

Takes no parameters.

lqwd_check_channel_status

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 get a 'no active grant' response. 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).

Takes no parameters.

lqwd_register

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. To receive an inbound channel from LQWD, pass `pubkey` AND `node_uri` together.

Parametersnamerequiredpubkeynode_uri

Version history

1
  1. v3.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.