Skip to main content
Glama
llmops-pro

albyhub-admin-mcp

by llmops-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to albyhub-admin-mcp

No user-submitted related servers found.

    Related Servers

    • nwc-mcp

      llmops-pro
      A
      license
      A
      quality
      D
      maintenance
      MCP server exposing a Lightning wallet to LLM agents over Nostr Wallet Connect (NIP-47): balance, invoices, LN address/LNURL payments, batch pay, and keysend. All spend tools are wrapped in a defense-in-depth safety stack — budget caps, allowlist, two-step confirmation, audit log.
      13
      26 npm
      MIT

    • l402-kit-mcp

      ShinyDapps
      A
      license
      A
      quality
      C
      maintenance
      MCP server for l402-kit — enables AI agents (Claude, Cursor, etc.) to autonomously pay Bitcoin Lightning-protected APIs. Tools: l402_fetch, l402_balance, l402_spending_report. Run with: npx l402-kit-mcp
      4
      53 npm
      3
      MIT

    • Polar MCP Server

      jamaljsr
      A
      license
      Not graded
      quality
      C
      maintenance
      Model Context Protocol (MCP) server for Polar Lightning that enables AI assistants to manage Bitcoin Lightning Network test environments, including network creation, node management, Bitcoin operations, Lightning channel management, and Taproot Assets.
      10 npm
      7
      MIT

    • Nvoy

      JAFairweather
      A
      license
      Not graded
      quality
      A
      maintenance
      Scoped, revocable data delegation to agentic workflows over nostr, mounted as an MCP server.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: generic proxy, confirmation step, and specific typed wrappers for node info, balances, apps, and channels. The proxy_request tool is explicitly a fallback for endpoints without a dedicated wrapper, so there is no confusion about when to use it.

    Naming Consistency5/5

    All tools share the consistent 'albyhub_' prefix and follow a verb_noun pattern (proxy_request, confirm_request, get_node_info, get_balances, list_apps, list_channels). The naming is uniform and predictable.

    Tool Count5/5

    With 6 tools, the set is well-scoped for an admin API wrapper. The generic proxy plus a few convenient typed wrappers cover the domain without redundancy or clutter.

    Completeness5/5

    The inclusion of a generic proxy_request tool ensures that any endpoint of the Alby Hub admin API can be accessed, so there are no dead ends. The typed wrappers cover common operations, and the proxy fills any gaps, making the surface complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources