Was kannst du mit bolthub machen?

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.

Package	Registry	Directory	What it is
`@bolthub/pay`	npm	`packages/pay`	The 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/mcp`	npm	`packages/mcp`	The bolthub MCP server: marketplace + specific gateways + your other MCP servers behind one config entry, with one shared Lightning budget
`@bolthub/cli`	npm	`packages/cli`	Terminal client for the marketplace
`@bolthub/verify`	npm	`packages/verify`	Gateway signature verification middleware (Express/Fastify/Node)
`bolthub`	PyPI	`packages/agent-python`	The payments SDK in Python: L402 client + wallets, and the seller-side paywall
`bolthub-verify`	PyPI	`packages/verify-python`	Python 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

Installation

bolthub zu deinem Client hinzufügen. Wähl den, den du nutzt.

claude mcp add mcp -- npx -y @bolthub/mcp

codex mcp add mcp -- npx -y @bolthub/mcp

amp mcp add mcp -- npx -y @bolthub/mcp

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bolthub/mcp"
      ]
    }
  }
}

Add to `claude_desktop_config.json`, then restart Claude Desktop.

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bolthub/mcp"
      ]
    }
  }
}

Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.

code --add-mcp '{"name":"mcp","command":"npx","args":["-y","@bolthub/mcp"]}'

Or add the block manually to `.vscode/mcp.json` under `servers`.

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bolthub/mcp"
      ]
    }
  }
}

Add to `~/.codeium/windsurf/mcp_config.json`.

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bolthub/mcp"
      ]
    }
  }
}

Add to `cline_mcp_settings.json` via the MCP Servers panel.

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bolthub/mcp"
      ]
    }
  }
}

Add to `~/.gemini/settings.json`.

{
  "mcpServers": {
    "mcp": {
      "type": "local",
      "command": "npx",
      "args": [
        "-y",
        "@bolthub/mcp"
      ],
      "tools": [
        "*"
      ]
    }
  }
}

Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.

{
  "context_servers": {
    "mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@bolthub/mcp"
        ]
      }
    }
  }
}

Add to your Zed `settings.json`.

npx -y @bolthub/mcp

Run `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.

Score

39 / 100

Unvollständig

Dokumentation22/25
Pflege22/25
Vertrauen16/20
Funktionsumfang0/15
Installation12/15

Documents what it does and how to connect
Has a resolvable package or endpoint
Exposes at least one tool, prompt or resource
README has substantive content
Includes a code example
Documents its configuration
Mentions credentials or security posture
Last commit 38 days ago
Has a release history
Repository is not archived
Licensed MIT
Namespace verified in the official MCP registry
Claimed by its owner
Published under an organisation
0 tool(s) documented
Provides prompt templates
Provides resources
12 documented install method(s)
Published to a package registry
Offers a hosted endpoint — no local install

Vollständige Kriterien lesen →

Versionsverlauf

Versionen	Veröffentlicht
0.7.2Aktuell	25. Juli 2026
0.7.1	24. Juli 2026
0.7.0	24. Juli 2026
0.6.0	21. Juli 2026
0.5.2	15. Juli 2026
0.5.1	15. Juli 2026
0.4.0	10. Juli 2026
0.3.0	10. Juli 2026
0.2.1	10. Juli 2026
0.2.0	10. Juli 2026
0.1.0	7. Juli 2026