bolthub
OfficialRelated Servers
Alternatives to bolthub
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceL402 + x402 client MCP. AI agents discover, pay for, and consume any payment-gated API autonomously. Supports Lightning (NWC), Cashu ecash, stablecoins, and human-in-the-loop payments.11340 npmMIT
- AlicenseAqualityAmaintenanceAgent-to-agent commerce over Bitcoin Lightning: buy, sell, list, and discover files, data, APIs, and compute on a public marketplace (or privately by offer id). Non-custodial, buyers pay sellers wallet-to-wallet and a verified payment preimage unlocks the result.627118 npmMIT No Attribution

gatefareio/mcp-serverofficial
AlicenseNot gradedqualityCmaintenanceMarketplace MCP for paid HTTP APIs. Pay per call in USDC on Base via the open x402 standard — non-custodial. 13 tools for discovery, buying, and publishing APIs.36 npm2MIT- FlicenseNot gradedqualityBmaintenanceAI Agent Hub is a pay-per-call API platform for AI agents Every call is billed automatically in USDC using the x402 protocol - there is no API key, no account, and no signup. Agents get instant access to data queries, file storage, and ad impressions, paying only for what they actually use. The same tools are also exposed natively over MCP, so any MCP-capable agent can discover and call them-
- AlicenseAqualityBmaintenanceMCP server that enables AI agents to make autonomous Bitcoin Lightning Network payments using the L402 protocol. Agents can pay for API access, purchase resources, and complete transactions without human intervention — invoice comes in, sats go out, done.179MIT

btcmatic-mcp-serverofficial
AlicenseAqualityCmaintenanceMCP server that gives autonomous agents pay-per-call Bitcoin context (self-custody radar, fee percentiles, price change windows, condition frequencies) paid in sats over Lightning via L402 invoices, with no account or API key required.7MIT
TDQS
Scored across 19 tools
The tools map to clear buyer/seller workflows and mostly do not overlap. The one potential trap is list_api sounding like a directory-listing operation alongside search_apis, but its description makes the draft-listing intent clear.
Most tools follow a verb_noun pattern such as search_apis, call_api, create_workspace, and publish_listing. Deviations like node_status and usage_summary omit a verb, and list_api uses singular where search_apis uses plural, but the overall style remains readable and predictable.
At 19 tools, the set sits in the heavy range and adds selection overhead for agents, though the buyer/seller split keeps tools purposeful. It is above the ideal well-scoped size but not bloated enough to be a major problem.
Core buyer and seller journeys are covered: discovery, pricing, calling, prepayment, delegation, onboarding, publishing, analysis, and reporting. However, there is no unpublish/delete for listings, no way to remove a workspace, and no explicit buyer balance query, leaving lifecycle dead ends.