blackpool
Related Servers
Alternatives to blackpool
- AlicenseAqualityDmaintenanceEnables AI agents to send and receive private Zcash payments with shielded transactions, balance checks, and encrypted memos.5MIT

@coinbase/payments-mcpofficial
AlicenseNot gradedqualityDmaintenanceCombines wallets, onramps, and payments via x402 to enable AI agents to autonomously discover and pay for services without API keys or complex setup.48 npm58Apache 2.0
Related Servers
- AlicenseAqualityCmaintenanceZcash MCP server for AI agents. 12 tools for shielded operations, memo decoding, ZAP1 attestation. Works with Claude, ChatGPT, OpenClaw.2088 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that lets any AI agent operate a wallet directly on-chain: create wallets, send, swap, bridge, and deploy contracts across EVM and Bitcoin networks.1MIT
- AlicenseAqualityBmaintenancePayment infrastructure MCP server enabling AI agents to make gasless USDC payments on Base and JIT single-use virtual card checkouts, with zero-trust card handling, merchant checkout hints, and signed receipts.13111 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server exposing 10 curated tools for AI agents, providing crypto trading signals, on-chain analysis, and web utilities via pay-per-call x402 endpoints on the Base network.MIT
- AlicenseNot gradedqualityBmaintenanceNon-custodial BVCC Agent Wallet MCP server: let an AI agent check balances, send native/ERC-20, approve, and swap on Uniswap v3/v4 across Ethereum, BNB Chain, Arbitrum and Base, within on-chain enforced limits.601 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients and AI agents to privately swap and send assets on Robinhood Chain, with quotes, swap creation, deposit payment from an optional local wallet, status checks, handoff links, wallet balances, and rewards.MIT
TDQS
Scored across 9 tools
Most tools map to clearly distinct actions (deposit vs send vs swap vs recover), but blackpool_bridge (initiate a cross-chain transfer) and blackpool_bridges (list existing bridges) differ only by a plural 's', which is an easy misselection trap. blackpool_assets and blackpool_bridges are also both read-only metadata/list tools that could be confused at a glance. The descriptions do disambiguate once read, which keeps this above a 2.
All nine tools share the same blackpool_ prefix and a flat lowercase style with no camelCase or multi-word mixing, so the surface looks uniform. However, the naming is noun-based for some tools (address, balance, assets, bridges) and verb-based for others (send, deposit, swap, recover), and the singular/plural bridge pair is not a predictable pattern.
Nine tools is well within the sweet spot and each one covers a distinct facet of a private wallet: identity, balances, shield, send, swap, bridge (create/list/assets), and recovery. Nothing appears redundant or padded, and nothing essential is obviously missing from the count.
The lifecycle is largely covered: funding address, shielded balance reads, deposit in, private send out, swap, cross-chain bridge with status listing and destination metadata, plus a recovery sweep for stuck funds. The main gap is an explicit unshield/withdraw-to-public operation and any transaction history beyond bridge records, though send-to-self could work around the former.