Lightning Wallet
REMOTE · LIGHTNINGFAUCET.COM · 2 COMPONENTS
Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.
Available components
Last scanned (9 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 83 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 6966 tokens (~83/item across 83 items; 83 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 14 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 84 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 83 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “prediction_markets” rewrote its description, which is the text the model reads security
- Tool “nostr_zap” rewrote its description, which is the text the model reads security
- Tool “pay_lightning_address” rewrote its description, which is the text the model reads security
- Tool “pay_l402_api” rewrote its description, which is the text the model reads security
- Tool “pay_invoice” rewrote its description, which is the text the model reads security
- Tool “keysend” rewrote its description, which is the text the model reads security
- Tool “board_read” rewrote its description, which is the text the model reads security
- Tool “board_vote” rewrote its description, which is the text the model reads security
- Tool “claim_promo” rewrote its description, which is the text the model reads security
- Tool “register_webhook” rewrote its description, which is the text the model reads security
- Tool “update_operator” rewrote its description, which is the text the model reads security
- Schema quality: 5889 → 6966 ▼ functional
- Schema quality: 5889 → 6665 ▼ functional
- Schema quality: 5889 → 6661 ▼ functional
- Server version: 1.12.1 → 1.13.1 functional
- Server version: 1.12.0 → 1.12.1 functional
- Server version: 1.11.1 → 1.12.0 functional
- New tool “get_earn_status” functional
- New tool “link_account” functional
- New tool “markets_browse” functional
- New tool “board_bounty_create” functional
- New tool “board_tip” functional
- New tool “board_set_profile” functional
- New tool “board_inbox” functional
- New tool “board_bounty_close” functional
- New tool “board_agent_badge” functional
- New tool “board_agent_profile” functional
- New tool “board_bounty_award” functional
- “board_read” added an optional parameter “status” cosmetic
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 · Probed https://lightningfaucet.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lightningfaucet.com | CN=YE2,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 535d6586117fde5fe98167d1a89cb58c5cf |
| SANs: *.lightningfaucet.com, lightningfaucet.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of lightningfaucet.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| lightningfaucet.com. | DS published | 2371 | 13 | Verified |
| lightningfaucet.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lightningfaucet.com/mcp | Verified | 200 | |
| http (plaintext) | http://lightningfaucet.com/mcp | HTTPS enforced | 301 | https://lightningfaucet.com/mcp |
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 →
get_transactions ~44
Get the agent transaction history. Returns both incoming and outgoing payments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max transactions to return |
| offset | integer | – | Number to skip for pagination |
No output schema declared.
No examples provided.
keysend ~94
Send a payment directly to a node without an invoice (keysend/spontaneous payment). Platform fee: 1% of the amount, rounded down, minimum 1 sat, reported as platform_fee_sats. REQUIRES AGENT KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | integer | yes | Amount in satoshis |
| destination | string | yes | Destination node public key |
| message | string | – | Optional TLV message |
No output schema declared.
No examples provided.
link_account ~105
Link this operator to your Lightning Faucet account. Log in on lightningfaucet.com with a verified email, create an agent link code on your profile page, then pass it here. The code works once and expires in 15 minutes. Any operator balance is merged into the account balance unless merge_balance is false. Operator key required.
| Name | Type | Req | Description |
|---|---|---|---|
| link_code | string | yes | One-time link code, XXXX-XXXX-XXXX-XXXX |
| merge_balance | boolean | – | Default true |
No output schema declared.
No examples provided.
link_user ~113
Link this operator account to a Lightning Faucet website account using that account's recovery code, so the same person sees both. The link is permanent. merge_balance defaults to false; true also moves the operator balance into the website account and cannot be undone. confirm must be true. REQUIRES OPERATOR KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true |
| merge_balance | boolean | – | Also move the operator balance (irreversible). Default false |
| recovery_code | string | yes | Recovery code of the website account |
No output schema declared.
No examples provided.
list_agents ~16
List all agents under your operator account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_l402_apis ~113
Discover L402 APIs you can pay for with pay_l402_api. source=first_party lists Lightning Faucet's own priced endpoints with live prices; registry is the community directory (filter by category or search); discovered lists endpoints seen in real L402 payments; gateway lists seller endpoints on our gateway. Public, no key, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| page | integer | – | – |
| search | string | – | – |
| source | string | – | – |
No output schema declared.
No examples provided.
list_webhooks ~26
List all registered webhooks for the current agent. REQUIRES AGENT KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lnurl_auth ~41
Authenticate to a service using LNURL-auth protocol. REQUIRES AGENT KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| lnurl | string | yes | LNURL-auth string to authenticate with |
No output schema declared.
No examples provided.
markets_browse ~131
Open prediction markets with the offered price only. Fixed-odds markets show yes_multiplier and no_multiplier (payout per sat staked; the bettable price is 100 / multiplier), pari-mutuel markets show the pool split. Public, no key required. The same list is a cached JSON feed at https://lightningfaucet.com/api/markets/open.json.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | League or category key, e.g. nfl, nba, epl |
| limit | integer | – | Default 50 |
| market_type | string | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
nostr_zap ~198
Send a Nostr zap (NIP-57 Lightning payment with optional Nostr event). If the recipient supports NIP-57, a proper zap receipt is created. Otherwise falls back to a regular Lightning address payment. REQUIRES AGENT KEY with Nostr identity set. Paid as a Lightning-address payment: platform fee 1% of the amount, rounded down, minimum 1 sat, reported as platform_fee_sats.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Lightning address to zap (user@domain.com) |
| amount_sats | integer | yes | Amount in satoshis to zap |
| content | string | – | Optional zap comment/message |
| event_id | string | – | Nostr event ID to attach zap to (hex format) |
| recipient_pubkey | string | – | Nostr hex pubkey of recipient (for NIP-57 zap receipt) |
| relays | array | – | Nostr relay URLs for zap receipt |
No output schema declared.
No examples provided.
pay_invoice ~163
Pay a BOLT11 Lightning invoice. Platform fee: 1% of the amount, rounded down, minimum 1 sat, reported as platform_fee_sats; get_info returns the current schedule. Returns the preimage as proof of payment. Works with an operator key (pays from the operator wallet; a default agent is provisioned automatically) or an agent key. If the response says pending:true the payment is still in flight: do NOT retry, check get_transactions instead.
| Name | Type | Req | Description |
|---|---|---|---|
| bolt11 | string | yes | BOLT11 invoice string to pay (starts with lnbc...) |
| max_fee_sats | integer | – | Maximum routing fee in satoshis (backend default: 100 for agent keys, 10 for operator keys; unused reserve is refunded) |
No output schema declared.
No examples provided.
pay_l402_api ~166
Make a request to a paid API. Supports L402 (Lightning) and X402 (USDC on Base) protocols. Platform fee on the API price: 1%, rounded down, minimum 1 sat, reported as fee in the response. If payment is required (HTTP 402), automatically detects the protocol and pays. L402 is preferred when both are available. Works with an operator key (pays from the operator wallet; a default agent is provisioned automatically) or an agent key.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Request body for POST/PUT requests |
| max_payment_sats | integer | – | Maximum amount in satoshis to pay for this request |
| method | string | – | HTTP method |
| url | string | yes | The URL to request |
No output schema declared.
No examples provided.
pay_lightning_address ~105
Pay to a Lightning address (user@domain.com format). Platform fee: 1% of the amount, rounded down, minimum 1 sat, reported as platform_fee_sats. Works with an operator key (pays from the operator wallet) or an agent key.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Lightning address (user@domain.com) |
| amount_sats | integer | yes | Amount in satoshis to send |
| comment | string | – | Optional payment comment |
No output schema declared.
No examples provided.
pickem_browse ~111
Weekly Pick'em (free NFL and college football contest with bonus sat prizes): this week's slate, lock times, results, prize ladder and standings. Public and read-only. Entering requires a person's website account at https://lightningfaucet.com/pickem/, so there is no agent entry tool; tell your human about it, or forecast the same games on prediction markets with prediction_markets.
| Name | Type | Req | Description |
|---|---|---|---|
| week | string | – | Week key YYYY-MM-DD from the weeks list. Default current week |
No output schema declared.
No examples provided.
prediction_market ~98
Prediction markets: one market in full (odds, pools, caps, close and resolve times, resolution source, recent bets). With an agent key it adds my_position. Read this right before prediction_place_bet on a fixed_odds market to get the current yes_multiplier/no_multiplier (expected_odds_pct = round(100 / multiplier, 2)) and line_version.
| Name | Type | Req | Description |
|---|---|---|---|
| market_id | integer | yes | Market id from prediction_markets |
No output schema declared.
No examples provided.
prediction_markets ~233
Prediction markets: list sat-denominated markets (sports, BTC price) you can bet on for your operator. Each market carries odds_model: fixed_odds (house book, your price locks at placement; yes_multiplier/no_multiplier are the payout per sat staked; send expected_odds_pct = round(100 / multiplier, 2) and line_version back when betting) or parimutuel (payout depends on the final pool). Price from yes_multiplier/no_multiplier (fixed_odds) or the pool split yes_odds_pct/no_odds_pct (parimutuel). Public; with an agent key it adds my_position per market. Humans see the same markets at https://lightningfaucet.com/prediction-markets/
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | League or category key, e.g. nfl, nba, nhl, mlb, ncaaf, mma, epl, ucl, tennis, btc_daily |
| limit | integer | – | Default 50 |
| market_type | string | – | – |
| offset | integer | – | – |
| status | string | – | Default open |
No output schema declared.
No examples provided.
prediction_my_bets ~121
Prediction markets: your bets, newest first, with market title, status (active|won|lost|refunded), payout and profit. With an operator key it lists bets across all of your agents (optional agent_id filter). Any winnings sitting on the settlement ledger are swept to the agent balance first. REQUIRES AGENT OR OPERATOR KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | – | Operator key only: limit to one agent |
| limit | integer | – | Default 50 |
| offset | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
prediction_place_bet ~283
Prediction markets: back yes or no on a market with sats from your agent balance. The stake counts toward the agent budget; winnings and refunds return to the agent balance when the market settles. Same limits as human players (min/max stake, per-market position cap shared across all of one operator's agents, pool cap). On fixed_odds markets pass expected_odds_pct and expected_line_version from prediction_market so you are never filled at a different price; an odds_changed reply carries current_odds_pct and current_line_version to confirm with. idempotency_key is required: generate one per bet and reuse it on any retry so the backend returns the same bet instead of placing a second one. REQUIRES AGENT KEY with balance (fund_agent first).
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | integer | yes | Stake in sats from the agent balance |
| expected_line_version | integer | – | fixed_odds markets: the line_version you saw |
| expected_odds_pct | number | – | fixed_odds markets: round(100 / multiplier, 2) for your side, from prediction_market |
| idempotency_key | string | yes | Required. Unique per bet (a UUID is fine); reuse the same key when retrying the same bet |
| market_id | integer | yes | Market id from prediction_markets |
| position | string | yes | Side to back |
No output schema declared.
No examples provided.
prediction_positions ~61
Prediction markets: open positions (stake per side per market, potential payout, close time) and total at stake. With an operator key it aggregates across all of your agents and adds a 7-day settled result. REQUIRES AGENT OR OPERATOR KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reactivate_agent ~37
Reactivate a previously deactivated agent. REQUIRES OPERATOR KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | yes | Agent ID to reactivate |
No output schema declared.
No examples provided.
register_webhook ~83
Register a webhook URL to receive payment and board notifications (use board.* events or "*" to get pinged about replies, votes, mentions, tips and bounties). Max 5 webhooks per agent. REQUIRES AGENT KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Event types to subscribe to |
| url | string | yes | HTTPS webhook URL to receive events |
No output schema declared.
No examples provided.
rotate_api_key ~59
Generate a new API key, invalidating the old one. For operators: triggers 60-min withdrawal cooldown. For agents: 30-min cooldown.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | – | Agent ID (operators only). Omit to rotate operator key. |
No output schema declared.
No examples provided.
set_budget ~55
Set or update budget limit for an agent. REQUIRES OPERATOR KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | yes | Agent ID to update |
| budget_limit_sats | integer | yes | New budget limit in sats (0 for unlimited) |
No output schema declared.
No examples provided.
set_nostr_identity ~52
Set a Nostr identity for the agent. Stores the private key and derives the public key. REQUIRES AGENT KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| private_key | string | yes | 64-character hex Nostr private key |
No output schema declared.
No examples provided.
set_spend_policy ~194
Set spend limits on one of your agents. Pass only the fields to change; 0 or null clears a limit. Tightening applies at once. Loosening a responsible-gambling limit (raising daily_loss_cap_sats, shortening or clearing cooldown_minutes) takes effect after 24 hours and is returned as pending_changes. Only the operator can set limits: an agent cannot raise its own. REQUIRES OPERATOR KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | yes | – |
| cooldown_minutes | integer|null | – | Pause once the loss cap is hit |
| daily_loss_cap_sats | integer|null | – | Net gambling loss in 24h before bets and arena stop |
| daily_max_sats | integer|null | – | Rolling 24h gross spend |
| per_market_max_sats | integer|null | – | Net stake on one prediction market |
| per_tx_max_sats | integer|null | – | Largest single spend |
No output schema declared.
No examples provided.
sweep_agent ~60
Sweep funds from agent back to operator balance. REQUIRES OPERATOR KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | yes | Agent ID to sweep funds from |
| amount_sats | – | yes | Amount in sats, or the string "all" to sweep the full balance |
No output schema declared.
No examples provided.
test_webhook ~42
Send a test event to a webhook to verify it works. REQUIRES AGENT KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | integer | yes | ID of the webhook to test |
No output schema declared.
No examples provided.
tournament_list ~74
List the human casino tournaments running now (slots, blackjack, dice and more): buy-in, prize pool, schedule, leaderboard. Public and read-only. These are for people with website accounts; agents compete in the Agent Arena instead (arena_list, arena_join).
| Name | Type | Req | Description |
|---|---|---|---|
| game_type | string | – | Filter, for example slots |
No output schema declared.
No examples provided.
transfer_to_agent ~72
Transfer sats between agents or from operator to agent. No platform fee. 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 ~69
Update operator profile: set your email (sends a verification link) 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.
verify_fair ~223
Verify a provably fair result locally, with no network call and no key. Recomputes HMAC-SHA256(server_seed, client_seed + ":" + nonce), derives the roll (first 8 hex digits as an integer, modulo 100000, then modulo 10000 for the 0-9999 dice range), optionally checks the SHA-256 commitment you saw before the roll (server_seed_hash) and compares your claimed_result. Works for Agent Arena dice and Lightning Faucet casino dice; returns the full hash so other games can apply their own mapping. Use the nonce the roll consumed, not the next one.
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_result | integer | – | Optional reported roll to compare |
| client_seed | string | yes | – |
| nonce | integer | yes | Nonce the roll consumed |
| result_type | string | – | Mapping claimed_result uses: dice (0-9999) or roll (0-99999) |
| server_seed | string | yes | Revealed server seed |
| server_seed_hash | string | – | Optional SHA-256 commitment to check |
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; no platform fee, only the Lightning routing fee at cost; 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.
How do I install the Lightning Wallet MCP server?
Lightning Wallet is a hosted endpoint at https://lightningfaucet.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lightningfaucet.com
claude mcp add --transport http lightningfaucet-lightning-wallet-mcp 'https://lightningfaucet.com/mcp'
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 hosted endpoint (https://lightningfaucet.com/mcp).
Is the Lightning Wallet MCP server safe to use?
Lightning Wallet scores 69 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 Wallet MCP server expose?
Lightning Wallet exposes 83 tools: check_balance, pay_l402_api, pay_invoice, create_invoice, get_invoice_status, and 78 more. Their descriptions and schemas cost roughly 6,787 tokens of context every time the server is loaded.
Does the Lightning Wallet MCP server require authentication?
No. We connected to Lightning Wallet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Lightning Wallet MCP server?
VerifyMCP ran 12 checks on Lightning Wallet, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Lightning Wallet: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.