English Français العربية

bolthub

Registre officiel E-commerce

The bolthub API marketplace, L402 gateways, and your other MCP servers, on one Lightning budget.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @bolthub/mcp
Claude Code 
claude mcp add bolthub -e 'LND_REST_HOST=<LND_REST_HOST>' -e 'LND_MACAROON=<your lnd_macaroon>' -e 'NWC_URI=<your nwc_uri>' -e 'LNBITS_URL=<LNBITS_URL>' -e 'LNBITS_ADMIN_KEY=<your lnbits_admin_key>' -e 'PHOENIXD_URL=<PHOENIXD_URL>' -e 'PHOENIXD_PASSWORD=<your phoenixd_password>' -e 'BUDGET_SATS=<BUDGET_SATS>' -e 'BOLTHUB_ACCOUNT_TOKEN=<your bolthub_account_token>' -- npx -y @bolthub/mcp@0.7.2
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "bolthub": {
            "command": "npx",
            "args": [
                "-y",
                "@bolthub/mcp@0.7.2"
            ],
            "env": {
                "LND_REST_HOST": "<LND_REST_HOST>",
                "LND_MACAROON": "<your lnd_macaroon>",
                "NWC_URI": "<your nwc_uri>",
                "LNBITS_URL": "<LNBITS_URL>",
                "LNBITS_ADMIN_KEY": "<your lnbits_admin_key>",
                "PHOENIXD_URL": "<PHOENIXD_URL>",
                "PHOENIXD_PASSWORD": "<your phoenixd_password>",
                "BUDGET_SATS": "<BUDGET_SATS>",
                "BOLTHUB_ACCOUNT_TOKEN": "<your bolthub_account_token>"
            }
        }
    }
}

Variables d'environnement

  • LND_REST_HOST LND REST API URL (recommended wallet; pair with LND_MACAROON). A wallet is optional — without one, free tools and marketplace search still work; paid calls return their payment challenge.
  • LND_MACAROON secret Hex-encoded macaroon for LND (use a pay-scoped macaroon in production). Required with LND_REST_HOST.
  • NWC_URI secret Nostr Wallet Connect string — easiest setup, works with CoinOS, Alby Hub, Zeus, and more. Alternative to LND.
  • LNBITS_URL LNbits instance URL (pair with LNBITS_ADMIN_KEY). Alternative wallet.
  • LNBITS_ADMIN_KEY secret Admin API key for LNbits. Required with LNBITS_URL.
  • PHOENIXD_URL Phoenixd HTTP API URL (pair with PHOENIXD_PASSWORD). Alternative wallet.
  • PHOENIXD_PASSWORD secret HTTP password for Phoenixd. Required with PHOENIXD_URL.
  • BUDGET_SATS Maximum sats the server may spend per session (process lifetime), across ALL sources. Unset = unlimited; 0 = free tools only. The config file's budget.sat takes precedence.
  • BOLTHUB_ACCOUNT_TOKEN secret Account token for tools that act on YOUR bolthub account (workspace, listing, audit, earnings, and node tools). Optional even for those: the connect_account tool pairs via the browser instead. Never needed to discover, call, or pay for APIs — buying is account-less.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. bolthub SDK
  2. Relationship to the bolthub platform
  3. Verifying what you install
  4. Development
  5. License

bolthub SDK

Source code for every publicly published bolthub.ai package: the npm @bolthub/* scope and the bolthub / bolthub-verify PyPI packages.

bolthub is a payment layer for agent-to-tool commerce: charge agents for your MCP tools and APIs per call, settling straight to your wallet over Lightning (L402), with bolthub never in the funds path. These packages are the open-source side of that: the tool-payment SDK, payment clients, MCP servers, a CLI, and origin-verification middleware.

PackageRegistryDirectoryWhat it is
@bolthub/paynpmpackages/payThe payments SDK, both sides: price an MCP tool or HTTP endpoint (createPaywall), pay for tools within a budget (ToolClient for MCP, L402Client for HTTP), wallet adapters (LND, LNbits, Phoenixd, NWC, WebLN); rails: L402, facilitator. Zero runtime dependencies
@bolthub/mcpnpmpackages/mcpThe bolthub MCP server: marketplace + specific gateways + your other MCP servers behind one config entry, with one shared Lightning budget
@bolthub/clinpmpackages/cliTerminal client for the marketplace
@bolthub/verifynpmpackages/verifyGateway signature verification middleware (Express/Fastify/Node)
bolthubPyPIpackages/agent-pythonThe payments SDK in Python: L402 client + wallets, and the seller-side paywall
bolthub-verifyPyPIpackages/verify-pythonPython gateway signature verification (Flask/Django/FastAPI)

packages/shared is internal (never published); it is here because @bolthub/mcp bundles it.

Consolidation (2026-07): @bolthub/agent merged into @bolthub/pay (≥0.4.0); @bolthub/mcp-registry and @bolthub/mcp-bridge merged into @bolthub/mcp. The old names are deprecated on npm and point here.

Relationship to the bolthub platform

The bolthub platform (gateway, API, web app) lives in a private monorepo. The SDK packages above are developed there and synced to this repository, which is the publish origin: releases are tagged here and built + published by CI with npm provenance, so what's on npm is verifiably built from this public source.

Issues and PRs are welcome here, but note that this repo is a generated mirror: PRs are never merged directly. Accepted changes are applied to the monorepo first (with attribution), then sync back out with the next release. See CONTRIBUTING.md before opening a PR.

Verifying what you install

Published dist/ bundles are built with Bun from this source and ship source maps with embedded sources, so the tarball itself is readable.

# provenance: confirm the tarball was built from this repo by GitHub Actions
npm audit signatures

# or rebuild and compare yourself
git clone https://github.com/signaltech-org/bolthub-sdk
cd bolthub-sdk && bun install
cd packages/mcp && bun run build

See SECURITY.md for the trust model (what touches your wallet credentials and what doesn't) and how to report vulnerabilities.

Development

bun install
bun test

Each TypeScript package builds with bun run build from its directory (@bolthub/pay must be built before the packages that bundle it).

License

MIT

Questions fréquentes

Qu'est-ce que bolthub ?

The bolthub API marketplace, L402 gateways, and your other MCP servers, on one Lightning budget.

Comment installer bolthub ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add bolthub -e 'LND_REST_HOST=<LND_REST_HOST>' -e 'LND_MACAROON=<your lnd_macaroon>' -e 'NWC_URI=<your nwc_uri>' -e 'LNBITS_URL=<LNBITS_URL>' -e 'LNBITS_ADMIN_KEY=<your lnbits_admin_key>' -e 'PHOENIXD_URL=<PHOENIXD_URL>' -e 'PHOENIXD_PASSWORD=<your phoenixd_password>' -e 'BUDGET_SATS=<BUDGET_SATS>' -e 'BOLTHUB_ACCOUNT_TOKEN=<your bolthub_account_token>' -- npx -y @bolthub/mcp@0.7.2. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour bolthub ?

Oui. Il attend LND_MACAROON, NWC_URI, LNBITS_ADMIN_KEY, PHOENIXD_PASSWORD, BOLTHUB_ACCOUNT_TOKEN, à renseigner dans sa configuration.

bolthub est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient bolthub ?

Il est publié par signaltech-org. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.