Lightningfaucet MCP server
io.github.lightningfaucet/mcp-server·v2.0.5·9 starsGive AI agents a Bitcoin wallet with Lightning Network payments and L402 support.
9 stars
Reviews
Write oneNobody has reviewed Lightningfaucet yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Lightningfaucet tools (37, 12 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
check_balanceCheck your current Lightning balance in satoshis. Works with both operator and agent keys.
claim_lnurl_withdrawClaim funds from an LNURL-withdraw link. REQUIRES AGENT KEY.
create_agentwrite actionCreate a new agent under your operator account. Returns the agent API key.
create_invoicewrite actionCreate a Lightning invoice to receive payment. Use get_invoice_status to check if paid.
deactivate_agentDeactivate an agent - it cannot make payments until reactivated. REQUIRES OPERATOR KEY.
decode_invoiceDecode a BOLT11 invoice without paying it. Returns amount, description, expiry, and destination.
delete_agentwrite actionPermanently delete an agent. Remaining balance is returned to operator. REQUIRES OPERATOR KEY.
delete_webhookwrite actionDelete a registered webhook. REQUIRES AGENT KEY.
export_transactionsExport transaction history in JSON or CSV format.
fund_agentwrite actionTransfer sats from operator balance to an agent.
get_agent_analyticsGet detailed spending analytics for an agent.
get_budget_statusGet budget status for an agent - shows limit, spent, and remaining. Works with operator or agent keys.
get_deposit_invoicewrite actionCreate a Lightning invoice to fund your operator account. Pay this invoice to add sats to your balance.
get_infoGet service information including version, status, limits, and supported features.
get_invoice_statusCheck if a created invoice has been paid. Use the payment_hash from create_invoice.
get_rate_limitsGet current rate limit status - requests remaining and reset time.
get_transactionsGet the agent transaction history. Returns both incoming and outgoing payments.
keysendwrite actionSend a payment directly to a node without an invoice (keysend/spontaneous payment). REQUIRES AGENT KEY.
list_agentsList all agents under your operator account.
list_webhooksList all registered webhooks for the current agent. REQUIRES AGENT KEY.
lnurl_authAuthenticate to a service using LNURL-auth protocol. REQUIRES AGENT KEY.
pay_invoicewrite actionPay a BOLT11 Lightning invoice from the agent balance. Returns preimage as proof of payment. REQUIRES AGENT KEY.
pay_l402_apiwrite actionMake a request to an L402-protected API. If payment is required (HTTP 402), automatically pay the Lightning invoice and complete the request. REQUIRES AGENT KEY - use set_agent_credentials first if operating as an operator.
pay_lightning_addresswrite actionPay to a Lightning address (user@domain.com format). REQUIRES AGENT KEY.
reactivate_agentReactivate a previously deactivated agent. REQUIRES OPERATOR KEY.
recover_accountRecover an operator account using the recovery code from registration. Returns a new API key. Triggers 60-min withdrawal cooldown.
register_operatorRegister a new operator account. Returns API key and recovery code. SAVE THESE - they cannot be retrieved later!
register_webhookRegister a webhook URL to receive payment notifications. Max 5 webhooks per agent. REQUIRES AGENT KEY.
rotate_api_keyGenerate a new API key, invalidating the old one. For operators: triggers 60-min withdrawal cooldown. For agents: 30-min cooldown.
set_agent_credentialsSwitch to an agent API key for subsequent requests. Use to operate as a specific agent after creating it.
set_budgetSet or update budget limit for an agent. REQUIRES OPERATOR KEY.
set_operator_keySwitch to a different operator API key for subsequent requests. Use after register_operator to start using the new credentials.
sweep_agentSweep funds from agent back to operator balance. REQUIRES OPERATOR KEY.
test_webhookwrite actionSend a test event to a webhook to verify it works. REQUIRES AGENT KEY.
transfer_to_agentwrite actionTransfer sats between agents or from operator to agent. REQUIRES OPERATOR KEY.
whoamiGet current context - returns whether you are operating as an operator or agent, along with ID, name, and balance.
withdrawWithdraw funds from operator account to external Lightning invoice. REQUIRES OPERATOR KEY. Subject to security cooldown.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 9 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Lightningfaucet compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- Tools
- 37
- the typical server has 7
- Tools that change things
- 32%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 9
- more than 87% of 28,688 servers
What its tools let an agent do: 20 read · 4 create · 11 change · 2 delete
Install Lightningfaucet in Claude Code, Cursor or VS Code
Runs npx -y lightning-faucet-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-server -- npx -y lightning-faucet-mcp
What the publisher says
From the Lightningfaucet repository's README, as published. We do not edit it. Read it on GitHub
Lightning Wallet
Give your AI agent a Bitcoin wallet. One MCP server plus a CLI. Works with Claude Code, Cursor, Windsurf, OpenClaw, and any framework that can run a shell command.
Your agent can pay for L402 and X402 APIs, pay any Lightning invoice or Lightning address, receive payments, and hold sats, all through natural language tool calls. Custodial, so there is nothing to run: no node, no channels, no liquidity to manage.
Quick start (60 seconds)
Claude Code
claude mcp add lightning-wallet -- npx -y lightning-wallet-mcpThen in Claude: "Register a Lightning wallet for me with the email you@example.com".
That is it. register_operator saves your credentials to ~/.lightning-wallet/credentials.json (mode 0600) and every later session reuses them automatically. Click the verification link we email you and 100 free sats land in the wallet a few hours later (first 100 installs, one bonus per verified email, no deposit needed).
Cursor / Windsurf / any MCP host (.cursor/mcp.json, .mcp.json, or the host's MCP settings):
{
"mcpServers": {
"lightning-wallet": {
"command": "npx",
"args": ["-y", "lightning-wallet-mcp"]
}
}
}Already have a key? Put it in the env block instead of registering again. The env var always wins over the saved file:
{
"mcpServers": {
"lightning-wallet": {
"command": "npx",
"args": ["-y", "lightning-wallet-mcp"],
"env": { "LIGHTNING_WALLET_API_KEY": "lf_your_operator_key" }
}
}
}CLI (any agent framework, CI, or a plain shell):
npm install -g lightning-wallet-mcp
lw register --name "My Bot" --email you@example.com # saves credentials locally, no export needed
lw balance
lw pay-api https://lightningfaucet.com/api/l402/fortune
lw pay <bolt11>
lw pay-address someone@getalby.com 100What's new in v1.6
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Lightningfaucet: common questions
- Is Lightningfaucet MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the Lightningfaucet safety report
- How do I install Lightningfaucet?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Lightningfaucet need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Lightningfaucet maintained?
- The last commit was 43 days ago (2026-09-22). The latest release is v2.0.5.
- How does Lightningfaucet compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); tools 37 (the typical server has 7); tools that change things 32% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.