$ loading_
Connect AI agents to a Lightning wallet with budgets, approvals, and audit logs.
This MCP tool is designed to let AI agents access a Lightning wallet through Nostr Wallet Connect, so the main exposure is the wallet credential and payment capability itself. With an official registry listing, open-source code, and recent maintenance, it appears generally auditable and lower risk overall, but it should be run with least privilege and strict spending limits.
It requires NWC_CONNECTION_STRING, which by function is a highly sensitive credential for connecting to and potentially controlling an NWC wallet; if exposed, it could enable payments or other wallet misuse. NWC_DAILY_BUDGET_SATS and NWC_READ_ONLY add budget and read-only constraints, which reduce impact but do not remove the primary credential risk.
No fixed remote host is declared in the materials, but the tool’s stated function inherently depends on Nostr Wallet Connect, so communicating with wallet infrastructure is part of its normal behavior. There is no clear evidence of sending data to unrelated third parties, but endpoint transparency is limited here and actual egress likely depends on the connection string configuration.
The system checks indicate that this tool executes code or runs as a local process, which is a standard MCP capability. The available materials do not show requests for system privileges clearly beyond its wallet function, but it should still be treated as a locally executable component and confined appropriately.
The description mentions budget caps, confirmation, and an audit log, indicating that it handles payment-related state and audit records; as a local process it will also typically have access to wallet credentials in environment variables. The materials do not show broad filesystem or unrelated data access, so there is no clear sign of over-privilege, but its visible data scope should still be minimized.
It comes from an official registry, has an auditable open-source repository, and has been updated within the last year, all of which are positive signals that lower supply-chain risk. The repository does not declare a license and has very low community adoption, which suggests limited ecosystem maturity, but these facts alone do not justify a high-risk rating.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "io.github.llmops-pro/nwc-mcp" MCP server from askskill: Run: claude mcp add 'io-github-llmops-pro-nwc-mcp' -- npx -y nwc-mcp
Help me configure a Nostr Wallet Connect Lightning wallet for this AI agent: 1000 sats max per payment, 5000 sats daily budget, require human approval above limits, and log all payments.
A wallet configuration plan including budget rules, approval flow, and audit logging requirements.
Design an approval flow for an AI agent making Lightning payments via NWC: auto-approve small payments, require human approval for larger ones, and make both failures and successes traceable.
A tiered approval workflow and status tracking plan for secure agent payments.
Outline audit requirements for this AI agent's Lightning wallet, including what fields to log and how to track each payment by time, amount, and approval status.
A checklist of audit log fields and tracking recommendations for troubleshooting and compliance review.
Enable AI agents to handle Lightning payments, wallets, and gated API access.
Enable AI agents to safely publish, query, and send DMs on Nostr.
Enable no-KYC web search for AI agents with pay-per-query Lightning access.
Enable AI agents to fully manage an RGB Lightning wallet and payments.
Manage Bitcoin micropayments, offers, and escrow contracts through MCP tools.
Enable AI agents to perform double-entry bookkeeping, ledger queries, and reconciliation.