Enterprise DNAEnterprise DNA

MCP Servers

getalby/nwc-mcp-server

Connect a bitcoin lightning wallet to your LLM using Nostr Wallet Connect and Model Context Protocol

Our verdict

Not reviewed yet

We have not reviewed getalby/nwc-mcp-server yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About getalby/nwc-mcp-server

A lightweight server that links a Bitcoin Lightning wallet to an LLM through Nostr Wallet Connect and the Model Context Protocol. It enables AI agents to make payments and query wallet balances over the Lightning Network.

Best for

Developers building AI agents that need to send or receive small Bitcoin payments

Use cases

  • Enable an LLM to send micropayments for API calls or services
  • Check wallet balance or transaction history via natural language
  • Automate Lightning tipping or pay-per-request workflows in agents

Notes

14 stars on GitHub. Last updated 2025-06-20.

Pros

  • Direct integration between MCP agents and real Bitcoin payments
  • Small codebase (TypeScript) easy to audit or extend
  • Leverages open, decentralized Nostr protocol for wallet control

Cons

  • Requires an Alby or compatible Lightning wallet already set up
  • Very early stage with only 14 stars and limited community support
  • Dependent on Nostr infrastructure which adds latency and complexity

Key facts

What we have checked

Days since the last commit
515
Checked GitHub
GitHub forks
8
Checked GitHub
GitHub stars
15
Checked GitHub
Open issues
0
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true npx n8n

Clients the listing names (not checked here)

Claude Desktop, Cline

Example client config

{
  "mcpServers": {
    "nwc": {
      "command": "npx",
      "args": [
        "-y",
        "@getalby/nwc-mcp-server"
      ],
      "env": {
        "NWC_CONNECTION_STRING": "YOUR NWC CONNECTION STRING HERE"
      }
    }
  }
}

Install

Add getalby/nwc-mcp-server to your client

Not verified yet

No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.

Until then, follow the project's own README, or the setup the listing publishes under How to set it up.

Works with

What getalby/nwc-mcp-server connects to

No confirmed connections yet. A product appears here when the server's registry name, repo, homepage or name ties it to that product, and a client appears when we have an install recipe for it.

Stars and usage

How getalby/nwc-mcp-server is growing

GitHub stars

15 to 15

stars. 28 Oct 2026 to 17 Nov 2026, 4 readings.

Source: GitHub. Checked .

Health and security

Is getalby/nwc-mcp-server looked after, and what do its setup files show

Health score

0 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Archived0Repository is archived

Security check static checks

87 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1 npm:@getalby/nwc-mcp-server@1.1.0. What it checks

  • Medium The repository has no licence file, so nobody has been granted the right to use, copy or change the code.
  • Low The documented install uses n8n, whose published metadata points at github.com/n8n-io/n8n, not this repository. Check it is the right package before installing.
  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.
Tool permissions (2)
  • N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE, environment variable it asks for
  • NWC_CONNECTION_STRING, environment variable it asks for

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

  1. Shut down

    Source: GitHub

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.