# LQWD Gateway (remote · api.lqwdclaw.bot)

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

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.lqwdclaw.bot`: 66/100 (this document), [markdown](https://verifymcp.io/servers/lqwdtech-gateway/v1-mcp.md), [page](https://verifymcp.io/servers/lqwdtech-gateway/v1-mcp)

## Channel facts

- Endpoint: `https://api.lqwdclaw.bot/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (lqwd_check_balance).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 444 tokens (~148/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.lqwdtech-gateway]
url = "https://api.lqwdclaw.bot/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lqwdtech-gateway": {
      "type": "remote",
      "url": "https://api.lqwdclaw.bot/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lqwdtech-gateway --url https://api.lqwdclaw.bot/v1/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lqwdtech-gateway:
    url: "https://api.lqwdclaw.bot/v1/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (3)

### `lqwd_check_balance` (~77 tokens)

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` (~123 tokens)

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` (~244 tokens)

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.

Input parameters:

- `name` (string, required): Agent name (1-100 characters). Choose a descriptive name for your agent.
- `node_uri` (string): Optional. Your node's public URI in the form `pubkey@host:port` (port 9735 must be publicly reachable). Required alongside pubkey. The response will include `channel_granted` and `next_steps.channel_…
- `pubkey` (string): Optional. Your LND node's public key (66-char hex string). When provided alongside node_uri, LQWD opens a one-time inbound channel to your node as part of the tier-1 faucet grant. Omit if you don't r…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lqwdtech-gateway/v1-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 64
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://api.lqwdclaw.bot/v1/mcp
- Repository: https://github.com/lqwdtech/lqwdclawnode
- Changelog RSS feed: https://verifymcp.io/servers/lqwdtech-gateway/v1-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/lqwdtech-gateway/v1-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/lqwdtech-gateway/v1-mcp