bolthub Marketplace — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor exact implementation activity, MCP interface, permission and setup changes.

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

Best fit

Bolthub paid API discovery and invocation

What we know

Discover and call every paid API on the bolthub marketplace with automatic L402 Lightning payments. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Maintenance / activity evidence

npm exact package downloads 292 in 2026-09-09..2026-10-08

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
L402 Lightning payments can incur real costs; set explicit budgets and wallet limits. Reported action classes: paid API invocation. Complete write authority is not verified.
Lightning wallet LND or NWC; configure spend budget
Sensitive access: wallet/payment credentials and API calls

L402 Lightning payments can incur real costs; set explicit budgets and wallet limits.
Public tracking suitability is not an installation safety audit.

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

Popularity

· 292 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @bolthub/mcp-registry; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T03:38:00Z.

All limitations / Review context

Has bolthub Marketplace changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?

Limited editorial listing; known permission implications disclosed, no independently established publication blocker.

L402 Lightning payments can incur real costs; set explicit budgets and wallet limits.
Public tracking suitability is not an installation safety audit.
Lightning wallet LND or NWC; configure spend budget
wallet/payment credentials and API calls
Reviewed write actions: paid API invocation
Sensitive access: wallet/payment credentials and API calls
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Upstream credential and permission scopes must be validated before runtime use.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Dated package download count is usage signal, not necessarily a current maintenance release.

Original activity observations

npm exact package downloads 292 in 2026-09-09..2026-10-08

Technical identity

npm/@bolthub/mcp-registry

Exact implementation source: https://www.npmjs.com/package/@bolthub/mcp-registry ↗
Reviewed resource type: MCP Server
Package identity: npm:@bolthub/mcp-registry

Evidence & Sources

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

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@bolthub/mcp-registry
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Old npm identity is deprecated; replacement @bolthub/mcp is a separate npm identity.
Wallet settings unchanged but payments carry financial risk; set explicit BUDGET_SATS limit and use least-privilege Lightning wallet.
Remove old entry rather than registering both.
Migration command targets replacement npm identity; old identity must remain in Radar metadata.
Publisher README config reproduced as MCP100 structured data; requires real credentials and may require separately installed or built server. Not runtime tested.
Prior reviewed safety note: Do not conflate the two npm identities or silently migrate existing users.
Prior reviewed safety note: Only verify registration/tool list and preview_cost; avoid buy_credit or other paid Lightning operations.
Prior reviewed safety note: Do not invent a one-line reversal command.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.

Install / connect
Publisher instructions
DEPRECATED identity: official migration specifies replace npx @bolthub/mcp-registry with npx @bolthub/mcp. Wallet env vars and BUDGET_SATS persist; remove old client entry instead of stacking both.
publisher documented install or registration · Publisher instructions
npx -y @bolthub/mcp
Configure / authenticate
MCP100 setup guide
Publisher states `npx @bolthub/mcp-registry` works, but recommends `npx @bolthub/mcp` as newer consolidated replacement. Register only one of the two to avoid duplicate tools.
Previously reviewed client configuration / prerequisites: LND_MACAROON, NWC_URI, LNBITS_ADMIN_KEY and PHOENIXD_PASSWORD are optional wallet adapter secrets.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "bolthub": { "args": [ "-y", "@bolthub/mcp" ], "command": "npx" } } }
Check connection
Suggested check
Use `search_apis`/`preview_cost` for read-only validation; do not trigger paid APIs.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `bolthub-mcp-registry`, run `claude mcp remove bolthub-mcp-registry`; 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. Prefer consolidating on @bolthub/mcp only after removing this duplicate host entry.
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-registry

Official Documentation & Sources

What it does

Discover and call every paid API on the bolthub marketplace with automatic L402 Lightning payments. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Capability: Finance & Payments
Resource type: MCP Server
Best fit: Bolthub paid API discovery and invocation

Representative uses

Bolthub paid API discovery and invocation

Limitations

L402 Lightning payments can incur real costs; set explicit budgets and wallet limits.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Dated package download count is usage signal, not necessarily a current maintenance release.

Reviewed access

Access & risk

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

Authentication: Lightning wallet LND or NWC; configure spend budget
Permissions: L402 Lightning payments can incur real costs; set explicit budgets and wallet limits.
Data handling: wallet/payment credentials and API calls
Cost: Provider or usage fees possible; verify current pricing
Risk and cautions: L402 Lightning payments can incur real costs; set explicit budgets and wallet limits.

Access scope and cautions

Write actions: Not verified paid API invocation
Sensitive access: wallet/payment credentials and API calls
Risk level: high
Security notes: L402 Lightning payments can incur real costs; set explicit budgets and wallet limits. Public tracking suitability is not an installation safety audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Bolthub paid API discovery and invocation.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Installation command omitted unless verified or clearly package-specific; do not infer npx/uvx entrypoints. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Lightning wallet LND or NWC; configure spend budget

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: paid API invocation. Recorded permission context: L402 Lightning payments can incur real costs; set explicit budgets and wallet limits.

What data-handling boundary should I consider?

wallet/payment credentials and API calls Recorded sensitive-access context: wallet/payment credentials and API calls.

What limitations and risks should I check before use?

L402 Lightning payments can incur real costs; set explicit budgets and wallet limits. Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted. Dated package download count is usage signal, not necessarily a current maintenance release. Public tracking suitability is not an installation safety audit. Upstream credential and permission scopes must be validated before runtime use.