Server data from the Official MCP Registry
Discover and call every paid API on the bolthub marketplace with automatic L402 Lightning payments.
Discover and call every paid API on the bolthub marketplace with automatic L402 Lightning payments.
Valid MCP server (2 strong, 2 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
14 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: LND_REST_HOST
Environment variable: LND_MACAROON
Environment variable: NWC_URI
Environment variable: LNBITS_URL
Environment variable: LNBITS_ADMIN_KEY
Environment variable: PHOENIXD_URL
Environment variable: PHOENIXD_PASSWORD
Environment variable: BUDGET_SATS
Environment variable: BOLTHUB_AUTH_TOKEN
Add this to your MCP configuration file:
{
"mcpServers": {
"ai-bolthub-registry": {
"env": {
"NWC_URI": "your-nwc-uri-here",
"LNBITS_URL": "your-lnbits-url-here",
"BUDGET_SATS": "your-budget-sats-here",
"LND_MACAROON": "your-lnd-macaroon-here",
"PHOENIXD_URL": "your-phoenixd-url-here",
"LND_REST_HOST": "your-lnd-rest-host-here",
"LNBITS_ADMIN_KEY": "your-lnbits-admin-key-here",
"PHOENIXD_PASSWORD": "your-phoenixd-password-here",
"BOLTHUB_AUTH_TOKEN": "your-bolthub-auth-token-here"
},
"args": [
"-y",
"@bolthub/mcp-registry"
],
"command": "npx"
}
}
}From the project's GitHub README.
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/agentmerged into@bolthub/pay(≥0.4.0);@bolthub/mcp-registryand@bolthub/mcp-bridgemerged into@bolthub/mcp. The old names are deprecated on npm and point here.
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.
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.
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).
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.