Server data from the Official MCP Registry
Admin an Alby Hub Lightning node from an agent: info, balances, channels; safety-gated writes.
Admin an Alby Hub Lightning node from an agent: info, balances, channels; safety-gated writes.
This MCP server implements a thoughtful safety model with multiple layers of protection for accessing an Alby Hub admin API. The code is well-structured with proper authentication via bearer tokens, rate limiting, optional confirmation gates, and comprehensive audit logging. Minor code quality issues around error handling breadth and input validation do not significantly impact security, as the server's permissions (network access to a configured Hub instance) align appropriately with its purpose as a developer tool. Supply chain analysis found 5 known vulnerabilities in dependencies (2 critical, 2 high severity). Package verification found 1 issue.
7 files analyzed · 11 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: ALBYHUB_URL
Environment variable: ALBYHUB_TOKEN
Environment variable: ALBYHUB_READ_ONLY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-llmops-pro-albyhub-admin-mcp": {
"env": {
"ALBYHUB_URL": "your-albyhub-url-here",
"ALBYHUB_TOKEN": "your-albyhub-token-here",
"ALBYHUB_READ_ONLY": "your-albyhub-read-only-here"
},
"args": [
"-y",
"albyhub-admin-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Node-admin operations on your Alby Hub, exposed to an LLM agent. MCP server that wraps the Alby Hub HTTP API — read node info, balances, channels, NWC sub-wallets. Where NWC (nwc-mcp) ends (it's wallet-scoped), this server picks up: hub-wide on-chain balance, channel state, sub-wallet inventory.
v0.1 — defensive design. Alby Hub's admin API has evolved across versions and isn't publicly versioned in a stable way. So v0.1 ships one generic proxy tool that hits any path (the escape hatch) plus typed wrappers around a few well-established endpoints. If a typed wrapper's endpoint-guess fails against your Hub version, the proxy lets you discover the right path without re-shipping. v0.2 hardens the typed wrappers once smoke-tested against real Hubs.
| Tool | Method | Path | Purpose |
|---|---|---|---|
albyhub_proxy_request | * | * | Generic HTTP proxy — escape hatch for any endpoint not yet wrapped. |
albyhub_confirm_request | * | * | Two-step confirm dispatcher for proxy_request. |
albyhub_get_node_info | GET | /api/info | Node identity, network, version. |
albyhub_get_balances | GET | /api/balances | On-chain + Lightning aggregate balances. |
albyhub_list_apps | GET | /api/apps | NWC connections (sub-wallets) provisioned on this hub. |
albyhub_list_channels | GET | /api/channels | Lightning channels with status + capacities. |
All typed wrappers are safe GETs. Non-GET behavior runs through albyhub_proxy_request, which is gated by ALBYHUB_READ_ONLY and ALBYHUB_REQUIRE_CONFIRM.
http://localhost:8080, or self-hosted exposed somewhere)npx -y albyhub-admin-mcp
cp .env.example .env
# edit .env: set ALBYHUB_URL (default http://localhost:8080) + ALBYHUB_TOKEN
| Var | Purpose |
|---|---|
ALBYHUB_URL | Base URL of your Hub. Default http://localhost:8080. Use HTTPS if exposed remotely. |
ALBYHUB_TOKEN | API access token. Full-scope tokens can drain the hub's on-chain balance — scope down or use ALBYHUB_READ_ONLY=true if your audience matters. |
| Var | Default | Purpose |
|---|---|---|
ALBYHUB_READ_ONLY | false | Refuse all non-GET requests via proxy_request. Strongly recommended for first-time setup. |
ALBYHUB_REQUIRE_CONFIRM | false | Two-step confirm for non-GET requests. |
ALBYHUB_MAX_REQUESTS_PER_MINUTE | 30 | Rolling 60s rate limit. |
ALBYHUB_LOG_PATH | ./albyhub-admin-mcp.log | Server log. |
ALBYHUB_AUDIT_PATH | ./albyhub-admin-mcp-audit.log | Append-only JSON-line audit log. |
The endpoint path probably differs in your Hub version. Use albyhub_proxy_request to probe — try /api/node, /info, /api/v1/info, etc. Once you find the right path, you can pin it in your usage (and ping the maintainer to fix the typed wrapper in v0.2).
agent: albyhub_proxy_request({ method: "GET", path: "/api/v1/info" })
→ { status: 200, body: { ... } } // found it
The proxy tool's pipeline:
ALBYHUB_READ_ONLY gate — non-GET requests blocked outright.requests bucket.ALBYHUB_REQUIRE_CONFIRM gate — non-GET requests return a token; albyhub_confirm_request executes.timeout_ms).GET-only convenience wrappers skip steps 1 + 3 (they're safe by construction) but still go through rate limit + audit.
nwc-mcp — wallet ops via NIP-47. Use this for per-sub-wallet spend; use albyhub-admin-mcp for hub-wide / node-level operations.nostr-ops-mcp — NOSTR identity + publishing.marketplace-mcp — NIP-15 marketplace storefront.MIT — see LICENSE.
Built by LLMOps.Pro.
npub1hdg932jvwc3jdvkqywgqv0ue4nn60exrf92asy8mtazt3hjg7d2s2yw0nw — follow, DM, zap.sovereigncitizens@getalby.com — for support zaps and "this was useful" tips.Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.