io.github.aibtcdev/mcp-server
NPM · @AIBTC/MCP-SERVER · SCANNED SEP 20
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 3 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 Management83
- Stability observed for 25 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.
- 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
- 10 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.
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 20 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 →
alex_get_pool_info ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenX | string | yes | First token contract ID |
| tokenY | string | yes | Second token contract ID |
No output schema declared.
No examples provided.
alex_get_swap_quote ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amountIn | string | yes | Amount of tokenX to swap (in smallest units) |
| tokenX | string | yes | Input token contract ID |
| tokenY | string | yes | Output token contract ID |
No output schema declared.
No examples provided.
alex_list_pools ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of pools to return (default 50) |
No output schema declared.
No examples provided.
alex_swap ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amountIn | string | yes | Amount of tokenX to swap (in smallest units) |
| minAmountOut | string | – | Minimum acceptable output amount (slippage protection) |
| tokenX | string | yes | Input token contract ID |
| tokenY | string | yes | Output token contract ID |
No output schema declared.
No examples provided.
broadcast_transaction ~35
Broadcast a pre-signed Stacks transaction to the network.
| Name | Type | Req | Description |
|---|---|---|---|
| signedTx | string | yes | The signed transaction as a hex string |
No output schema declared.
No examples provided.
btc_sign_message ~83
Sign a plain text message using the Bitcoin message signing format (BIP-137). Creates a 65-byte signature compatible with most Bitcoin wallets. Use cases: proving Bitcoin address ownership, authentication, off-chain verification. Requires an unlocked wallet with Bitcoin keys.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The plain text message to sign. Will be formatted with Bitcoin message prefix before signing. |
No output schema declared.
No examples provided.
btc_verify_message ~138
Verify a BIP-137 Bitcoin message signature and recover the signer's address. Takes the original message and signature (hex or base64), recovers the public key, and derives the Bitcoin address. Compatible with signatures from most Bitcoin wallets.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedSigner | string | – | Optional: expected signer Bitcoin address to verify against. If provided, returns whether the signature is valid for this address. |
| message | string | yes | The original plain text message that was signed. |
| signature | string | yes | The BIP-137 signature (65 bytes as hex or base64). Hex format: 130 characters. Base64 format: 88 characters. |
No output schema declared.
No examples provided.
call_contract ~202
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...'}
| Name | Type | Req | Description |
|---|---|---|---|
| contractAddress | string | yes | The contract deployer's address (e.g., SP2...) |
| contractName | string | yes | The contract name (e.g., 'my-token') |
| fee | string | – | Optional fee: 'low' | 'medium' | 'high' preset or micro-STX amount. If omitted, auto-estimated. |
| functionArgs | array | – | Function arguments. For explicit types: {type: 'uint'|'int'|'principal'|..., value: ...} |
| functionName | string | yes | The function to call (e.g., 'transfer') |
| postConditionMode | string | – | 'deny' (default): Blocks unexpected transfers. 'allow': Permits any transfers. |
No output schema declared.
No examples provided.
call_read_only_function ~100
Call a read-only function on a smart contract (no signing required).
| Name | Type | Req | Description |
|---|---|---|---|
| contractId | string | yes | Contract ID in format: address.contract-name |
| functionArgs | array | – | Function arguments. For explicit types: {type: 'uint'|'int'|'principal'|..., value: ...} |
| functionName | string | yes | The read-only function to call |
| senderAddress | string | – | Optional sender address for the call |
No output schema declared.
No examples provided.
check_bns_availability ~41
Check if a BNS domain name is available for registration.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | BNS name to check (e.g., 'alice') |
No output schema declared.
No examples provided.
deploy_contract ~89
Deploy a Clarity smart contract to the Stacks blockchain.
| Name | Type | Req | Description |
|---|---|---|---|
| codeBody | string | yes | The complete Clarity source code |
| contractName | string | yes | Unique name for the contract (lowercase, hyphens allowed) |
| fee | string | – | Optional fee: 'low' | 'medium' | 'high' preset or micro-STX amount. If omitted, auto-estimated. |
No output schema declared.
No examples provided.
estimate_inscription_fee ~108
Calculate the total cost (in satoshis) for creating an inscription. Returns breakdown of commit fee, reveal fee, and total cost. Content should be provided as base64-encoded string.
| Name | Type | Req | Description |
|---|---|---|---|
| contentBase64 | string | yes | Content as base64-encoded string |
| contentType | string | yes | MIME type (e.g., 'text/plain', 'image/png') |
| feeRate | number | – | Fee rate in sat/vB (optional, defaults to current medium fee) |
No output schema declared.
No examples provided.
execute_x402_endpoint ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiUrl | string | – | API base URL. Defaults to configured API_URL (x402.biwas.xyz). |
| data | object | – | Request body for POST/PUT requests |
| method | string | – | HTTP method |
| params | object | – | Query parameters for GET requests |
| path | string | yes | API endpoint path (e.g., '/api/pools/trending') |
No output schema declared.
No examples provided.
extend_stacking ~60
Extend an existing stacking lock period.
| Name | Type | Req | Description |
|---|---|---|---|
| extendCount | number | yes | Number of additional cycles to lock |
| poxAddressHashbytes | string | yes | Bitcoin address hash (hex string) |
| poxAddressVersion | number | yes | Bitcoin address version |
No output schema declared.
No examples provided.
get_account_info ~35
Get detailed account information including nonce and balance.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Stacks address. Uses configured wallet if not provided. |
No output schema declared.
No examples provided.
get_account_transactions ~54
Get transaction history for an account.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Stacks address. Uses configured wallet if not provided. |
| limit | number | – | Maximum number of results |
| offset | number | – | Offset for pagination |
No output schema declared.
No examples provided.
get_block_info ~33
Get information about a specific block.
| Name | Type | Req | Description |
|---|---|---|---|
| heightOrHash | string | yes | Block height (number) or block hash |
No output schema declared.
No examples provided.
get_bns_info ~40
Get detailed information about a BNS domain name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | BNS name to lookup (e.g., 'alice.btc') |
No output schema declared.
No examples provided.
get_bns_price ~39
Get the registration price for a BNS domain name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | BNS name to check (e.g., 'alice') |
No output schema declared.
No examples provided.
get_btc_balance ~66
Get the BTC balance for a Bitcoin address. Returns both total balance (including unconfirmed) and confirmed balance.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Bitcoin address to check (bc1... for mainnet, tb1... for testnet). Uses wallet's Bitcoin address if not provided. |
No output schema declared.
No examples provided.
get_btc_fees ~45
Get current Bitcoin fee estimates for different confirmation targets. Returns fast (~10 min), medium (~30 min), and slow (~1 hour) fee rates in sat/vB.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_btc_utxos ~77
List all UTXOs (Unspent Transaction Outputs) for a Bitcoin address. Useful for debugging, transparency, and understanding transaction inputs.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Bitcoin address to check. Uses wallet's Bitcoin address if not provided. |
| confirmedOnly | boolean | – | Only return confirmed UTXOs (default: false) |
No output schema declared.
No examples provided.
get_cardinal_utxos ~110
Get cardinal UTXOs (safe to spend - no inscriptions). Cardinal UTXOs are regular Bitcoin outputs that do not contain ordinal inscriptions. These UTXOs can be safely used for regular Bitcoin transfers and fees. Only available on mainnet (Hiro Ordinals API does not index testnet).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Bitcoin address to check. Uses wallet's Bitcoin address if not provided. |
| confirmedOnly | boolean | – | Only return confirmed UTXOs (default: false) |
No output schema declared.
No examples provided.
get_collection_info ~28
Get information about an NFT collection.
| Name | Type | Req | Description |
|---|---|---|---|
| contractId | string | yes | NFT collection contract ID |
No output schema declared.
No examples provided.
get_contract_events ~54
Get events emitted by a smart contract.
| Name | Type | Req | Description |
|---|---|---|---|
| contractId | string | yes | Contract ID in format: address.contract-name |
| limit | number | – | Maximum number of results |
| offset | number | – | Offset for pagination |
No output schema declared.
No examples provided.
get_contract_info ~35
Get information about a smart contract including its ABI.
| Name | Type | Req | Description |
|---|---|---|---|
| contractId | string | yes | Contract ID in format: address.contract-name |
No output schema declared.
No examples provided.
get_identity ~45
Get agent identity information from ERC-8004 identity registry. Returns owner address, URI, and wallet address if set.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | integer | yes | Agent ID to look up |
No output schema declared.
No examples provided.
get_inscription ~69
Get inscription content from a Bitcoin reveal transaction. Fetches the transaction from mempool.space and parses inscription data from the witness. Returns content type, body (as base64 and text if applicable), and metadata tags.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | Transaction ID of the reveal transaction containing the inscription |
No output schema declared.
No examples provided.
get_inscriptions_by_address ~67
Get all inscriptions owned by a Bitcoin address. Returns inscription IDs, content types, and metadata. Only available on mainnet (Hiro Ordinals API does not index testnet).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Bitcoin address to check. Uses wallet's Bitcoin address if not provided. |
No output schema declared.
No examples provided.
get_mempool_info ~52
Get pending transactions in the mempool.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results |
| offset | number | – | Offset for pagination |
| senderAddress | string | – | Filter by sender address |
No output schema declared.
No examples provided.
get_network_status ~19
Get the current status of the Stacks network.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_nft_history ~53
Get the transfer history of NFTs in a collection.
| Name | Type | Req | Description |
|---|---|---|---|
| contractId | string | yes | NFT collection contract ID |
| limit | number | – | Maximum number of results |
| offset | number | – | Offset for pagination |
No output schema declared.
No examples provided.
get_nft_holdings ~72
List all NFTs owned by an address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Wallet address to check. Uses configured wallet if not provided. |
| contractId | string | – | Filter by specific NFT collection contract |
| limit | number | – | Maximum number of results |
| offset | number | – | Offset for pagination |
No output schema declared.
No examples provided.
get_nft_metadata ~47
Get metadata for a specific NFT (SIP-016).
| Name | Type | Req | Description |
|---|---|---|---|
| contractId | string | yes | NFT collection contract ID |
| tokenId | number | yes | Token ID of the NFT |
No output schema declared.
No examples provided.
get_nft_owner ~44
Get the current owner of a specific NFT.
| Name | Type | Req | Description |
|---|---|---|---|
| contractId | string | yes | NFT collection contract ID |
| tokenId | number | yes | Token ID of the NFT |
No output schema declared.
No examples provided.
get_ordinal_utxos ~115
Get ordinal UTXOs (contain inscriptions - do not spend). Ordinal UTXOs contain Bitcoin inscriptions and should not be spent in regular transfers. These UTXOs are valuable as they carry ordinal data (text, images, etc.). Only available on mainnet (Hiro Ordinals API does not index testnet).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Bitcoin address to check. Uses wallet's Bitcoin address if not provided. |
| confirmedOnly | boolean | – | Only return confirmed UTXOs (default: false) |
No output schema declared.
No examples provided.
get_pox_info ~22
Get current Proof of Transfer (PoX) cycle information.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_reputation ~56
Get aggregated reputation summary for an agent from ERC-8004 reputation registry. Returns average rating as a raw WAD string (18 decimals) and total feedback count.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | integer | yes | Agent ID to get reputation for |
No output schema declared.
No examples provided.
get_stacking_status ~38
Check if an address is currently stacking STX.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Wallet address to check. Uses configured wallet if not provided. |
No output schema declared.
No examples provided.
get_stx_balance ~38
Get the STX balance for a wallet address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Wallet address to check. Uses configured wallet if not provided. |
No output schema declared.
No examples provided.
get_stx_fees ~42
Get current STX fee estimates for different priority levels. Returns low, medium, and high fee tiers in micro-STX, based on mempool analysis.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_taproot_address ~69
Get the wallet's Taproot (P2TR) address for receiving inscriptions. This address follows BIP86 derivation (m/86'/0'/0'/0/0) and uses bc1p... (mainnet) or tb1p... (testnet) prefix.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token_balance ~97
Get the balance of any SIP-010 token for a wallet address. Supports well-known tokens by symbol: sBTC, USDCx, ALEX, DIKO Or use the full contract ID: address.contract-name
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Wallet address to check. Uses configured wallet if not provided. |
| token | string | yes | Token symbol (e.g., 'USDCx', 'sBTC') or contract ID |
No output schema declared.
No examples provided.
get_token_holders ~56
Get the top holders of a SIP-010 token.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of holders to return |
| offset | number | – | Offset for pagination |
| token | string | yes | Token symbol or contract ID |
No output schema declared.
No examples provided.
get_token_info ~38
Get metadata for a SIP-010 token (name, symbol, decimals, supply).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Token symbol or contract ID |
No output schema declared.
No examples provided.
get_transaction_status ~38
Check the status of a Stacks transaction by its txid.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | The transaction ID (64 character hex string) |
No output schema declared.
No examples provided.
get_validation_status ~57
Get the status of a validation request using ERC-8004 validation registry. Returns validator, agent ID, response score (0-100), and response metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| requestHash | string | yes | Request hash as hex string (32 bytes) |
No output schema declared.
No examples provided.
get_validation_summary ~51
Get validation summary for an agent using ERC-8004 validation registry. Returns total validation count and average response score (0-100).
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | integer | yes | Agent ID to get validation summary for |
No output schema declared.
No examples provided.
get_wallet_info ~35
Get the agent's wallet address and status. If the agent doesn't have a wallet yet, provides guidance on how to assign one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
give_feedback ~193
Submit feedback for an agent using ERC-8004 reputation registry. Value is normalized to 18 decimals (WAD) internally for aggregation. Requires an unlocked wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | integer | yes | Agent ID to give feedback for |
| decimals | integer | yes | Decimals for the value (e.g., 0 for integer ratings) |
| endpoint | string | – | Optional endpoint URL |
| fee | string | – | Fee preset ("low", "medium", "high") or micro-STX amount. Optional. |
| feedbackHash | string | – | Optional feedback hash as hex string (32 bytes) |
| feedbackUri | string | – | Optional feedback URI |
| tag1 | string | – | Optional tag 1 (max 64 chars) |
| tag2 | string | – | Optional tag 2 (max 64 chars) |
| value | integer | yes | Feedback value (e.g., 5 for 5-star rating) |
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 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 20 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.