MCP.Market

Aibtcdev MCP server

by aibtcdev·io.github.aibtcdev/mcp-server·v1.17.0·10 stars

Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, x402 payments.

A94/100grade A
What users say
No reviews yet
Be the first
Safety scan
A94/100

full report

Adoption
Growing

10 stars790 downloads/wk

Reviews

Write one

Nobody has reviewed Aibtcdev yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Aibtcdev tools (100, 17 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • alex_get_pool_info

    Get liquidity pool information from ALEX DEX. Returns reserve balances and pool details for a token pair. Note: ALEX DEX is only available on mainnet.

  • alex_get_swap_quote

    Get a swap quote from ALEX DEX. Returns the expected output amount for swapping tokenX to tokenY. Use full contract IDs for tokens (e.g., 'SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-wstx-v2'). Note: ALEX DEX is only available on mainnet.

  • alex_list_pools

    List all available trading pools on ALEX DEX. Discovers all token pairs that can be swapped directly. Returns pool ID, token pair, and factor (fee tier) for each pool. Use this to find which tokens can be swapped before calling alex_swap. Note: ALEX DEX is only available on mainnet.

  • alex_swapwrite action

    Execute a token swap on ALEX DEX. Swaps tokenX for tokenY using the ALEX AMM. Use full contract IDs for tokens. Note: ALEX DEX is only available on mainnet.

  • bitflow_cancel_orderwrite action

    Cancel a Bitflow Keeper order. Cancels a pending order before execution. Requires BITFLOW_KEEPER_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • bitflow_create_orderwrite action

    Create an automated swap order via Bitflow Keeper. Creates a pending order that will be executed by the Keeper service. Requires BITFLOW_KEEPER_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • bitflow_get_keeper_contract

    Get or create a Bitflow Keeper contract for automated swaps. Keeper contracts enable scheduled/automated token swaps. Requires BITFLOW_KEEPER_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • bitflow_get_keeper_user

    Get Bitflow Keeper user info and orders. Retrieves user's keeper contracts and order history. Requires BITFLOW_KEEPER_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • bitflow_get_orderwrite action

    Get details of a Bitflow Keeper order. Retrieves the status and details of a specific order. Requires BITFLOW_KEEPER_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • bitflow_get_quote

    Get a swap quote from Bitflow DEX. Returns the expected output amount and route for swapping tokens. Requires BITFLOW_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • bitflow_get_routes

    Get all possible swap routes between two tokens on Bitflow. Returns all available routes for swapping from tokenX to tokenY. Useful for understanding routing options. Requires BITFLOW_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • bitflow_get_swap_targets

    Get possible swap target tokens for a given input token on Bitflow. Returns all tokens that can be received when swapping from the specified token. Requires BITFLOW_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • bitflow_get_ticker

    Get market ticker data from Bitflow DEX. Returns price, volume, and liquidity data for all trading pairs. This endpoint does NOT require an API key. Note: Bitflow is only available on mainnet.

  • bitflow_get_tokens

    Get all available tokens for swapping on Bitflow. Returns the list of tokens that can be swapped on Bitflow DEX. Requires BITFLOW_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • bitflow_swapwrite action

    Execute a token swap on Bitflow DEX. Swaps tokenX for tokenY using Bitflow's aggregated liquidity. Requires BITFLOW_API_KEY environment variable. Note: Bitflow is only available on mainnet.

  • call_contract

    Call a function on a Stacks smart contract. Signs and broadcasts the transaction. For typed arguments, use objects like {type: 'uint', value: 100} or {type: 'principal', value: 'SP...'}

  • call_read_only_function

    Call a read-only function on a smart contract (no signing required).

  • check_bns_availability

    Check if a BNS domain name is available for registration.

  • deploy_contractwrite action

    Deploy a Clarity smart contract to the Stacks blockchain.

  • estimate_inscription_fee

    Calculate the total cost (in satoshis) for creating an inscription.

  • execute_x402_endpointwrite action

    Execute an x402 API endpoint. Payment is handled automatically. Supported sources: - x402.biwas.xyz (default): Use path like "/api/pools/trending" - stx402.com: Use apiUrl="https://stx402.com" with path like "/api/ai/dad-joke" Use list_x402_endpoints to discover available endpoints.

  • get_account_info

    Get detailed account information including nonce and balance.

  • get_bns_info

    Get detailed information about a BNS domain name.

  • get_bns_price

    Get the registration price for a BNS domain name.

  • get_btc_balance

    Get the BTC balance for a Bitcoin address.

  • get_btc_fees

    Get current Bitcoin fee estimates for different confirmation targets.

  • get_btc_utxos

    List all UTXOs (Unspent Transaction Outputs) for a Bitcoin address.

  • get_cardinal_utxos

    Get cardinal UTXOs (safe to spend - no inscriptions).

  • get_collection_info

    Get information about an NFT collection.

  • get_identity

    Get agent identity information from ERC-8004 identity registry.

  • get_inscription

    Get inscription content from a Bitcoin reveal transaction.

  • get_inscriptions_by_address

    Get all inscriptions owned by a Bitcoin address.

  • get_nft_history

    Get the transfer history of NFTs in a collection.

  • get_nft_holdings

    List all NFTs owned by an address.

  • get_nft_metadata

    Get metadata for a specific NFT (SIP-016).

  • get_nft_owner

    Get the current owner of a specific NFT.

  • get_ordinal_utxos

    Get ordinal UTXOs (contain inscriptions - do not spend).

  • get_reputation

    Get aggregated reputation summary for an agent from ERC-8004 reputation registry.

  • get_stx_fees

    Get current STX fee estimates for different priority levels.

  • get_taproot_address

    Get the wallet's Taproot (P2TR) address for receiving inscriptions.

  • get_transaction_status

    Check the status of a Stacks transaction by its txid.

  • get_validation_status

    Get the status of a validation request using ERC-8004 validation registry.

  • get_validation_summary

    Get validation summary for an agent using ERC-8004 validation registry.

  • give_feedbackwrite action

    Submit feedback for an agent using ERC-8004 reputation registry.

  • inscribewrite action

    Create a Bitcoin inscription - STEP 1: Broadcast commit transaction.

  • inscribe_reveal

    Complete a Bitcoin inscription - STEP 2: Broadcast reveal transaction.

  • list_user_domains

    List all BNS domains owned by an address.

  • list_x402_endpoints

    List known x402 API endpoints from x402.biwas.xyz and stx402.com. The agent can: 1. Execute x402 endpoints from these sources (paid API calls with automatic payment handling) 2. Execute direct Stacks transactions (transfer STX, call contracts, deploy contracts) Sources: - x402.biwas.xyz: DeFi analytics, market data, wallet analysis, Zest/ALEX protocols - stx402.com: AI services, cryptography, stor

  • lookup_bns_name

    Resolve a .btc domain name to its Stacks address.

  • openrouter_integration_guide

    Get OpenRouter integration examples and code patterns for implementing AI features. Use this tool when you need to add AI capabilities to any project. Returns: - Code examples for different environments (Node.js, Cloudflare Workers, browser) - API patterns and best practices - Model recommendations - Error handling patterns This is a reference tool - use the returned code as a template for impleme

  • openrouter_models

    Get list of popular OpenRouter models with capabilities and context lengths. Use this to choose the right model for your use case. For latest pricing, check openrouter.ai/models

  • pillar_add_admin

    Add a backup admin address to your Pillar smart wallet for recovery purposes.

  • pillar_auto_compound

    Configure auto-compound for your Pillar wallet.

  • pillar_boostwrite action

    Create or increase a leveraged sBTC position (up to 1.5x).

  • pillar_connect

    Connect to your Pillar smart wallet. Opens the Pillar website - if you're logged in,

  • pillar_create_walletwrite action

    Create a new Pillar smart wallet. Opens the Pillar website to complete registration.

  • pillar_dca_invite

    Invite a DCA partner by email or wallet address.

  • pillar_dca_leaderboard

    View the DCA streak leaderboard. Shows top partnerships by streak length, and highlights your entry if you have one.

  • pillar_dca_partners

    View your DCA partners and weekly status.

  • pillar_dca_status

    Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress

  • pillar_direct_add_admin

    Add a backup admin address to your Pillar smart wallet for recovery purposes.

  • pillar_direct_auto_compound

    Configure auto-compound for your Pillar wallet.

  • pillar_direct_boostwrite action

    Create or increase a leveraged sBTC position (up to 1.5x) on your Pillar smart wallet.

  • pillar_direct_create_walletwrite action

    Create a new Pillar smart wallet for agent direct operations.

  • pillar_direct_dca_invite

    Invite a DCA partner by email or wallet address.

  • pillar_direct_dca_leaderboard

    View the DCA streak leaderboard. Shows top partnerships by streak length, and highlights your entry if you have one.

  • pillar_direct_dca_partners

    View your DCA partners and weekly status.

  • pillar_direct_dca_status

    Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress

  • pillar_direct_position

    View your Pillar smart wallet balances (STX, sBTC, aeUSDC) and Zest position.

  • pillar_direct_quote

    Get a boost quote showing projected leverage, LTV, and swap details.

  • pillar_direct_sendwrite action

    Send sBTC from your Pillar smart wallet to a recipient.

  • pillar_direct_supply

    Supply sBTC from your Pillar smart wallet to Zest Protocol to earn yield (0x leverage).

  • pillar_direct_unwind

    Close or reduce your leveraged sBTC position. Agent-signed, no browser needed.

  • pillar_direct_withdraw_collateral

    Withdraw sBTC collateral from Zest on the Pillar smart wallet.

  • pillar_disconnect

    Disconnect from Pillar. Clears locally stored wallet address.

  • pillar_fund

    Fund your Pillar smart wallet. Supports multiple methods:

  • pillar_invite

    Get your Pillar referral link to invite friends. Share this link and earn rewards when friends sign up.

  • pillar_key_generate

    Generate a new secp256k1 signing keypair for Pillar smart wallet direct operations.

  • pillar_key_info

    Show signing key info: pubkey, smart wallet, lock status, and all stored keys.

  • pillar_key_lock

    Lock the signing key, clearing sensitive data from memory.

  • pillar_key_unlock

    Unlock a signing key for Pillar direct operations.

  • pillar_position

    View your Pillar wallet balance and Zest position.

  • pillar_sendwrite action

    Send sBTC from your Pillar smart wallet. Requires being connected first (use pillar_connect).

  • pillar_status

    Check if you're connected to Pillar and get your wallet address.

  • pillar_supply

    Supply sBTC from your Pillar smart wallet to Zest Protocol to earn yield.

  • pillar_unwind

    Close or reduce your leveraged sBTC position.

  • preorder_bns_name

    Preorder a BNS domain name. This is step 1 of a 2-step registration process.

  • register_bns_name

    Register a BNS domain name after preorder is confirmed. This is step 2 of a 2-step process.

  • register_identity

    Register a new agent identity on-chain using ERC-8004 identity registry.

  • request_validation

    Request third-party validation for an agent using ERC-8004 validation registry.

  • reverse_bns_lookup

    Get the BNS domain names owned by an address.

  • transfer_btcwrite action

    Transfer BTC to a recipient address.

  • transfer_nftwrite action

    Transfer an NFT (SIP-009) to a recipient address.

  • zest_borrow

    Borrow assets from Zest Protocol. Borrows assets against your supplied collateral. Ensure you have sufficient collateral to maintain a healthy position. You can use the asset symbol (e.g., 'aeUSDC') or full contract ID. Note: Zest Protocol is only available on mainnet.

  • zest_claim_rewards

    Claim accumulated rewards from Zest Protocol incentives program. Currently, sBTC suppliers earn wSTX rewards. This function claims any accumulated rewards and sends them to your wallet. You can use the asset symbol (e.g., 'sBTC') or full contract ID. Note: Zest Protocol is only available on mainnet.

  • zest_get_position

    Get user's lending position on Zest Protocol. Returns supplied and borrowed amounts for a specific asset. You can use the asset symbol (e.g., 'stSTX') or full contract ID. Note: Zest Protocol is only available on mainnet.

  • zest_list_assets

    List all supported assets on Zest Protocol. Returns the list of assets that can be supplied, borrowed, or used as collateral. Each asset includes its symbol, name, and contract ID. Use this to discover available assets before supplying or borrowing. Note: Zest Protocol is only available on mainnet.

  • zest_repay

    Repay borrowed assets to Zest Protocol. Repays borrowed assets plus accrued interest. You can use the asset symbol (e.g., 'aeUSDC') or full contract ID. Note: Zest Protocol is only available on mainnet.

  • zest_supply

    Supply assets to Zest Protocol lending pool. Deposits assets to earn interest from borrowers. You can use the asset symbol (e.g., 'stSTX') or full contract ID. Note: Zest Protocol is only available on mainnet.

  • zest_withdraw

    Withdraw assets from Zest Protocol lending pool. Redeems supplied assets plus earned interest. You can use the asset symbol (e.g., 'stSTX') or full contract ID. Note: Zest Protocol is only available on mainnet.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan137 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Aibtcdev compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
94/100
higher than 96% of 48,255 servers
Tools
100
the typical server has 7
Tools that change things
17%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
10
more than 88% of 28,688 servers
Downloads a week
790
more than 93% of 12,191 servers with a package

What its tools let an agent do: 79 read · 4 create · 15 change · 2 run or deploy

Install Aibtcdev in Claude Code, Cursor or VS Code

Runs npx -y @aibtc/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-server -- npx -y @aibtc/mcp-server
Add to Cursor

What the publisher says

From the Aibtcdev repository's README, as published. We do not edit it. Read it on GitHub

@aibtc/mcp-server

Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, and x402 payments.

Features

  • Bitcoin L1 - Check balances, send BTC, manage UTXOs via mempool.space
  • Agent's Own Wallet - Agents get their own wallet to perform blockchain transactions
  • Secure Storage - Wallets encrypted with AES-256-GCM and stored locally
  • 350+ Tools - Bitcoin L1 + comprehensive Stacks L2 operations
  • sBTC Support - Native Bitcoin on Stacks operations
  • Token Operations - SIP-010 fungible token transfers and queries
  • NFT Support - SIP-009 NFT holdings, transfers, and metadata
  • DeFi Trading - ALEX DEX swaps and Zest Protocol lending/borrowing
  • Stacking/PoX-5 - Stake STX with a signer manager, extend, unstake, claim sBTC rewards
  • BNS Domains - .btc domain lookups and management (V1 + V2)
  • x402 Payments - Automatic payment handling for paid APIs

Quick Start

Claude Code (Terminal)

npx @aibtc/mcp-server@latest --install

This configures Claude Code and creates the agent's wallet: it prints the Stacks and Bitcoin addresses, a generated password and the 24-word mnemonic once. Write both down. The mnemonic is stored only encrypted (AES-256-GCM) in ~/.aibtc/ on this machine, and the password is not saved anywhere; the agent asks for it to unlock, and you can change it with walletrotatepassword. If a wallet for the network already exists it is kept. The wallet is only created when the install runs in an interactive terminal (never into a pipe or CI log). Pass --no-wallet to skip it and create or import one from the agent instead.

Restart your terminal, send a little STX to the printed address, and ask the agent to unlock the wallet and make a paid inference call.

Claude Desktop (App)

npx @aibtc/mcp-server@latest --install --desktop

This detects your OS and writes to the correct Claude Desktop config file:

Restart Claude Desktop after installing.

Other MCP Clients

This is a standard stdio MCP server, so it works with any MCP-compatible client. Claude Code is the default --install target; select another client with a flag:

npx @aibtc/mcp-server@latest --install --cursor     # Cursor
npx @aibtc/mcp-server@latest --install --windsurf   # Windsurf
npx @aibtc/mcp-server@latest --install --gemini     # Gemini CLI
npx @aibtc/mcp-server@latest --install --codex      # OpenAI Codex CLI
npx @aibtc/mcp-server@latest --install --vscode     # VS Code (writes ./.vscode/mcp.json)

Each installer merges into the existing config — it won't clobber other servers or settings. Restart the client afterward.

OpenRouter (any model)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Aibtcdev: common questions

Is Aibtcdev MCP server safe?
Yes, by our scan: it is graded A (94/100). Read the Aibtcdev safety report
How do I install Aibtcdev?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Aibtcdev need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Aibtcdev maintained?
The last commit was 37 days ago (2026-09-28). The latest release is v1.17.0.
How does Aibtcdev compare with other MCP servers?
safety score 94/100 (higher than 96% of 48,255 servers); tools 100 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.