io.github.aibtcdev/mcp-server
NPM · @AIBTC/MCP-SERVER · SCANNED SEP 21
Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, x402 payments.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 56 of 196 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 11838 tokens (~85/item across 138 items; 138 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 13 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "transfer_btc" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 138 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.aibtcdev/mcp-server server?
io.github.aibtcdev/mcp-server runs locally as an npm package, launched with npx -y @aibtc/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @aibtc/mcp-server
claude mcp add aibtcdev-mcp-server -- npx -y @aibtc/mcp-server
{
"mcpServers": {
"aibtcdev-mcp-server": {
"command": "npx",
"args": [
"-y",
"@aibtc/mcp-server"
]
}
}
} {
"servers": {
"aibtcdev-mcp-server": {
"command": "npx",
"args": [
"-y",
"@aibtc/mcp-server"
]
}
}
} codex mcp add aibtcdev-mcp-server -- npx -y @aibtc/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aibtcdev-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@aibtc/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add aibtcdev-mcp-server --command npx --arg -y --arg @aibtc/mcp-server
mcp_servers:
aibtcdev-mcp-server:
command: "npx"
args: ["-y", "@aibtc/mcp-server"] {
"McpServers": {
"aibtcdev-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@aibtc/mcp-server"
]
}
}
} assistant mcp add aibtcdev-mcp-server -t stdio -c npx -a -y @aibtc/mcp-server
{
"mcpServers": {
"aibtcdev-mcp-server": {
"command": "npx",
"args": [
"-y",
"@aibtc/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/@aibtc/mcp-server@1.17.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 196 packages
| Packages resolved | 196 |
|---|---|
| Stale | 54 |
| No linked repository | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
inscribe ~176
Create a Bitcoin inscription - STEP 1: Broadcast commit transaction. This tool broadcasts the commit tx and returns immediately. It does NOT wait for confirmation. After the commit confirms (typically 10-60 min), use `inscribe_reveal` with the same contentType and contentBase64 to complete the inscription. Returns: commitTxid, revealAddress, revealAmount, and feeRate (save these for inscribe_reveal)
| Name | Type | Req | Description |
|---|---|---|---|
| contentBase64 | string | yes | Content as base64-encoded string |
| contentType | string | yes | MIME type (e.g., 'text/plain', 'image/png', 'text/html') |
| feeRate | – | – | Fee rate: 'fast' (~10 min), 'medium' (~30 min), 'slow' (~1 hr), or number in sat/vB (default: medium) |
No output schema declared.
No examples provided.
inscribe_reveal ~157
Complete a Bitcoin inscription - STEP 2: Broadcast reveal transaction. Call this AFTER the commit transaction from `inscribe` has confirmed. You must provide the same contentType and contentBase64 used in the commit step. Returns: inscriptionId ({revealTxid}i0) on success
| Name | Type | Req | Description |
|---|---|---|---|
| commitTxid | string | yes | Transaction ID of the confirmed commit transaction |
| contentBase64 | string | yes | Content as base64-encoded string (must match the commit step) |
| contentType | string | yes | MIME type (must match the commit step) |
| feeRate | – | – | Fee rate for reveal tx (default: medium) |
| revealAmount | number | yes | Amount in the commit output (from inscribe response) |
No output schema declared.
No examples provided.
list_user_domains ~38
List all BNS domains owned by an address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Stacks address to check. Uses configured wallet if not provided. |
No output schema declared.
No examples provided.
list_user_tokens ~37
List all fungible tokens owned by an address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Wallet address to check. Uses configured wallet if not provided. |
No output schema declared.
No examples provided.
list_x402_endpoints ~196
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, storage, utilities, agent registry
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (use without value to see available categories) |
| search | string | – | Search endpoints by keyword (searches path, description, category) |
| showFreeOnly | boolean | – | Only show free endpoints (no payment required) |
| showPaidOnly | boolean | – | Only show paid endpoints (require x402 payment) |
| source | string | – | Filter by API source |
No output schema declared.
No examples provided.
lookup_bns_name ~46
Resolve a .btc domain name to its Stacks address.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | BNS name to lookup (e.g., 'alice.btc' or 'alice') |
No output schema declared.
No examples provided.
openrouter_integration_guide ~113
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 implementation.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Target environment for the integration |
| feature | string | – | Specific AI feature to implement |
No output schema declared.
No examples provided.
openrouter_models ~55
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
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by model category |
No output schema declared.
No examples provided.
pillar_add_admin ~64
Add a backup admin address to your Pillar smart wallet for recovery purposes. The admin can help recover funds if you lose access to your passkey.
| Name | Type | Req | Description |
|---|---|---|---|
| adminAddress | string | – | Stacks address (SP...) to add as backup admin (can be set in UI) |
No output schema declared.
No examples provided.
pillar_auto_compound ~76
Configure auto-compound for your Pillar wallet. When enabled, a keeper will automatically boost your position when sBTC accumulates in your wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| minSbtc | number | – | Minimum sBTC to keep in wallet (in sats) |
| trigger | number | – | Amount above minimum that triggers auto-compound (in sats) |
No output schema declared.
No examples provided.
pillar_boost ~126
Create or increase a leveraged sBTC position (up to 1.5x). Opens the Pillar website where you can set the amount and confirm the boost. Your sBTC is supplied to Zest, borrowed against, and re-supplied for amplified exposure. Amounts over 100,000 sats automatically enter DCA mode — split into daily 100k-sat chunks (max 700k sats per schedule). The first chunk executes immediately, the rest follow daily.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Amount in satoshis to boost (optional, shown as suggestion) |
No output schema declared.
No examples provided.
pillar_connect ~46
Connect to your Pillar smart wallet. Opens the Pillar website - if you're logged in, it will automatically connect and return your wallet address. Use this first before other Pillar actions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_create_wallet ~90
Create a new Pillar smart wallet. Opens the Pillar website to complete registration. You'll need to enter your email to receive updates. If the user doesn't have a referral link, tell them they can DM @pillar_btc on X (https://x.com/pillar_btc) to request one before signing up.
| Name | Type | Req | Description |
|---|---|---|---|
| referral | string | – | Referral wallet address (optional, defaults to MCP referral) |
No output schema declared.
No examples provided.
pillar_dca_invite ~59
Invite a DCA partner by email or wallet address. DCA partners hold each other accountable — both must boost each week to keep the streak alive.
| Name | Type | Req | Description |
|---|---|---|---|
| partner | string | yes | Partner's email address or Stacks wallet address (SP...) |
No output schema declared.
No examples provided.
pillar_dca_leaderboard ~35
View the DCA streak leaderboard. Shows top partnerships by streak length, and highlights your entry if you have one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_dca_partners ~40
View your DCA partners and weekly status. Shows active partnerships with streak, PnL, and weekly status badges, plus any pending invites.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_dca_status ~44
Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress (completed, pending, failed) and next execution time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_direct_add_admin ~71
Add a backup admin address to your Pillar smart wallet for recovery purposes. Agent-signed, no browser needed. The admin can help recover funds if you lose access to your passkey. Backend sponsors gas.
| Name | Type | Req | Description |
|---|---|---|---|
| newAdmin | string | yes | Stacks address (SP...) to add as backup admin |
No output schema declared.
No examples provided.
pillar_direct_auto_compound ~101
Configure auto-compound for your Pillar wallet. When enabled, a keeper automatically boosts when sBTC accumulates above the trigger. Agent-signed, no browser needed. Backend sponsors gas.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | Enable or disable auto-compound |
| minSbtc | number | yes | Minimum sBTC to keep in wallet (in sats) |
| trigger | number | yes | sBTC amount above minimum that triggers auto-compound (in sats) |
No output schema declared.
No examples provided.
pillar_direct_boost ~127
Create or increase a leveraged sBTC position (up to 1.5x) on your Pillar smart wallet. Agent-signed, no browser needed. Your sBTC is supplied to Zest, borrowed against, and re-supplied for amplified exposure. Backend sponsors gas.
| Name | Type | Req | Description |
|---|---|---|---|
| aeUsdcToBorrow | number | yes | aeUSDC amount to borrow (6 decimals) |
| minSbtcFromSwap | number | yes | Min sBTC from swap in sats (slippage protection) |
| sbtcAmount | number | yes | sBTC amount in sats to supply as collateral |
No output schema declared.
No examples provided.
pillar_direct_create_wallet ~140
Create a new Pillar smart wallet for agent direct operations. This is a bundled operation: generates a signing keypair, unlocks it, and deploys a new smart wallet with the pubkey registered. Backend deploys the contract and calls onboard() in background. After ~20-30 seconds the wallet is ready for pillar_direct_* operations.
| Name | Type | Req | Description |
|---|---|---|---|
| referredBy | string | – | Contract address of the referring wallet. Defaults to the Pillar team wallet if not provided. |
| walletName | string | yes | Wallet name (3-20 chars, lowercase letters, numbers, hyphens). The contract will be deployed as {walletName}-wallet. |
No output schema declared.
No examples provided.
pillar_direct_dca_invite ~60
Invite a DCA partner by email or wallet address. DCA partners hold each other accountable — both must boost each week to keep the streak alive.
| Name | Type | Req | Description |
|---|---|---|---|
| partner | string | yes | Partner's email address or Stacks wallet address (SP...) |
No output schema declared.
No examples provided.
pillar_direct_dca_leaderboard ~36
View the DCA streak leaderboard. Shows top partnerships by streak length, and highlights your entry if you have one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_direct_dca_partners ~41
View your DCA partners and weekly status. Shows active partnerships with streak, PnL, and weekly status badges, plus any pending invites.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_direct_dca_status ~45
Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress (completed, pending, failed) and next execution time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_direct_position ~41
View your Pillar smart wallet balances (STX, sBTC, aeUSDC) and Zest position. No signing needed — reads on-chain data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_direct_quote ~66
Get a boost quote showing projected leverage, LTV, and swap details. No signing needed. Use this to determine aeUsdcToBorrow and minSbtcFromSwap before calling pillar_direct_boost.
| Name | Type | Req | Description |
|---|---|---|---|
| sbtcAmount | number | yes | sBTC amount in sats to boost |
No output schema declared.
No examples provided.
pillar_direct_send ~114
Send sBTC from your Pillar smart wallet to a recipient. Agent-signed, no browser needed. Supports BNS names, wallet names, or Stacks addresses. Backend sponsors gas.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in satoshis |
| recipientType | string | – | Type of recipient: 'bns' (default), 'wallet', or 'address' |
| to | string | yes | Recipient: BNS name (muneeb.btc), Pillar wallet name, or Stacks address (SP...) |
No output schema declared.
No examples provided.
pillar_direct_supply ~58
Supply sBTC from your Pillar smart wallet to Zest Protocol to earn yield (0x leverage). Agent-signed, no browser needed. Backend sponsors gas.
| Name | Type | Req | Description |
|---|---|---|---|
| sbtcAmount | number | yes | sBTC amount in sats to supply |
No output schema declared.
No examples provided.
pillar_direct_unwind ~119
Close or reduce your leveraged sBTC position. Agent-signed, no browser needed. Swaps sBTC to aeUSDC to repay debt, then withdraws remaining sBTC collateral. Backend sponsors gas.
| Name | Type | Req | Description |
|---|---|---|---|
| minAeUsdcFromSwap | number | yes | Min aeUSDC from swap (slippage protection, 6 decimals) |
| sbtcToSwap | number | yes | sBTC to swap to aeUSDC for repayment (in sats) |
| sbtcToWithdraw | number | yes | sBTC to withdraw after repayment (in sats) |
No output schema declared.
No examples provided.
pillar_direct_withdraw_collateral ~54
Withdraw sBTC collateral from Zest on the Pillar smart wallet. Agent-signed, no browser needed. Backend sponsors gas.
| Name | Type | Req | Description |
|---|---|---|---|
| sbtcAmount | number | yes | sBTC amount in sats to withdraw |
No output schema declared.
No examples provided.
pillar_disconnect ~19
Disconnect from Pillar. Clears locally stored wallet address.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_fund ~153
Fund your Pillar smart wallet. Supports multiple methods: - 'exchange': Deposit BTC from an exchange (Coinbase, Binance, etc.) - generates a deposit address - 'btc': Deposit BTC from your Leather/Xverse wallet - auto-converts to sBTC - 'sbtc': Deposit sBTC directly from your Leather/Xverse wallet Opens the frontend with the appropriate deposit flow.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Amount in satoshis to deposit (optional, can be set in UI) |
| method | string | yes | Funding method: 'exchange' (deposit from Coinbase/Binance), 'btc' (from Leather/Xverse BTC), 'sbtc' (from Leather/Xverse sBTC) |
No output schema declared.
No examples provided.
pillar_invite ~30
Get your Pillar referral link to invite friends. Share this link and earn rewards when friends sign up.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_key_generate ~126
Generate a new secp256k1 signing keypair for Pillar smart wallet direct operations. Returns the compressed public key (33 bytes hex). After generation, propose this pubkey on your smart wallet contract (admin must do this).
| Name | Type | Req | Description |
|---|---|---|---|
| smartWallet | string | – | Smart wallet contract ID this key is for (e.g. SPV9K21TBFAK4KNRJXF5DFP8N7W46G4V9RCJDC22.my-wallet). Use 'pending' if creating a new wallet — pillar_direct_create_wallet will update it automatically. |
No output schema declared.
No examples provided.
pillar_key_info ~28
Show signing key info: pubkey, smart wallet, lock status, and all stored keys.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_key_lock ~20
Lock the signing key, clearing sensitive data from memory.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_key_unlock ~60
Unlock a signing key for Pillar direct operations. Uses auto-derived password. Usually not needed — tools auto-unlock on first use.
| Name | Type | Req | Description |
|---|---|---|---|
| keyId | string | – | The signing key ID to unlock. If omitted, unlocks the first stored key. |
No output schema declared.
No examples provided.
pillar_position ~45
View your Pillar wallet balance and Zest position. Opens the Position modal in the browser AND returns the data (sBTC balance, collateral, borrowed, LTV, liquidation price).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_send ~161
Send sBTC from your Pillar smart wallet. Requires being connected first (use pillar_connect). Opens the frontend for signing, then waits for confirmation. Supports three recipient types: 'bns' for BNS names (muneeb.btc), 'wallet' for Pillar wallet names (iphone), 'address' for Stacks addresses (SP...).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in satoshis |
| recipientType | string | – | Type of recipient: 'bns' (default), 'wallet' for Pillar smart wallets, or 'address' for raw Stacks addresses |
| to | string | yes | Recipient: BNS name (muneeb.btc), Pillar wallet name (iphone), or Stacks address (SP...) |
No output schema declared.
No examples provided.
pillar_status ~21
Check if you're connected to Pillar and get your wallet address.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pillar_supply ~59
Supply sBTC from your Pillar smart wallet to Zest Protocol to earn yield. Your sBTC will be deposited as collateral and earn interest.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Amount in satoshis to supply (optional, can be set in UI) |
No output schema declared.
No examples provided.
pillar_unwind ~58
Close or reduce your leveraged sBTC position. Opens a modal to repay borrowed sBTC and withdraw collateral back to your wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| percentage | number | – | Percentage of position to unwind (1-100, optional, can be set in UI) |
No output schema declared.
No examples provided.
preorder_bns_name ~134
Preorder a BNS domain name. This is step 1 of a 2-step registration process. After preorder is confirmed (~10 minutes), call register_bns_name with the same salt. IMPORTANT: Save the returned salt - you'll need it for the register step! Auto-detects contract version: V2 for .btc names, V1 for other namespaces.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | BNS name to preorder (e.g., 'myname' or 'myname.btc') |
| salt | string | – | Optional salt for the preorder hash. If not provided, a random salt will be generated. |
No output schema declared.
No examples provided.
register_bns_name ~121
Register a BNS domain name after preorder is confirmed. This is step 2 of a 2-step process. You MUST use the same salt from the preorder step. Only call this after the preorder transaction has been confirmed on-chain (~10 minutes). Auto-detects contract version: V2 for .btc names, V1 for other namespaces.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | BNS name to register (must match the preordered name) |
| salt | string | yes | The hex salt used in the preorder step (REQUIRED - must match exactly) |
No output schema declared.
No examples provided.
register_identity ~113
Register a new agent identity on-chain using ERC-8004 identity registry. Returns a transaction ID. Check the transaction result to get the assigned agent ID. Requires an unlocked wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| fee | string | – | Fee preset ("low", "medium", "high") or micro-STX amount. Optional. |
| metadata | array | – | Array of metadata key-value pairs. Values must be hex-encoded buffers. Optional. |
| uri | string | – | URI pointing to agent metadata (IPFS, HTTP, etc.). Optional. |
No output schema declared.
No examples provided.
request_validation ~136
Request third-party validation for an agent using ERC-8004 validation registry. The validator will be notified and can respond with a 0-100 score. Requires an unlocked wallet and must be called by agent owner or approved operator.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | integer | yes | Agent ID to request validation for |
| fee | string | – | Fee preset ("low", "medium", "high") or micro-STX amount. Optional. |
| requestHash | string | yes | Unique request hash as hex string (32 bytes) |
| requestUri | string | yes | URI with validation request details |
| validator | string | yes | Stacks address of the validator |
No output schema declared.
No examples provided.
reverse_bns_lookup ~40
Get the BNS domain names owned by an address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Stacks address to lookup. Uses configured wallet if not provided. |
No output schema declared.
No examples provided.
sbtc_deposit ~268
Deposit BTC to receive sBTC on Stacks L2. This builds, signs, and broadcasts a Bitcoin transaction to the sBTC deposit address. After confirmation, sBTC tokens are minted to your Stacks address. The transaction uses your wallet's Taproot address for the reclaim path. If the deposit fails, you can reclaim your BTC after the lock time expires. By default, only uses cardinal UTXOs (safe to spend - no inscriptions). Set includeOrdinals=true to allow spending ordinal UTXOs (advanced users only).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | Amount to deposit in satoshis (1 BTC = 100,000,000 satoshis) |
| feeRate | – | – | Fee rate: 'fast' (~10 min), 'medium' (~30 min), 'slow' (~1 hr), or number in sat/vB |
| includeOrdinals | boolean | – | Include ordinal UTXOs (contains inscriptions). Default: false (cardinal only). WARNING: Setting this to true may destroy valuable inscriptions! |
| maxSignerFee | integer | – | Max fee the sBTC system can charge in satoshis (default: 80000 sats) |
| reclaimLockTime | integer | – | Block height when reclaim becomes available if deposit fails (default: 950 blocks) |
No output schema declared.
No examples provided.
sbtc_deposit_status ~56
Check the status of an sBTC deposit transaction from Emily API.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | Bitcoin transaction ID of the deposit |
| vout | integer | – | Output index of the deposit (default: 0) |
No output schema declared.
No examples provided.
What is the io.github.aibtcdev/mcp-server server?
io.github.aibtcdev/mcp-server is listed in the public MCP registry as io.github.aibtcdev/mcp-server. Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, x402 payments. This page covers its npm package (@aibtc/mcp-server).
Is the io.github.aibtcdev/mcp-server server safe to use?
io.github.aibtcdev/mcp-server scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.aibtcdev/mcp-server server expose?
io.github.aibtcdev/mcp-server exposes 138 tools: get_btc_balance, get_btc_fees, get_btc_utxos, transfer_btc, get_cardinal_utxos, and 133 more. Their descriptions and schemas cost roughly 11,838 tokens of context every time the server is loaded.
Is the io.github.aibtcdev/mcp-server server still maintained?
io.github.aibtcdev/mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.aibtcdev/mcp-server server under?
io.github.aibtcdev/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.