LQWD Gateway is a remote MCP server that gives an AI agent 3 tools, among them lqwd_check_balance, lqwd_check_channel_status, lqwd_register. It answers at https://api.lqwdclaw.bot/v1/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
Free Lightning faucet MCP — agents register, get an inbound channel, bootstrap an LDK node.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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_ |
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; |
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 — thi Inputs: name, node_uri, pubkey |
Every block below points at https://api.lqwdclaw.bot/v1/mcp. Pick your client and copy.
claude mcp add --transport http lqwd-gateway https://api.lqwdclaw.bot/v1/mcp
{
"mcpServers": {
"lqwd-gateway": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.lqwdclaw.bot/v1/mcp"]
}
}
}{
"mcpServers": {
"lqwd-gateway": {
"url": "https://api.lqwdclaw.bot/v1/mcp"
}
}
}{
"servers": {
"lqwd-gateway": {
"type": "http",
"url": "https://api.lqwdclaw.bot/v1/mcp"
}
}
}{
"context_servers": {
"lqwd-gateway": {
"url": "https://api.lqwdclaw.bot/v1/mcp"
}
}
}{
"mcpServers": {
"lqwd-gateway": {
"serverUrl": "https://api.lqwdclaw.bot/v1/mcp"
}
}
}{
"mcpServers": {
"lqwd-gateway": {
"url": "https://api.lqwdclaw.bot/v1/mcp"
}
}
}name: LQWD Gateway
version: 0.0.1
schema: v1
mcpServers:
- name: LQWD Gateway
type: streamable-http
url: https://api.lqwdclaw.bot/v1/mcp{
"mcpServers": {
"lqwd-gateway": {
"httpUrl": "https://api.lqwdclaw.bot/v1/mcp"
}
}
}{
"mcpServers": {
"lqwd-gateway": {
"type": "http",
"url": "https://api.lqwdclaw.bot/v1/mcp"
}
}
}{
"mcpServers": {
"lqwd-gateway": {
"url": "https://api.lqwdclaw.bot/v1/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.lqwdclaw.bot%2Fv1%2Fmcp&type=streamable_http&id=lqwd-gateway&name=LQWD%20Gateway
It answered our last check on 22 October 2026 in 659 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 15 September 2026: lqwd_check_balance, lqwd_check_channel_status, lqwd_register.
It answered our last check on 22 October 2026 in 659 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.lqwdclaw.bot/v1/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.lqwdtech. Endpoint host: api.lqwdclaw.bot. ARD identifier: urn:air:io.github.lqwdtech:mcp:gateway.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.