Lightning Wallet
NPM · LIGHTNING-WALLET-MCP · SCANNED SEP 20
Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to lightningfaucet/lightning-wallet-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3307 tokens (~61/item across 54 items; 54 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 13 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_l402_api" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 54 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
How do I install the Lightning Wallet MCP server?
Lightning Wallet runs locally as an npm package, launched with npx -y lightning-wallet-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · lightning-wallet-mcp
claude mcp add lightningfaucet-lightning-wallet-mcp -- npx -y lightning-wallet-mcp
{
"mcpServers": {
"lightningfaucet-lightning-wallet-mcp": {
"command": "npx",
"args": [
"-y",
"lightning-wallet-mcp"
]
}
}
} {
"servers": {
"lightningfaucet-lightning-wallet-mcp": {
"command": "npx",
"args": [
"-y",
"lightning-wallet-mcp"
]
}
}
} codex mcp add lightningfaucet-lightning-wallet-mcp -- npx -y lightning-wallet-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lightningfaucet-lightning-wallet-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"lightning-wallet-mcp"
],
"enabled": true
}
}
} openclaw mcp add lightningfaucet-lightning-wallet-mcp --command npx --arg -y --arg lightning-wallet-mcp
mcp_servers:
lightningfaucet-lightning-wallet-mcp:
command: "npx"
args: ["-y", "lightning-wallet-mcp"] {
"McpServers": {
"lightningfaucet-lightning-wallet-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"lightning-wallet-mcp"
]
}
}
} assistant mcp add lightningfaucet-lightning-wallet-mcp -t stdio -c npx -a -y lightning-wallet-mcp
{
"mcpServers": {
"lightningfaucet-lightning-wallet-mcp": {
"command": "npx",
"args": [
"-y",
"lightning-wallet-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 15 Sept 26 −3
- Malware scan: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- Stability: 0.97 → pass security
- The attested source repository moved: lightningfaucet/lightning-wallet-mcp security
- Schema quality: 2755 → 3307 ▼ functional
- Package version: 1.6.1 → 1.7.0 functional
- 13 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 1.5.0 → 1.6.1 functional
- 10 Sept 26 −3
- Stability: pass → 0.83 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/lightning-wallet-mcp@1.7.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | lightningfaucet/lightning-wallet-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/lightningfaucet/lightning-wallet-mcp/.github/workflows/publish.yml@refs/tags/v1.7.0 |
| Rekor log index | 2851468989 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:acc411f76f7563f7fcbed7cb2709509e63525a230d1aa9131ef29b0318c05ea9a04ca1d2a38b66e0522e51efdb869b891bb0b8a2bb510bc113c2fbc47 |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
transfer_to_agent ~68
Transfer sats between agents or from operator to agent. REQUIRES OPERATOR KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | integer | yes | Amount to transfer |
| from_agent_id | integer | – | Source agent ID (omit to use operator balance) |
| to_agent_id | integer | yes | Destination agent ID |
No output schema declared.
No examples provided.
update_operator ~77
Update operator profile: set your email (sends a verification link - required for the free-sats promo) and/or display name. REQUIRES OPERATOR KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address to set. A verification link is emailed; click it to verify. | |
| name | string | – | Display name for the operator account |
No output schema declared.
No examples provided.
whoami ~32
Get current context - returns whether you are operating as an operator or agent, along with ID, name, and balance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
withdraw ~72
Withdraw funds from the operator account to an external Lightning invoice (minimum 10 sats; 1% platform fee, none under 100 sats; unused routing reserve refunded). REQUIRES OPERATOR KEY. Subject to a security cooldown after key rotation.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | BOLT11 invoice to pay out to |
No output schema declared.
No examples provided.
What is the Lightning Wallet MCP server?
Lightning Wallet is an MCP server listed in the public MCP registry as io.github.lightningfaucet/lightning-wallet-mcp. Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support. This page covers its npm package (lightning-wallet-mcp).
Is the Lightning Wallet MCP server safe to use?
Lightning Wallet scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Wallet MCP server expose?
Lightning Wallet exposes 54 tools: check_balance, pay_l402_api, pay_invoice, create_invoice, get_invoice_status, and 49 more. Their descriptions and schemas cost roughly 3,307 tokens of context every time the server is loaded.
Is the Lightning Wallet MCP server still maintained?
Lightning Wallet 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 Wallet MCP server under?
Lightning Wallet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.