Alby Bitcoin PaymentsSAFE
Connect a bitcoin lightning wallet to your LLM using Nostr Wallet Connect and Model Context Protocol
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
d9fe01dca208OBSERVED · 2026-10-07Connect
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 mcp add mcp -- npx -y @getalby/[email protected]
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@getalby/[email protected]"
]
}
}
}Exposed tools (11)
10 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
fetch_l402 | read | |
fiat_to_sats | read | |
get_balance | read | |
get_info | read | |
get_wallet_service_info | read | |
list_transactions | read | |
lookup_invoice | read | |
make_invoice | read | |
parse_invoice | read | |
pay_invoice | write | |
request_invoice | read |
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.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (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)
import { assertPublicUrl } from "../../security.js";@getalby/lightning-tools, @getalby/sdk, @modelcontextprotocol/sdk, @types/node, dotenv, express, ipaddr.js, typescript
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
Gates applied: no_behavioural_pass.
d9fe01dca208full audit observations/trust-audit/mcp-server/getalby__alby.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | d9fe01dca208 | SAFE | B | 89 | first audit |
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.