$ loading_
Safely let an agent manage Alby Hub Lightning node info, balances, and channels.
This MCP tool is intended for administering an Alby Hub Lightning node and requires management-related URL/token credentials, with normal code-execution and node administration capabilities. Given its official registry presence, open-source code, and recent maintenance, it fits a caution rating rather than high risk; the provided materials show no clear red flags such as exfiltration to unrelated third parties or obvious overreach.
It requires ALBYHUB_URL, ALBYHUB_TOKEN, and ALBYHUB_READ_ONLY; ALBYHUB_TOKEN is a sensitive administrative credential that could be abused to read node data or perform management writes when not configured as read-only. The README is missing, and the materials do not describe credential storage, least-privilege controls, or rotation practices.
No fixed remote host is declared, but the presence of ALBYHUB_URL indicates it will connect to a user-configured Alby Hub instance for node query/administration requests. The materials do not show evidence of sending data to unrelated third-party endpoints, but the configurable URL means the actual request target and transmitted data should still be verified.
The system flags it as executes-code, meaning the MCP has the normal ability to run locally as a service/process. Based on the stated function, this execution capability is likely used to interact with the Alby Hub API; the materials do not show requests for system privileges that clearly exceed node administration needs.
By description, it can access node information, balances, channels, and perform safety-gated write operations; this falls within its stated functional scope. The materials do not indicate broad local file read/write access, but administration of a Lightning node is inherently sensitive business access, so read-only mode should be preferred where possible.
It comes from an official registry and has an auditable open-source repository with updates in the past year, all of which are positive risk-reducing signals. On the other hand, the missing README, undeclared license, and very low community adoption (0 stars) limit auditability and ecosystem validation, so a caution rating is more appropriate.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "io.github.llmops-pro/albyhub-admin-mcp" MCP server from askskill: Run: claude mcp add 'io-github-llmops-pro-albyhub-admin-mcp' -- npx -y albyhub-admin-mcp
Connect to the Alby Hub admin interface, read the current Lightning node's basic info, on-chain and channel balances, and active channel count, then summarize any anomalies in English.
A node overview, balance details, channel stats, and a summary of issues needing attention.
List all channels with capacity, local and remote liquidity, status, and recent activity, then flag channels that may need rebalancing or closure and explain why.
A channel health report with risk flags and optimization recommendations.
Before any write action, show the planned changes and risk notes; if I confirm, proceed with the requested channel management action and return the result.
First, a confirmation-ready action plan; after approval, the actual execution result and status feedback.
Enable no-KYC web search for AI agents with pay-per-query Lightning access.
Connect AI agents to a Lightning wallet with budgets, approvals, and audit logs.
Enable AI agents to safely publish, query, and send DMs on Nostr.
Buy inbound Lightning liquidity for a node through Amboss Magma automatically.
Enable AI agents to fully manage an RGB Lightning wallet and payments.
Enable AI coding agents to exchange messages across machines and sessions.