Nwc MCP

Name: Nwc MCP
Author: llmops-pro

by llmops-proversion 0.2.3i★ –iRuns on your computer

Registry nameio.github.llmops-pro/nwc-mcp

Install

Overview

Description from the maker (original English)

Lightning wallet for AI agents via Nostr Wallet Connect (NIP-47): budget caps, confirm, audit log.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: NWC_CONNECTION_STRING

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: NWC_CONNECTION_STRING, NWC_DAILY_BUDGET_SATS, NWC_READ_ONLY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "nwc": {
      "command": "npx",
      "args": [
        "-y",
        "nwc-mcp"
      ],
      "env": {
        "NWC_CONNECTION_STRING": "your-value",
        "NWC_DAILY_BUDGET_SATS": "your-value",
        "NWC_READ_ONLY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add nwc --env NWC_CONNECTION_STRING=your-value --env NWC_DAILY_BUDGET_SATS=your-value --env NWC_READ_ONLY=your-value -- npx -y nwc-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "nwc": {
      "command": "npx",
      "args": [
        "-y",
        "nwc-mcp"
      ],
      "env": {
        "NWC_CONNECTION_STRING": "your-value",
        "NWC_DAILY_BUDGET_SATS": "your-value",
        "NWC_READ_ONLY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "nwc": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "nwc-mcp"
      ],
      "env": {
        "NWC_CONNECTION_STRING": "your-value",
        "NWC_DAILY_BUDGET_SATS": "your-value",
        "NWC_READ_ONLY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

NWC_CONNECTION_STRING secret required env
Nostr Wallet Connect connection string (nostr+walletconnect://...)
NWC_DAILY_BUDGET_SATS env
Daily spend cap in sats
NWC_READ_ONLY env
Set true to block all spend tools

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account llmops-pro, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32712 servers in this category
Published to the registry more recently than 12% of the other 32712 servers in this category
Basic checks equal to or better than 100% of the other 32712 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Nwc MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: NWC_CONNECTION_STRING

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.3) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Aiterm MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Aiterm MCP

by kitepon

Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

nwc-mcp

A Lightning wallet for your LLM agent. MCP server that exposes Nostr Wallet Connect (NIP-47) wallet operations as tools your agent can call — read balance, generate invoices, pay invoices, pay Lightning Addresses, pay LNURLs, batch payments, keysend — all wrapped in a defense-in-depth safety stack.

Drop it into Claude Desktop, Claude Code, Cursor, or any MCP-speaking client. Hand the agent a sub-wallet (not your main one). Set a daily cap. Let it spend sats on your behalf within rails you control.

v0.2 — all spend tools shipped. Twelve tools (7 read/receive + 5 spend + 1 confirm), four safety gates, full audit log. Validated end-to-end against Alby Hub + Olympus by ZEUS routing — real outbound payment settled in 8 seconds.

What you can do with this

A coding agent that pays for its own paywalled tool calls (L402-style paid MCP servers).
A NOSTR bot that zaps interesting notes under a daily cap you set.
An evaluation harness that pays a small fee per task to a worker agent it consumes.
A storefront agent that issues receive invoices in response to incoming DMs.
Personal sats-aware agents — "every Friday, send 1,000 sats to my favorite OSS maintainers via their LN addresses."

The safety stack is the load-bearing reason this is usable in production: the agent can request a payment, but the *server* refuses anything that breaches your configured limits, demands a second-step confirmation if you set one, and writes every call to a structured audit log.

The twelve tools

Read-only (always enabled, no spend risk)

Tool	Purpose
`nwc_get_info`	Wallet capabilities, supported NIP-47 methods, node pubkey, network, alias. Call first.
`nwc_get_balance`	Spendable balance in sats (and msat).
`nwc_lookup_invoice`	Look up an invoice by payment hash or bolt11; returns state + preimage if settled.
`nwc_list_transactions`	List transactions with filters (time range, direction, unpaid).
`nwc_decode_invoice`	Parse a bolt11 locally — amount, memo, expiry, payee pubkey. No network call.
`nwc_budget_status`	Current spend budget state — daily spent, caps, lifetime spent.

Receive (safe — only generates invoices, no spend)

Tool	Purpose
`nwc_make_invoice`	Create a bolt11 invoice for a given amount of sats.

Spend (gated by the safety pipeline)

Tool	Purpose
`nwc_pay_invoice`	Pay a bolt11. Amount-resolution for amountless invoices via `amount_override_sats`.
`nwc_pay_lightning_address`	Pay `name@domain.tld` (LUD-16). Direct LNURL-pay resolution, non-proxied by default.
`nwc_pay_lnurl`	Pay a raw `lnurl1...` bech32 string (LUD-01).
`nwc_multi_pay_invoice`	Pay up to 20 invoices in one call. Sum is checked against the budget cap atomically.
`nwc_pay_keysend`	Spontaneous payment direct to a pubkey. Default-off — opt in via `NWC_KEYSEND_ENABLED=true`.
`nwc_confirm_payment`	Execute a two-step-confirm payment by consuming its one-time token.

Requirements

Node 20+
A NWC connection string from a NIP-47-compatible wallet (Alby Hub, Mutiny, Coinos, Phoenix, …)

The canonical buyer setup is Alby Hub PRO with a dedicated sub-wallet for the agent — that's what this server has been smoke-tested against. But the protocol is wallet-agnostic; anything that speaks NIP-47 works.

Install

# From npm (once published)

npx -y nwc-mcp

From source

git clone cd nwc-mcp corepack enable pnpm pnpm install pnpm build

Configure

Copy .env.example to .env and fill in your NWC connection string:

cp .env.example .env

edit .env: NWC_CONNECTION_STRING=nostr+walletconnect://...

The server auto-loads .env from the current working directory and from the project root (one level up from dist/). Env vars passed by the parent process (e.g., claude mcp add --env ...) take precedence over .env. .env is gitignored — keep your NWC string out of any committed file.

Required

Var	Purpose
`NWC_CONNECTION_STRING`	`nostr+walletconnect://...` — get this from your wallet (in Alby Hub: Sub-wallets → Connections). Treat as a secret — anyone holding it can spend up to the daily cap.
`NWC_DAILY_BUDGET_SATS`	Rolling 24h spend cap. Server refuses to start without this set.

Optional safety knobs

Var	Default	Purpose
`NWC_TOTAL_BUDGET_SATS`	unset	Lifetime spend cap.
`NWC_MAX_INVOICE_SATS`	unset	Per-payment cap.
`NWC_READ_ONLY`	`false`	If `true`, disables all spend tools — useful for dev / eval / curious mode.
`NWC_REQUIRE_CONFIRM`	`false`	If `true`, spend tools return a one-time token; payment only executes after `nwc_confirm_payment` with the token. Trades agent autonomy for safety.
`NWC_KEYSEND_ENABLED`	`false`	Opt-in toggle for `nwc_pay_keysend`. Off because keysend is power-user (no payment hash, weaker safety surface than bolt11).
`NWC_ALLOWED_DESTINATIONS`	unset	Comma-separated allowlist of LN addresses / pubkeys / LNURLs. If set, ONLY those can be paid.
`NWC_LOG_PATH`	`./nwc-mcp.log`	Path to the structured audit log file.
`NWC_BUDGET_STATE_PATH`	`./nwc-mcp-state.json`	Path to the persisted budget tracker state.

Wire into an MCP client

Claude Code (project-scoped, recommended)

From this directory:

claude mcp add nwc -s project node "$(pwd)/dist/index.js"

This writes a .mcp.json in the project root. Project-scoped servers load only when Claude Code starts from this directory tree. Use /mcp inside a session to inspect what's loaded. Restart the CLI to pick up a fresh dist/index.js after a rebuild.

Switch -s project to -s user if you want the server available everywhere.

Claude Desktop / Cursor / other clients

See examples/claude-desktop-config.json for the manifest snippet. Copy it into your client's config, replace the path placeholder. Because the server loads .env itself, you don't need to pass NWC_* vars through the client config — leave the env block empty.

Safety model

This server is designed for use by autonomous LLM agents that hold the keys to spend real sats. The defense in depth runs in this order on every spend tool call:

`NWC_READ_ONLY` gate — if set, blocks at the first gate. No decode, no network, audit log entry only.
Invoice decode + amount resolution — for bolt11-based tools. Rejects ambiguity (amount-override conflicting with embedded amount).
Allowlist check — if NWC_ALLOWED_DESTINATIONS is set, the payee (pubkey for bolt11, LN address for LUD-16, LNURL string for LUD-01, pubkey for keysend) must match. Empty allowlist = no-op.
Budget check — daily rolling cap + optional total cap + optional per-invoice cap. State is persisted to NWC_BUDGET_STATE_PATH.
Two-step confirmation gate — if NWC_REQUIRE_CONFIRM=true, returns a 16-byte hex token with 5-minute TTL instead of executing. Agent must call nwc_confirm_payment with the token. Safety re-runs on consume.
Execute — calls the wallet via NIP-47. On success: budget records principal + (over-rounded) fees.
Audit log — every attempt (success, blocked, error) is appended as one structured JSON line per call.

The floor is your NWC connection's own daily cap, set in your wallet. This server's checks are belt-and-suspenders on top — if you trust nothing about the server, the wallet still won't spend past its connection-level cap.

Verifying calls actually went through

Independent of what the LLM tells you, tail the audit log:

tail -n 5 nwc-mcp.log

Successful call: {"ts":"...","tool":"nwc_pay_invoice","outcome":"ok","result":{"paid_sats":50,...}}. Blocked: {"ts":"...","tool":"nwc_pay_invoice","outcome":"blocked","blocked_reason":"..."}. The audit log is append-only by intent; rotate it as part of your operational hygiene.

Testing

pnpm typecheck   # tsc --noEmit

pnpm test # 25 vitest cases covering Allowlist, ConfirmStore, evaluateSafety, decodeLnurl pnpm build # produces dist/index.js (~47 KB ESM bundle)

evaluateSafety is a pure function that the unit tests exercise across the full safety matrix (read-only / amount-conflict / allowlist / budget / confirm) without touching a real wallet.

For end-to-end smoke testing against a live wallet, see paywall-mcp-test/ in the parent project — a throwaway second MCP server that exposes one paid tool (premium_compliment) and validates the full agent → invoice → pay → redeem loop.

License

MIT — see LICENSE.

Contact / Issues

Built by LLMOps.Pro.

NOSTR: npub1hdg932jvwc3jdvkqywgqv0ue4nn60exrf92asy8mtazt3hjg7d2s2yw0nw — follow, DM, zap.
Lightning Address: sovereigncitizens@getalby.com — for support zaps and "this was useful" tips.
Bug reports / feature requests: open a GitHub issue (https://github.com/llmops-pro/nwc-mcp).
Security issues: please disclose privately via NOSTR DM before opening a public issue.

Nwc MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Aiterm MCP

README from the maker

nwc-mcp

What you can do with this

The twelve tools

Read-only (always enabled, no spend risk)

Receive (safe — only generates invoices, no spend)

Spend (gated by the safety pipeline)

Requirements

Install

From source

Configure

edit .env: NWC_CONNECTION_STRING=nostr+walletconnect://...

Required

Optional safety knobs

Wire into an MCP client

Claude Code (project-scoped, recommended)

Claude Desktop / Cursor / other clients

Safety model

Verifying calls actually went through

Testing

License

Contact / Issues