mcpbeat

LQWD Gateway MCP Server

io.github.lqwdtech/gateway
answering

LQWD Gateway is answering right now. Last checked 14 min ago. It exposes 3 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
731 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add gateway --transport http https://api.lqwdclaw.bot/v1/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "gateway": {
      "url": "https://api.lqwdclaw.bot/v1/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.gateway]
url = "https://api.lqwdclaw.bot/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "gateway": {
      "url": "https://api.lqwdclaw.bot/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "gateway": {
      "url": "https://api.lqwdclaw.bot/v1/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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

Endpoints

URLTransportStateLatencyChecked
https://api.lqwdclaw.bot/v1/mcp streamable-http answering 751 ms 14 min ago

LQWD Gateway — questions

Answers built from our own checks of this server.

What can LQWD Gateway do?
It exposes 3 tools, read directly from the server on our last check. Among them: lqwd_check_balance, lqwd_check_channel_status, lqwd_register. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is LQWD Gateway working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 731 ms. The bar chart above shows every period we have measured.
Is LQWD Gateway still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect LQWD Gateway?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does LQWD Gateway need an API key?
No. LQWD Gateway completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is LQWD Gateway?
It answers our handshake in 731 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.