# Lightning Enable MCP Server (oci · docker.io/refinedelement/lightning-enable-mcp:2.0.1)

AI agent Lightning payments: L402, invoices, wallets, API discovery, budgets, self-serve signup.

- Trust score: 47/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- nuget · `LightningEnable.Mcp`: 76/100, [markdown](https://verifymcp.io/servers/refined-element-lightning-enable-mcp/lightningenable-mcp.md), [page](https://verifymcp.io/servers/refined-element-lightning-enable-mcp/lightningenable-mcp)
- oci · `docker.io/refinedelement/lightning-enable-mcp:2.0.1`: 47/100 (this document), [markdown](https://verifymcp.io/servers/refined-element-lightning-enable-mcp/docker-io-refinedelement-lightning-enable-mcp-2-0-1.md), [page](https://verifymcp.io/servers/refined-element-lightning-enable-mcp/docker-io-refinedelement-lightning-enable-mcp-2-0-1)
- pypi · `lightning-enable-mcp`: 74/100, [markdown](https://verifymcp.io/servers/refined-element-lightning-enable-mcp/lightning-enable-mcp.md), [page](https://verifymcp.io/servers/refined-element-lightning-enable-mcp/lightning-enable-mcp)

## Channel facts

- Registry: `oci`
- Package: `docker.io/refinedelement/lightning-enable-mcp:2.0.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2146 tokens (~126/item across 17 items; 16 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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).
  - 99% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Lightning Enable MCP Server server?

Lightning Enable MCP Server runs locally as a container image, launched with docker run --rm -i docker.io/refinedelement/lightning-enable-mcp:2.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add refined-element-lightning-enable-mcp -- docker run --rm -i docker.io/refinedelement/lightning-enable-mcp:2.0.1
```

### Cursor

```json
{
  "mcpServers": {
    "refined-element-lightning-enable-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/refinedelement/lightning-enable-mcp:2.0.1"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "refined-element-lightning-enable-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/refinedelement/lightning-enable-mcp:2.0.1"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add refined-element-lightning-enable-mcp -- docker run --rm -i docker.io/refinedelement/lightning-enable-mcp:2.0.1
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "refined-element-lightning-enable-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "docker.io/refinedelement/lightning-enable-mcp:2.0.1"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  refined-element-lightning-enable-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "docker.io/refinedelement/lightning-enable-mcp:2.0.1"]
```

### Netclaw

```json
{
  "McpServers": {
    "refined-element-lightning-enable-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "docker.io/refinedelement/lightning-enable-mcp:2.0.1"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "refined-element-lightning-enable-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/refinedelement/lightning-enable-mcp:2.0.1"
      ]
    }
  }
}
```

## 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-09-20 (score 47, +1)

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

### 2026-09-18 (score 46, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-11 (score 43)

First indexed and scored.

## MCP tools (16)

### `setup_wallet` (~65 tokens)

Report the wallet this server pays from, or connect one. Call with no arguments first - it also returns the setup steps when no wallet is configured.

Input parameters:

- `nwc_connection_string` (string): NWC connection string (nostr+walletconnect://...). Omit to just report.

### `access_l402_resource` (~110 tokens)

Fetch a URL, automatically paying any L402 challenge and retrying. Returns the response plus what was paid.

Input parameters:

- `body` (string): Body for POST/PUT
- `confirmation_nonce` (string): Code the human reads off the server console (never returned to you). Omit to request one.
- `headers` (object): Extra headers
- `max_sats` (integer): Max sats to pay
- `method` (string)
- `url` (string, required): URL to fetch

### `pay_invoice` (~77 tokens)

Pay a BOLT11 Lightning invoice directly and get the preimage as proof.

Input parameters:

- `confirmation_nonce` (string): Code the human reads off the server console (never returned to you). Omit to request one.
- `invoice` (string, required): BOLT11 invoice to pay
- `max_sats` (integer): Max sats to pay

### `pay_l402_challenge` (~153 tokens)

Pay an L402 or MPP invoice yourself and get the authorization token. Omit macaroon for MPP; pass challenge_header for a draft-00 Payment challenge.

Input parameters:

- `challenge_header` (string): Raw WWW-Authenticate value of a 'Payment' challenge; draft-00 yields a single-use credential.
- `confirmation_nonce` (string): Code the human reads off the server console (never returned to you). Omit to request one.
- `invoice` (string): BOLT11 invoice. Optional if challenge_header carries one.
- `macaroon` (string|null): Base64 macaroon from the challenge. Omit for MPP.
- `max_sats` (integer): Max sats to pay

### `test_l402_payment` (~79 tokens)

Self-test the wallet by paying the public 1-sat L402 test endpoint end to end. A 'needs_confirmation' verdict means the server printed a code to its console; re-run with confirmation_nonce.

Input parameters:

- `confirmation_nonce` (string): Code the human reads off the server console (never returned to you). Omit to request one.

### `get_balance` (~30 tokens)

Get the connected wallet's balance in sats, plus all currency balances and wallet info where the wallet reports them.

### `budget` (~89 tokens)

View or tighten this session's spending limits. Tightening is one-way - an agent can lower its caps but never raise the operator's config limits.

Input parameters:

- `action` (string, required): status: read limits, tiers and session spend. tighten: lower the runtime sats caps.
- `per_request` (integer): tighten: max sats per request
- `per_session` (integer): tighten: max sats per session

### `receipts` (~97 tokens)

List payments this wallet made. The durable log persists across restarts and says how to revoke the wallet; the session list is in-memory only.

Input parameters:

- `limit` (integer): Max entries (durable clamps to 1-200)
- `since` (string): session: ISO timestamp to filter from
- `source` (string, required): durable: the append-only log at ~/.lightning-enable/receipts.jsonl. session: payments since startup.

### `create_invoice` (~55 tokens)

Create a BOLT11 Lightning invoice to receive a payment.

Input parameters:

- `amount_sats` (integer, required): Satoshis to receive
- `expiry_secs` (integer): Expiry in seconds
- `memo` (string): Invoice memo

### `check_invoice_status` (~33 tokens)

Check whether an invoice from create_invoice has been paid.

Input parameters:

- `invoice_id` (string, required): Invoice ID from create_invoice

### `verify_confirmation_code` (~59 tokens)

Check whether a payment confirmation code is still valid and what it authorizes. Verification ONLY - it never pays; to pay, re-call the payment tool with confirmation_nonce.

Input parameters:

- `nonce` (string, required): The 6-character code from the payment request

### `discover_api` (~103 tokens)

Discover L402 APIs: search the registry with query/category, or fetch one API's manifest with url.

Input parameters:

- `budget_aware` (boolean): Annotate endpoints with affordable call counts
- `category` (string): Registry category filter, e.g. 'ai'
- `query` (string): Registry keyword search, e.g. 'weather'
- `url` (string): Base URL of an L402 API, or a manifest URL. Omit to search the registry.

### `create_lightning_enable_account` (~106 tokens)

Self-bootstrapping signup: pay a ~100-sat activation fee for a Lightning Enable merchant API key. Needs only a wallet; the key is saved to ~/.lightning-enable/config.json.

Input parameters:

- `confirmation_nonce` (string): Code the human reads off the server console (never returned to you). Omit to request one.
- `email` (string, required): Email to register
- `max_sats` (integer): Max sats for the ~100-sat fee

### `wallet_ops` (~179 tokens)

Wallet operations beyond invoices: BTC price, currency exchange, on-chain sends. Strike only (send_onchain also works on LND).

Input parameters:

- `action` (string, required): price: BTC/USD. exchange: convert currency in your wallet. send_onchain: irreversible - ALWAYS needs confirmation_nonce, so the first call only prints a code to the server console.
- `address` (string): send_onchain: destination address
- `amount` (number): exchange: amount in source_currency
- `amount_sats` (integer): send_onchain: satoshis to send
- `confirmation_nonce` (string): Code the human reads off the server console (never returned to you). Omit to request one.
- `source_currency` (string): exchange: from, USD or BTC
- `target_currency` (string): exchange: to, BTC or USD

### `l402_producer` (~457 tokens)

Sell access with L402: set up the seller account, monetize an API, mint challenges and verify payer tokens. Requires LIGHTNING_ENABLE_API_KEY.

Input parameters:

- `action` (string, required): create: mint an invoice + macaroon challenge. verify: check a payer's token before granting access. configure_receive: point payouts at your own NWC wallet. status: plan, wallet, checklist and recent…
- `categories` (array): publish: registry categories
- `challenge_status` (string): list_challenges: filter; omit for all
- `default_price_sats` (integer): create_proxy: default price per request
- `description` (string): create: invoice text; create_proxy: what the API does
- `endpoint_id` (string): add_endpoint: stable id for the route
- `http_method` (string): add_endpoint: GET, POST, ... (default GET)
- `limit` (integer): status/list_challenges: max rows
- `macaroon` (string): verify: base64 macaroon
- `name` (string): create_proxy: service name
- `nwc_connection_string` (string): configure_receive: nostr+walletconnect:// string; omit to reuse this server's own NWC wallet
- `offset` (integer): list_challenges: rows to skip
- `path` (string): add_endpoint: route path like /forecast
- `preimage` (string): verify: hex preimage
- `price_sats` (integer): create/add_endpoint: price in sats
- `proxy_id` (string): add_endpoint/publish: id from create_proxy
- `resource` (string): create: URL or name you are charging for
- `service_description` (string): publish: registry description
- `service_name` (string): publish: rename the listed service
- `summary` (string): add_endpoint: one-line summary
- `target_base_url` (string): create_proxy: https:// base URL to monetize

### `agent_services` (~412 tokens)

Agent Service Agreements over Nostr: discover, request, settle, publish and review agent services. Requires LIGHTNING_ENABLE_API_KEY.

Input parameters:

- `action` (string, required): discover: search listings. request: ask for a service. settle: PAY an agreement's L402 endpoint. publish: list your service. unpublish: remove it. attest: review a finished agreement. reputation: rea…
- `agreement_id` (string): settle/attest: agreement id
- `body` (string): settle: request body
- `budget_sats` (integer): request: max sats
- `capability_event_id` (string): request: capability event id
- `categories` (array): publish: categories
- `category` (string): discover: category
- `confirmation_nonce` (string): Code the human reads off the server console (never returned to you). Omit to request one.
- `content` (string): publish: service text; attest: review text
- `hashtags` (array): discover/publish: hashtags
- `l402_endpoint` (string): settle/publish: L402 endpoint
- `limit` (integer): discover/reputation: max results
- `max_sats` (integer): settle: max sats
- `method` (string): settle: HTTP method
- `parameters` (string): request: extra params, JSON string
- `price_sats` (integer): publish: price per request
- `proof` (string): attest: preimage hash
- `pubkey` (string): reputation: agent pubkey
- `query` (string): discover: keyword
- `rating` (integer): attest: 1-5
- `reason` (string): unpublish: reason
- `service_id` (string): publish/unpublish: listing d-tag
- `subject_pubkey` (string): attest: agent being reviewed
- `target_url` (string): publish: API URL to wrap in a new L402 proxy

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/refined-element-lightning-enable-mcp/docker-io-refinedelement-lightning-enable-mcp-2-0-1#diagnostics

## Score history

- 2026-09-20: 47
- 2026-09-19: 46
- 2026-09-18: 46
- 2026-09-17: 43
- 2026-09-16: 43
- 2026-09-15: 43
- 2026-09-14: 43
- 2026-09-13: 43
- 2026-09-12: 43
- 2026-09-11: 43

## Common questions

### What is the Lightning Enable MCP Server server?

Lightning Enable MCP Server is listed in the public MCP registry as io.github.refined-element/lightning-enable-mcp. AI agent Lightning payments: L402, invoices, wallets, API discovery, budgets, self-serve signup. This page covers its container image (docker.io/refinedelement/lightning-enable-mcp:2.0.1).

### Is the Lightning Enable MCP Server server safe to use?

Lightning Enable MCP Server scores 47 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Lightning Enable MCP Server server expose?

Lightning Enable MCP Server exposes 16 tools: setup_wallet, access_l402_resource, pay_invoice, pay_l402_challenge, test_l402_payment, and 11 more. Their descriptions and schemas cost roughly 2,104 tokens of context every time the server is loaded.

### Is the Lightning Enable MCP Server server still maintained?

Lightning Enable MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Lightning Enable MCP Server server under?

Lightning Enable MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/refined-element/lightning-enable-mcp
- Website: https://docs.lightningenable.com/products/agentic-commerce/mcp-complete-guide
- Changelog RSS feed: https://verifymcp.io/servers/refined-element-lightning-enable-mcp/docker-io-refinedelement-lightning-enable-mcp-2-0-1.xml
- Changelog JSON feed: https://verifymcp.io/servers/refined-element-lightning-enable-mcp/docker-io-refinedelement-lightning-enable-mcp-2-0-1.json
- HTML version of this page: https://verifymcp.io/servers/refined-element-lightning-enable-mcp/docker-io-refinedelement-lightning-enable-mcp-2-0-1