BoltHub MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Bolthub MCP aggregation sharing one Lightning wallet budget: Do routed external servers and marketplace calls respect the same scoped budget before payment?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

One Lightning budget for API marketplace calls, L402 gateways and proxied MCP servers.

What we know

Gateway/marketplace MCP that searches/executes paid APIs, wraps L402 gateways, pays challenged MCP calls within budget, and lets sellers draft/publish API listings. It supersedes older bolthub MCP registry/bridge packages.

Maintenance / activity evidence

@bolthub/mcp 0.7.2 published 2026-07-25T02:03:37.689Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Can make paid calls, buy credit, manage scoped tokens and marketplace listings. Writes: Spend Lightning budget on API/MCP calls; Buy credits; Mint/revoke tokens; Create/publish marketplace listings.
NWC wallet credential and optional account token.
Sensitive access: Wallet/NWC credential, Account token, API payloads, Seller revenue data

Real money/payment authority; enforce spending caps and protect wallet credentials.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do routed external servers and marketplace calls respect the same scoped budget before payment?

The bounded review of the publisher's documented Bolthub MCP aggregation sharing one Lightning wallet budget and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Real money/payment authority; enforce spending caps and protect wallet credentials.
Can make paid calls, buy credit, manage scoped tokens and marketplace listings.
NWC wallet credential and optional account token.
API requests, payment challenges and listing/account data pass through BoltHub.
Reviewed write actions: Spend Lightning budget on API/MCP calls; Buy credits; Mint/revoke tokens; Create/publish marketplace listings
Sensitive access: Wallet/NWC credential, Account token, API payloads, Seller revenue data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Requires NWC/Lightning budget for paid calls.
Account operations need BoltHub account token.
Can spend funds automatically within configured budget.
Publishing listings changes public marketplace state.

Original activity observations

@bolthub/mcp 0.7.2 published 2026-07-25T02:03:37.689Z

Technical identity

npm/@bolthub/mcp

Exact implementation source: https://www.npmjs.com/package/@bolthub/mcp ↗
Reviewed resource type: Gateway
Repository identity: signaltech-org/bolthub-sdk
Package identity: npm:@bolthub/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@bolthub/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Marketplace and L402 gateway orchestration; ~/.bolthub/mcp.json optional for shared nested MCP configuration. Previous mcp-registry and bridge superseded.
publisher install or stdio launch · Publisher instructions
npx -y @bolthub/mcp
Configure / authenticate
MCP100 setup guide
Use `npx @bolthub/mcp` and register it with the MCP host; it consolidates marketplace, registry and bridge functions. Remove old duplicate @bolthub/mcp-registry registrations rather than stacking both.
Previously reviewed client configuration / prerequisites: Its marketplace calls may require a Lightning payment budget/wallet; account-specific listing requires browser connect_account or BOLTHUB_ACCOUNT_TOKEN. Distinguish search_apis / preview_cost from pay-capable call_api / buy_credit.
Check connection
Suggested check
Use `search_apis`/`preview_cost` only, not `call_api`, `buy_credit` or deployment.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `bolthub-mcp`, run `claude mcp remove bolthub-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default. Also remove superseded `@bolthub/mcp-registry` registration only if it is separately installed.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove bolthub-mcp

Official Documentation & Sources

What it does

Gateway/marketplace MCP that searches/executes paid APIs, wraps L402 gateways, pays challenged MCP calls within budget, and lets sellers draft/publish API listings. It supersedes older bolthub MCP registry/bridge packages.

Capability: Finance & Payments
Resource type: Gateway
Industry: Financial Services & Investing
Best fit: One Lightning budget for API marketplace calls, L402 gateways and proxied MCP servers.

Representative uses

Search/inspect/call marketplace APIs
Preview cost and buy credits
Mint/revoke scoped tokens
Proxy/pay L402 MCP calls
Draft/audit/publish own API listing
Inspect earnings/usage

Limitations

Requires NWC/Lightning budget for paid calls.
Account operations need BoltHub account token.
Can spend funds automatically within configured budget.
Publishing listings changes public marketplace state.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: NWC wallet credential and optional account token.
Permissions: Can make paid calls, buy credit, manage scoped tokens and marketplace listings.
Data handling: API requests, payment challenges and listing/account data pass through BoltHub.
Cost: transactional
Risk and cautions: Real money/payment authority; enforce spending caps and protect wallet credentials.

Access scope and cautions

Write actions: Spend Lightning budget on API/MCP calls Buy credits Mint/revoke tokens Create/publish marketplace listings
Sensitive access: Wallet/NWC credential Account token API payloads Seller revenue data
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Search/inspect/call marketplace APIs; Preview cost and buy credits; Mint/revoke scoped tokens; Proxy/pay L402 MCP calls; Draft/audit/publish own API listing; Inspect earnings/usage.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @bolthub/mcp. Recorded transport: stdio. Recorded environment-variable notes: NWC_URI; BOLTHUB_ACCOUNT_TOKEN (optional seller/account actions). No configuration values are supplied here. Prerequisites: MCP client; Lightning/NWC wallet for paid use. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: NWC wallet connection for buying; optional browser pairing/account token for seller/account operations.

Can it modify data or perform write operations?

Documented write actions include: Spend Lightning budget on API/MCP calls; Buy credits; Mint/revoke tokens; Create/publish marketplace listings. Recorded permission boundary: Can make paid calls, buy credit, manage scoped tokens and marketplace listings.

What data-handling boundary should I consider?

API requests, payment challenges and listing/account data pass through BoltHub. Recorded sensitive-access context: Wallet/NWC credential; Account token; API payloads; Seller revenue data.

What limitations and risks should I check before use?

Real money/payment authority; enforce spending caps and protect wallet credentials. Requires NWC/Lightning budget for paid calls. Account operations need BoltHub account token. Can spend funds automatically within configured budget. Publishing listings changes public marketplace state. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is transactional. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.