Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.lightningfaucet/mcp-server

NPM · LIGHTNING-FAUCET-MCP · SCANNED SEP 20

Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.

0 this week 75 Trust /100
Trust breakdown (7 categories)

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 & Transparency19
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1763 tokens (~47/item across 37 items; 37 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 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 10 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 37 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
Install

How do I install the io.github.lightningfaucet/mcp-server server?

io.github.lightningfaucet/mcp-server runs locally as an npm package, launched with npx -y lightning-faucet-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-faucet-mcp

# add to Claude Code
claude mcp add lightningfaucet-mcp-server -- npx -y lightning-faucet-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "lightningfaucet-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "lightning-faucet-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lightningfaucet-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "lightning-faucet-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add lightningfaucet-mcp-server -- npx -y lightning-faucet-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lightningfaucet-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "lightning-faucet-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lightningfaucet-mcp-server --command npx --arg -y --arg lightning-faucet-mcp
# ~/.hermes/config.yaml
mcp_servers:
  lightningfaucet-mcp-server:
    command: "npx"
    args: ["-y", "lightning-faucet-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lightningfaucet-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lightning-faucet-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add lightningfaucet-mcp-server -t stdio -c npx -a -y lightning-faucet-mcp
// mcp.json
{
  "mcpServers": {
    "lightningfaucet-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "lightning-faucet-mcp"
      ]
    }
  }
}
Changelog

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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 15 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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-faucet-mcp@2.0.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

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 →

MCP tools · 37 exposed · ~1,763 tokens

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 →

Tool Tokens
check_balance ~26

Check your current Lightning balance in satoshis. Works with both operator and agent keys.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

claim_lnurl_withdraw ~44

Claim funds from an LNURL-withdraw link. REQUIRES AGENT KEY.

NameTypeReqDescription
lnurlstringyesLNURL-withdraw string to claim from

No output schema declared.

No examples provided.

create_agent ~58

Create a new agent under your operator account. Returns the agent API key.

NameTypeReqDescription
budget_limit_satsintegerOptional spending limit in sats
descriptionstringOptional description
namestringyesName for the agent

No output schema declared.

No examples provided.

create_invoice ~54

Create a Lightning invoice to receive payment. Use get_invoice_status to check if paid.

NameTypeReqDescription
amount_satsintegeryesAmount in satoshis to request
memostringDescription/memo for the invoice

No output schema declared.

No examples provided.

deactivate_agent ~40

Deactivate an agent - it cannot make payments until reactivated. REQUIRES OPERATOR KEY.

NameTypeReqDescription
agent_idintegeryesAgent ID to deactivate

No output schema declared.

No examples provided.

decode_invoice ~43

Decode a BOLT11 invoice without paying it. Returns amount, description, expiry, and destination.

NameTypeReqDescription
bolt11stringyesBOLT11 invoice string to decode

No output schema declared.

No examples provided.

delete_agent ~53

Permanently delete an agent. Remaining balance is returned to operator. REQUIRES OPERATOR KEY.

NameTypeReqDescription
agent_idintegeryesAgent ID to delete
confirmbooleanyesMust be true to confirm deletion

No output schema declared.

No examples provided.

delete_webhook ~35

Delete a registered webhook. REQUIRES AGENT KEY.

NameTypeReqDescription
webhook_idintegeryesID of the webhook to delete

No output schema declared.

No examples provided.

export_transactions ~65

Export transaction history in JSON or CSV format.

NameTypeReqDescription
end_datestringISO date for end of range
formatstringExport format
include_pendingbooleanInclude pending transactions
start_datestringISO date for start of range

No output schema declared.

No examples provided.

fund_agent ~47

Transfer sats from operator balance to an agent.

NameTypeReqDescription
agent_idintegeryesID of the agent to fund
amount_satsintegeryesAmount in satoshis to transfer

No output schema declared.

No examples provided.

get_agent_analytics ~42

Get detailed spending analytics for an agent.

NameTypeReqDescription
agent_idintegerAgent ID (defaults to current agent)
periodstringTime period

No output schema declared.

No examples provided.

get_budget_status ~49

Get budget status for an agent - shows limit, spent, and remaining. Works with operator or agent keys.

NameTypeReqDescription
agent_idintegerAgent ID (operators only, omit for current agent)

No output schema declared.

No examples provided.

get_deposit_invoice ~46

Create a Lightning invoice to fund your operator account. Pay this invoice to add sats to your balance.

NameTypeReqDescription
amount_satsintegeryesAmount in satoshis to deposit

No output schema declared.

No examples provided.

get_info ~22

Get service information including version, status, limits, and supported features.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_invoice_status ~41

Check if a created invoice has been paid. Use the payment_hash from create_invoice.

NameTypeReqDescription
payment_hashstringyesPayment hash of the invoice to check

No output schema declared.

No examples provided.

get_rate_limits ~21

Get current rate limit status - requests remaining and reset time.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_transactions ~44

Get the agent transaction history. Returns both incoming and outgoing payments.

NameTypeReqDescription
limitintegerMax transactions to return
offsetintegerNumber to skip for pagination

No output schema declared.

No examples provided.

keysend ~69

Send a payment directly to a node without an invoice (keysend/spontaneous payment). REQUIRES AGENT KEY.

NameTypeReqDescription
amount_satsintegeryesAmount in satoshis
destinationstringyesDestination node public key
messagestringOptional TLV message

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_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.

NameTypeReqDescription
lnurlstringyesLNURL-auth string to authenticate with

No output schema declared.

No examples provided.

pay_invoice ~73

Pay a BOLT11 Lightning invoice from the agent balance. Returns preimage as proof of payment. REQUIRES AGENT KEY.

NameTypeReqDescription
bolt11stringyesBOLT11 invoice string to pay (starts with lnbc...)
max_fee_satsintegerMaximum routing fee in satoshis

No output schema declared.

No examples provided.

pay_l402_api ~113

Make 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.

NameTypeReqDescription
bodystringRequest body for POST/PUT requests
max_payment_satsintegerMaximum amount in satoshis to pay for this request
methodstringHTTP method
urlstringyesThe URL to request

No output schema declared.

No examples provided.

pay_lightning_address ~69

Pay to a Lightning address (user@domain.com format). REQUIRES AGENT KEY.

NameTypeReqDescription
addressstringyesLightning address (user@domain.com)
amount_satsintegeryesAmount in satoshis to send
commentstringOptional payment comment

No output schema declared.

No examples provided.

reactivate_agent ~37

Reactivate a previously deactivated agent. REQUIRES OPERATOR KEY.

NameTypeReqDescription
agent_idintegeryesAgent ID to reactivate

No output schema declared.

No examples provided.

recover_account ~45

Recover an operator account using the recovery code from registration. Returns a new API key. Triggers 60-min withdrawal cooldown.

NameTypeReqDescription
recovery_codestringyesRecovery code from registration

No output schema declared.

No examples provided.

register_operator ~44

Register a new operator account. Returns API key and recovery code. SAVE THESE - they cannot be retrieved later!

NameTypeReqDescription
namestringName for the operator account (optional)

No output schema declared.

No examples provided.

register_webhook ~58

Register a webhook URL to receive payment notifications. Max 5 webhooks per agent. REQUIRES AGENT KEY.

NameTypeReqDescription
eventsarrayEvent types to subscribe to
urlstringyesHTTPS 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.

NameTypeReqDescription
agent_idintegerAgent ID (operators only). Omit to rotate operator key.

No output schema declared.

No examples provided.

set_agent_credentials ~42

Switch to an agent API key for subsequent requests. Use to operate as a specific agent after creating it.

NameTypeReqDescription
api_keystringyesThe agent API key

No output schema declared.

No examples provided.

set_budget ~55

Set or update budget limit for an agent. REQUIRES OPERATOR KEY.

NameTypeReqDescription
agent_idintegeryesAgent ID to update
budget_limit_satsintegeryesNew budget limit in sats (0 for unlimited)

No output schema declared.

No examples provided.

set_operator_key ~43

Switch to a different operator API key for subsequent requests. Use after register_operator to start using the new credentials.

NameTypeReqDescription
api_keystringyesThe operator API key

No output schema declared.

No examples provided.

sweep_agent ~57

Sweep funds from agent back to operator balance. REQUIRES OPERATOR KEY.

NameTypeReqDescription
agent_idintegeryesAgent ID to sweep funds from
amount_satsintegeryesAmount in sats (use large number for 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.

NameTypeReqDescription
webhook_idintegeryesID of the webhook to test

No output schema declared.

No examples provided.

transfer_to_agent ~68

Transfer sats between agents or from operator to agent. REQUIRES OPERATOR KEY.

NameTypeReqDescription
amount_satsintegeryesAmount to transfer
from_agent_idintegerSource agent ID (omit to use operator balance)
to_agent_idintegeryesDestination agent ID

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 ~44

Withdraw funds from operator account to external Lightning invoice. REQUIRES OPERATOR KEY. Subject to security cooldown.

NameTypeReqDescription
invoicestringyesBOLT11 invoice to pay out to

No output schema declared.

No examples provided.

Common questions

What is the io.github.lightningfaucet/mcp-server server?

io.github.lightningfaucet/mcp-server is listed in the public MCP registry as io.github.lightningfaucet/mcp-server. Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support. This page covers its npm package (lightning-faucet-mcp).

Is the io.github.lightningfaucet/mcp-server server safe to use?

io.github.lightningfaucet/mcp-server scores 75 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. 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 io.github.lightningfaucet/mcp-server server expose?

io.github.lightningfaucet/mcp-server exposes 37 tools: check_balance, pay_l402_api, pay_invoice, create_invoice, get_invoice_status, and 32 more. Their descriptions and schemas cost roughly 1,763 tokens of context every time the server is loaded.

Is the io.github.lightningfaucet/mcp-server server still maintained?

io.github.lightningfaucet/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 io.github.lightningfaucet/mcp-server server under?

io.github.lightningfaucet/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.