MCP.Market

Albyhub Admin MCP server

by llmops-pro·io.github.llmops-pro/albyhub-admin-mcp·v0.1.2
No reviews yet

Admin an Alby Hub Lightning node from an agent: info, balances, channels; safety-gated writes.

B71/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B71/100

full report

Adoption
New

0 stars37 downloads/wk

Reviews

Write one

Nobody has reviewed Albyhub Admin yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Albyhub Admin tools (6, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • albyhub_confirm_requestwrite action

    Execute a previously-prepared non-GET request, identified by its one-time token. Only meaningful when ALBYHUB_REQUIRE_CONFIRM=true. The token is consumed (single use) and the safety pipeline (read-only, rate limit) re-runs before the HTTP call.

  • albyhub_get_balances

    Fetch hub balances (on-chain + lightning) from GET /api/balances. Distinct from nwc_get_balance \u2014 that one is a single sub-wallet's view via NWC; this one is the hub-wide aggregate including on-chain. If your Hub returns 404, probe with albyhub_proxy_request.

  • albyhub_get_node_info

    Fetch Alby Hub node info (identity, network, version) from GET /api/info. Convenience wrapper. If your Hub returns 404 here, the endpoint path differs in your version \u2014 use albyhub_proxy_request to probe alternatives like /api/node or /info.

  • albyhub_list_apps

    List NWC connections / sub-wallets ('apps') currently provisioned on the Hub. Each entry typically includes name, pubkey, scope, daily budget, and creation timestamp. Hits GET /api/apps. Use this to inventory what's connected to your Hub and what each connection's budget cap is.

  • albyhub_list_channels

    List Lightning channels \u2014 typically peer pubkey, capacity, local/remote balance, public/private flag, online status. Hits GET /api/channels. The hub-wide view (vs. nwc-mcp which has no channel concept). Useful for spotting offline channels, low inbound, etc.

  • albyhub_proxy_request

    Generic HTTP proxy to your Alby Hub admin API. Use this when no typed convenience tool exists for the endpoint you need. Returns the response status, headers, and (JSON-parsed when possible) body. Non-GET methods are gated by ALBYHUB_READ_ONLY and ALBYHUB_REQUIRE_CONFIRM. Pair with the Hub's own docs to discover endpoints; the typed wrappers (get_node_info, list_apps, get_balances) are layered on

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 104 days ago8/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Albyhub Admin compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
71/100
higher than 38% of 4,460 AI and agents servers
Tools
6
the typical AI and agents server has 6
Tools that change things
17%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
37
more than 28% of 1,538 AI and agents servers with a package

What its tools let an agent do: 5 read · 1 change

Install Albyhub Admin in Claude Code, Cursor or VS Code

Runs npx -y albyhub-admin-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add albyhub-admin-mcp -- npx -y albyhub-admin-mcp
Add to Cursor

What the publisher says

From the Albyhub Admin repository's README, as published. We do not edit it. Read it on GitHub

albyhub-admin-mcp

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.

The six tools

All typed wrappers are safe GETs. Non-GET behavior runs through albyhubproxyrequest, which is gated by ALBYHUBREADONLY and ALBYHUBREQUIRECONFIRM.

Requirements

  • Node 20+
  • A running Alby Hub instance (desktop app on http://localhost:8080, or self-hosted exposed somewhere)
  • An Alby Hub API token (Settings → Developer / Apps in the Hub UI)

Install

npx -y albyhub-admin-mcp

Configure

cp .env.example .env
# edit .env: set ALBYHUB_URL (default http://localhost:8080) + ALBYHUB_TOKEN

Required

Optional safety knobs

What if my Hub returns 404 on the typed wrappers?

The endpoint path probably differs in your Hub version. Use albyhubproxyrequest 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

Safety model

The proxy tool's pipeline:

  1. ALBYHUBREADONLY gate — non-GET requests blocked outright.
  2. Rate limit — rolling 60s window on the requests bucket.
  3. ALBYHUBREQUIRECONFIRM gate — non-GET requests return a token; albyhubconfirmrequest executes.
  4. HTTP request — Bearer auth, 15s timeout (override via timeout_ms).
  5. Audit log — every attempt (ok / blocked / error) as one structured JSON line.

GET-only convenience wrappers skip steps 1 + 3 (they're safe by construction) but still go through rate limit + audit.

Companion servers

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Albyhub Admin: common questions

Is Albyhub Admin MCP server safe?
Mostly: it is graded B (71/100). Read the Albyhub Admin safety report
How do I install Albyhub Admin?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Albyhub Admin need an API key?
Yes. The registry entry asks for ALBYHUB_TOKEN.
Is Albyhub Admin maintained?
The last commit was 142 days ago (2026-06-15). The latest release is v0.1.2.
What can I use instead of Albyhub Admin?
Servers from other publishers that do the same job: three.ws Portfolio MCP server, Vibe Check MCP server and Shellward MCP server.
How does Albyhub Admin compare with other AI and agents MCP servers?
safety score 71/100 (higher than 38% of 4,460 AI and agents servers); tools 6 (the typical AI and agents server has 6); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Albyhub Admin

Same job from other publishers: the closest match first, then the best rated.

  • three.ws Portfolio
    An agent's trading state — portfolio value, PnL, live balances, trade feed, and signed transfers.
    B
  • Vibe Check
    Metacognitive AI agent oversight: adaptive CPI interrupts for alignment, reflection and safety
    B
  • Shellward
    AI agent security: 7 MCP tools for injection detection, PII scanning, command safety, DLP.
    A

More from llmops-pro →