Lightning Enable MCP Server
OCI · DOCKER.IO/REFINEDELEMENT/LIGHTNING-ENABLE-MCP · 3 COMPONENTS
AI agent Lightning payments: L402, invoices, wallets, API discovery, budgets, self-serve signup.
Last scanned (16 minutes ago)
Scores higher than 86% of OCI servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2412 tokens (~126/item across 19 items; 18 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Package version: 2.1.1 → 2.2.0 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +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.
- 22 Oct 26 +1
- Package version: 2.1.0 → 2.1.1 functional
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/docker.io/refinedelement/lightning-enable-mcp@2.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
access_l402_resource ~135
Fetch a URL with GET or HEAD, automatically paying any L402 challenge and retrying. Read-only: other HTTP methods are refused. Returns the response plus what was paid.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Optional request body (rarely needed) |
| 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 | – | GET or HEAD only (paid HTTP is read-only) |
| url | string | yes | URL to fetch |
No output schema declared.
No examples provided.
agent_services ~422
Agent Service Agreements over Nostr: discover, request, settle, publish and review agent services. Requires LIGHTNING_ENABLE_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | discover: search listings. request: ask for a service. settle: PAY an agreement's L402 endpoint. publish: list your service once; to change it, unpublish then publish. unpublish: remove it. attest: r… |
| 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 |
No output schema declared.
No examples provided.
budget ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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 |
No output schema declared.
No examples provided.
check_invoice_status ~33
Check whether an invoice from create_invoice has been paid.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | Invoice ID from create_invoice |
No output schema declared.
No examples provided.
create_invoice ~55
Create a BOLT11 Lightning invoice to receive a payment.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | integer | yes | Satoshis to receive |
| expiry_secs | integer | – | Expiry in seconds |
| memo | string | – | Invoice memo |
No output schema declared.
No examples provided.
create_lightning_enable_account ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_nonce | string | – | Code the human reads off the server console (never returned to you). Omit to request one. |
| string | yes | Email to register | |
| max_sats | integer | – | Max sats for the ~100-sat fee |
No output schema declared.
No examples provided.
discover_api ~103
Discover L402 APIs: search the registry with query/category, or fetch one API's manifest with url.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
docs ~85
Search or read the Lightning Enable docs. search: query -> sections. read: path, optional section -> text.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| limit | integer | – | default 5, max 20 |
| path | string | – | e.g. /nwc-setup/account-setup |
| query | string | – | – |
| section | string | – | heading text |
No output schema declared.
No examples provided.
get_balance ~30
Get the connected wallet's balance in sats, plus all currency balances and wallet info where the wallet reports them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
l402_producer ~457
Sell access with L402: set up the seller account, monetize an API, mint challenges and verify payer tokens. Requires LIGHTNING_ENABLE_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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 |
No output schema declared.
No examples provided.
pay_invoice ~77
Pay a BOLT11 Lightning invoice directly and get the preimage as proof.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_nonce | string | – | Code the human reads off the server console (never returned to you). Omit to request one. |
| invoice | string | yes | BOLT11 invoice to pay |
| max_sats | integer | – | Max sats to pay |
No output schema declared.
No examples provided.
pay_l402_challenge ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
receipts ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max entries (durable clamps to 1-200) |
| since | string | – | session: ISO timestamp to filter from |
| source | string | yes | durable: the append-only log at ~/.lightning-enable/receipts.jsonl. session: payments since startup. |
No output schema declared.
No examples provided.
renew_lightning_enable_subscription ~83
Pay the L402 invoice that buys or extends 30 days of Lightning Enable Agentic Commerce for the configured API key. Needs a preimage-capable wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_nonce | string | – | Code the human reads off the server console (never returned to you). Omit to request one. |
| max_sats | integer | – | Max sats to pay |
No output schema declared.
No examples provided.
setup_wallet ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nwc_connection_string | string | – | NWC connection string (nostr+walletconnect://...). Omit to just report. |
No output schema declared.
No examples provided.
test_l402_payment ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_nonce | string | – | Code the human reads off the server console (never returned to you). Omit to request one. |
No output schema declared.
No examples provided.
verify_confirmation_code ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | The 6-character code from the payment request |
No output schema declared.
No examples provided.
wallet_ops ~242
Wallet operations beyond invoices: BTC price, currency exchange, on-chain sends. Strike only (send_onchain also works on LND).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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. |
| intent_id | string | – | send_onchain: optional idempotency scope. Omit for normal use. Supply a NEW value only when you intentionally need to pay the same address the same amount again; a repeat with the same address, amoun… |
| source_currency | string | – | exchange: from, USD or BTC |
| target_currency | string | – | exchange: to, BTC or USD |
No output schema declared.
No examples provided.
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 -e STRIKE_API_KEY -e NWC_CONNECTION_STRING -e LND_REST_HOST -e LND_MACAROON_HEX -e OPENNODE_API_KEY -e LIGHTNING_ENABLE_API_KEY -e LIGHTNING_ENABLE_TOOL_PROFILE -e AGENT_RELAY_URL docker.io/refinedelement/lightning-enable-mcp:2.2.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/refinedelement/lightning-enable-mcp
claude mcp add refined-element-lightning-enable-mcp -- docker run --rm -i -e STRIKE_API_KEY -e NWC_CONNECTION_STRING -e LND_REST_HOST -e LND_MACAROON_HEX -e OPENNODE_API_KEY -e LIGHTNING_ENABLE_API_KEY -e LIGHTNING_ENABLE_TOOL_PROFILE -e AGENT_RELAY_URL docker.io/refinedelement/lightning-enable-mcp:2.2.0
This image reads STRIKE_API_KEY, NWC_CONNECTION_STRING, LND_REST_HOST, LND_MACAROON_HEX, OPENNODE_API_KEY, LIGHTNING_ENABLE_API_KEY, LIGHTNING_ENABLE_TOOL_PROFILE and AGENT_RELAY_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
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).
Is the Lightning Enable MCP Server server safe to use?
Lightning Enable MCP Server scores 52 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 18 tools: setup_wallet, access_l402_resource, pay_invoice, pay_l402_challenge, test_l402_payment, and 13 more. Their descriptions and schemas cost roughly 2,370 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 5 November 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.