Atlas / MCP servers / getalby / Alby Bitcoin Payments

Alby Bitcoin PaymentsSAFE

mcp/getalby/alby

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

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
11 10r · 1w · 0d
Transport
sse · stdio · streamable-http
License
Apache-2.0
Stars
66
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

NEW: also checkout Alby CLI for agents that don't support MCP.

Connect a bitcoin lightning wallet to your LLM using Nostr Wallet Connect (NWC).

This MCP server uses the official MCP TypeScript SDK

This MCP server has knowledge of NWC, LNURL and L402 using Alby SDK and Alby Lightning Tools.

Take a look at [Awesome AI Bitcoin](https://github.com/getAlby/awesome-ai-bitcoin) for places where you can use the Alby MCP.

Quick Start

In case you get stuck, see troubleshooting section below.

Use the Alby-Hosted MCP Server

If your agent supports remote MCP servers - SSE (e.g. N8N) or HTTP Streamable transports, you can connect to Alby's MCP server.

  • SSE: https://mcp.getalby.com/sse
  • HTTP Streamable: https://mcp.getalby.com/mcp

Authentication

Both require providing an NWC connection secret as authentication, either as Bearer authentication (preferred) or via the nwc query parameter.

Bearer Auth

Example: Authorization: Bearer nostr+walletconnect://...

If your agent UI supports bearer auth, just paste the connection secret into the bearer auth field.

Query Parameter

If your agent doesn't support bearer auth, you can pass the NWC connection secret as a query parameter.

Example: https://mcp.getalby.com/sse?nwc=ENCODED_CONNECTION_SECRET or https://mcp.getalby.com/mcp?nwc=ENCODED_CONNECTION_SECRET

To get ENCODEDCONNECTION_SECRET, open browser devtools (right click -> inspect) and enter this in the console, with your own NWC

Read from source at commit d9fe01dca208OBSERVED · 2026-10-07
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add mcp -- npx -y @getalby/[email protected]
claude-desktop
{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@getalby/[email protected]"
      ]
    }
  }
}
03

Exposed tools (11)

10 read · 1 write · 0 destructive.

ToolRiskDescription
fetch_l402read
fiat_to_satsread
get_balanceread
get_inforead
get_wallet_service_inforead
list_transactionsread
lookup_invoiceread
make_invoiceread
parse_invoiceread
pay_invoicewrite
request_invoiceread
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (1 observation(s))
Network
declared (1 observation(s))
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (3)

LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/tools/lightning/fetch_l402.ts:5
import { assertPublicUrl } from "../../security.js";
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@getalby/lightning-tools, @getalby/sdk, @modelcontextprotocol/sdk, @types/node, dotenv, express, ipaddr.js, typescript
Why it matters. 9 dependency range(s) float
Fix. pin exact versions or ship a lockfile
LOWPrompt injection · prompt.transfer_instruction · CWE-94, CWE-1427
README.md:209
The HTTP endpoints only accept requests whose `Host` header is allowlisted. Requests from browsers (carrying an `Origin` header) are refused; MCP clients that aren't browsers don't send one. `fetch_l4
Why it matters. an instruction to move sensitive data to an outside destination
Fix. remove; a skill never needs the user's secrets off the machine

Gates applied: no_behavioural_pass.

Audited 2026-10-07 · audit v0.4.1 · source sha d9fe01dca208full audit observations/trust-audit/mcp-server/getalby__alby.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-07d9fe01dca208SAFEB89first audit
06

Questions

What is the Alby Bitcoin Payments MCP server?

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

What tools does Alby Bitcoin Payments expose?

11 in total: 10 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Alby Bitcoin Payments safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Alby Bitcoin Payments need?

No credential environment variables were found in its source, so it appears to need none.

How does Alby Bitcoin Payments run?

It speaks sse, stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as @getalby/mcp at 1.1.2.

How current is this page?

The grade is for one exact copy of the source (d9fe01dca208), read on 2026-10-07. The repository is watched and re-audited when it changes.

Advertisement