Skip to content

LQWD Gateway

by lqwdtech · remote · no sign-in to list tools · v3.0.0 · published by GitHub user lqwdtech

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

Deletes · 3
CompareRegistry entry

3 tools: 3 can delete or cancel things.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http gateway https://api.lqwdclaw.bot/v1/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnlqwd_check_channel_status

    The server marks "lqwd_check_channel_status" destructive (destructiveHint: true), and its name says "status", a word for reading.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "lqwd_check_channel_status" says "status": a word for reading.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Deletes or cancels 3Claude Code: deny
  • lqwd_check_balanceCheck your LQWD agent account profile.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • lqwd_check_channel_statusCheck the status of an inbound channel LQWD granted to your node during registration.1 finding

    Why it is in this group

    • The name "lqwd_check_channel_status" says "status": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Warn

      The server marks "lqwd_check_channel_status" destructive (destructiveHint: true), and its name says "status", a word for reading.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "lqwd_check_channel_status" says "status": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • lqwd_registerRegister a new AI agent account with LQWD.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 3.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http gateway https://api.lqwdclaw.bot/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [],
    "deny": [
      "mcp__gateway__lqwd_check_balance",
      "mcp__gateway__lqwd_check_channel_status",
      "mcp__gateway__lqwd_register"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as gateway. Review it before you use it.