LQWD Gateway MCP server
io.github.lqwdtech/gatewaylqwdtechstreamable-httpv3.0.0Scanned
Free Lightning faucet MCP — agents register, get an inbound channel, bootstrap an LDK node.
3 tools: 3 can delete or cancel things.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the LQWD Gateway MCP server can do
The LQWD Gateway MCP server is published by the GitHub account lqwdtech. It has 3 tools. It can delete or cancel things (3 tools: lqwd_check_balance, lqwd_check_channel_status and lqwd_register). None of its tools only reads.
3 tools bring in text other people can write (lqwd_check_balance, lqwd_check_channel_status and lqwd_register).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 3.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Deletes or cancels 3Claude Code: deny
lqwd_check_balanceCheck your LQWD agent account profile.Reads text others writeNo 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).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads text others write1 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).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "lqwd_check_channel_status" destructive (destructiveHint: true), and its name says "status", a word for reading.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "lqwd_check_channel_status" says "status": a word for reading.
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.Reads text others writeNo 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).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:07 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.lqwdclaw.bot/v1/mcp: tools/list returned 3 tools to an anonymous client, including lqwd_check_balance (destructive), lqwd_check_channel_status (destructive), lqwd_register (destructive)
Findings
Matches of fixed checks, with the text they matched.
The server marks "lqwd_check_channel_status" destructive (destructiveHint: true), and its name says "status", a word for reading.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":true}; The name "lqwd_check_channel_status" says "status": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http gateway https://api.lqwdclaw.bot/v1/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gateway. Review it before you use it.
Capability tags behind 3 rules
- mcp__gateway__lqwd_check_balance untrusted-input
- mcp__gateway__lqwd_check_channel_status untrusted-input
- mcp__gateway__lqwd_register untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.lqwdtech/gateway/verify?hash=b9cc3118c2253ab953abafd770338ac75a377f22fc77a76bd93d6e0cff18aca0" | jq -e '.changed == false'Pinned hash b9cc3118c225, from Nov 20, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.lqwdtech/gateway/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.lqwdtech/gateway)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:38 UTC.
LQWD Gateway MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the LQWD Gateway MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the LQWD Gateway MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: lqwd_check_balance, lqwd_check_channel_status and lqwd_register.
Can the LQWD Gateway MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the LQWD Gateway MCP server have?
- 3 tools: 3 destructive. lqwd_check_balance, lqwd_check_channel_status and lqwd_register.
Does the LQWD Gateway MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the LQWD Gateway MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the LQWD Gateway MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.