Blink MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLINK_API_KEY | Yes | Your Blink API key | |
| BLINK_NETWORK | No | Network to use (mainnet or staging) | mainnet |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_infoA | Get the current user account information including wallets, balances, and settings |
| get_walletsA | Get all wallets (BTC and USD) with their current balances. Balance is in satoshis for BTC wallet and cents for USD wallet. |
| get_wallet_balanceA | Get the balance of a specific wallet by ID. Returns balance in satoshis (BTC) or cents (USD). |
| get_transactionsB | Get transaction history for one or more wallets. Supports pagination. |
| get_transaction_by_idB | Get details of a specific transaction by ID |
| get_account_limitsA | Get the current account limits for withdrawals, internal sends, and currency conversion |
| set_default_walletA | Set the default wallet for the account (BTC or USD wallet) |
| set_display_currencyB | Set the display currency for the account (e.g., USD, EUR, BTC) |
| get_realtime_priceA | Get the current real-time Bitcoin price in a specified currency |
| get_price_historyA | Get Bitcoin price history for a specified time range |
| convert_currencyC | Get currency conversion estimation between fiat and Bitcoin |
| get_supported_currenciesB | Get list of all supported display currencies |
| lookup_user_walletB | Look up a user's default wallet by their Blink username |
| check_username_availableA | Check if a Blink username is available |
| set_usernameA | Set or update the username for the current user |
| get_authorization_scopesA | Get the permission scopes available for the current API key |
| get_network_infoA | Get global network information including Lightning node details and fee information |
| create_invoiceB | Create a Lightning invoice to receive a specific amount of Bitcoin. Amount is in satoshis for BTC wallet. |
| create_invoice_usdA | Create a Lightning invoice to receive a specific amount in USD cents (Stablesats). The invoice will be denominated in satoshis but credited as USD. |
| create_invoice_no_amountA | Create a Lightning invoice without a specified amount (open invoice). The payer can choose how much to send. |
| cancel_invoiceA | Cancel an unpaid Lightning invoice |
| get_invoice_statusA | Check the payment status of a Lightning invoice by payment hash |
| get_invoice_status_by_requestA | Check the payment status of a Lightning invoice by payment request (bolt11) |
| pay_invoiceB | Pay a Lightning invoice. The invoice amount must be specified in the invoice. |
| pay_invoice_with_amountB | Pay a Lightning invoice that has no amount specified (open invoice). You specify the amount to send. |
| pay_lightning_addressC | Send Bitcoin to a Lightning Address (e.g., user@blink.sv) |
| pay_lnurlC | Pay using an LNURL (Lightning URL) |
| estimate_lightning_feeA | Estimate the Lightning network fee for paying an invoice |
| estimate_lightning_fee_no_amountB | Estimate the Lightning network fee for paying an open (no-amount) invoice |
| create_onchain_addressA | Generate a new on-chain Bitcoin address to receive funds |
| get_current_onchain_addressA | Get the current (most recent) on-chain Bitcoin address for a wallet |
| send_onchainC | Send Bitcoin on-chain to a Bitcoin address. Amount is in satoshis for BTC wallet. |
| send_onchain_allB | Send the entire wallet balance on-chain to a Bitcoin address (sweep) |
| send_onchain_usdC | Send on-chain Bitcoin from a USD (Stablesats) wallet. Amount is in cents. |
| estimate_onchain_feeB | Estimate the on-chain transaction fee for sending Bitcoin (BTC wallet) |
| estimate_onchain_fee_usdA | Estimate the on-chain transaction fee for sending from USD wallet |
| send_to_walletA | Send Bitcoin directly to another Blink wallet (free, instant, intraledger transfer). Amount is in satoshis for BTC wallets. |
| send_to_wallet_usdA | Send USD (Stablesats) directly to another Blink wallet (free, instant, intraledger transfer). Amount is in cents. |
| send_to_usernameA | Send Bitcoin to a Blink user by their username. This looks up their wallet and does an intraledger transfer (free, instant). |
| list_webhooksA | List all registered webhook callback endpoints for the account |
| add_webhookB | Register a new webhook callback endpoint to receive payment notifications |
| remove_webhookB | Remove a registered webhook callback endpoint |
| subscribe_invoice_statusC | Subscribe to real-time updates for a Lightning invoice payment status. Returns a subscription ID to track or cancel. |
| subscribe_invoice_status_by_hashB | Subscribe to real-time updates for a Lightning invoice by payment hash |
| subscribe_account_updatesA | Subscribe to all real-time account updates including incoming/outgoing transactions and price updates |
| subscribe_price_updatesC | Subscribe to real-time Bitcoin price updates in a specified currency |
| list_subscriptionsA | List all active real-time subscriptions |
| cancel_subscriptionB | Cancel an active real-time subscription |
| cancel_all_subscriptionsA | Cancel all active real-time subscriptions |
| l402_discoverA | Probe a URL for L402 payment requirements without paying. Returns the invoice, price in sats, and format (lightning-labs or l402-protocol). Use this before l402_pay to check the cost of accessing a resource. |
| l402_payA | Access an L402-protected URL by automatically paying the Lightning invoice. Checks the token cache first to avoid re-paying. Returns the response data from the protected resource after successful payment. |
| l402_challenge_createA | Create an L402 payment challenge (invoice + signed macaroon) to protect a resource behind a Lightning paywall. Returns a WWW-Authenticate header that can be sent to clients with HTTP 402. |
| l402_payment_verifyA | Verify an L402 payment token submitted by a client. Checks three layers: 1) preimage proves payment (SHA-256), 2) HMAC signature proves authenticity, 3) caveats (expiry, resource) are satisfied. Returns valid: true/false. |
| l402_searchA | Search L402 service directories to find paid APIs that can be accessed with Lightning payments. Default source: l402.directory (curated, rich schema). Alternative: 402index.io (broader coverage, 50+ services). |
| l402_storeA | Manage the local L402 token cache at ~/.blink/l402-tokens.json. List cached tokens (with masked sensitive data), get a token for a domain, or clear tokens. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 55 tools
The BTC/USD tool pairs (send_onchain vs send_onchain_usd, send_to_wallet vs send_to_wallet_usd, estimate_onchain_fee vs estimate_onchain_fee_usd, create_invoice vs create_invoice_usd) and the invoice-status quartet (get_invoice_status, get_invoice_status_by_request, subscribe_invoice_status, subscribe_invoice_status_by_hash) create real selection friction. Descriptions do a decent job of explaining the differences, but an agent must read carefully to avoid picking the wrong variant. Multi-mode tools like l402_store (list/get/clear in one) add further ambiguity.
Mostly snake_case verb_noun with a coherent variant-suffix scheme (_usd, _no_amount, _by_request, _by_hash, _all), which is readable. However the l402_ family is noun-prefixed with non-verb names (l402_discover, l402_store, l402_challenge_create) and a few tools use different molds (check_username_available, lookup_user_wallet), so it's mixed rather than uniform.
55 tools is well above what a wallet API surface needs; many are near-duplicates that could be collapsed into one tool with a wallet/currency parameter (all the *_usd variants, the three create_invoice variants, the four estimate_*_fee tools). The L402 and subscription families are legitimate, but the BTC/USD duplication inflates the count significantly.
Coverage is strong: receive (invoices, on-chain addresses), send (invoice, LNURL, lightning address, intraledger, on-chain sweep), fees, webhooks, real-time subscriptions, account settings, and a full L402 client+server flow. Minor gaps exist — no explicit USD-wallet invoice payment tool (create_invoice_usd has no pay counterpart), no webhook get/update-by-id, and no contacts directory.