@aibtc/mcp-server 1.26.0 → 1.28.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -3
- package/dist/tools/signing.tools.d.ts +3 -3
- package/dist/tools/signing.tools.d.ts.map +1 -1
- package/dist/tools/signing.tools.js +609 -132
- package/dist/tools/signing.tools.js.map +1 -1
- package/dist/transactions/inscription-builder.js +2 -2
- package/dist/transactions/inscription-builder.js.map +1 -1
- package/package.json +1 -1
- package/skill/SKILL.md +1 -1
- package/dist/wallet.d.ts +0 -114
- package/dist/wallet.d.ts.map +0 -1
- package/dist/wallet.js +0 -295
- package/dist/wallet.js.map +0 -1
package/README.md
CHANGED
|
@@ -10,7 +10,7 @@ Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg,
|
|
|
10
10
|
- **Bitcoin L1** - Check balances, send BTC, manage UTXOs via mempool.space
|
|
11
11
|
- **Agent's Own Wallet** - Agents get their own wallet to perform blockchain transactions
|
|
12
12
|
- **Secure Storage** - Wallets encrypted with AES-256-GCM and stored locally
|
|
13
|
-
- **
|
|
13
|
+
- **150+ Tools** - Bitcoin L1 + comprehensive Stacks L2 operations
|
|
14
14
|
- **sBTC Support** - Native Bitcoin on Stacks operations
|
|
15
15
|
- **Token Operations** - SIP-010 fungible token transfers and queries
|
|
16
16
|
- **NFT Support** - SIP-009 NFT holdings, transfers, and metadata
|
|
@@ -194,7 +194,7 @@ Claude: Done! Transaction broadcast: abc123...
|
|
|
194
194
|
|
|
195
195
|
Both addresses are derived from the same recovery phrase, making it easy to manage both Layer 1 (Bitcoin) and Layer 2 (Stacks) assets.
|
|
196
196
|
|
|
197
|
-
## Available Tools (
|
|
197
|
+
## Available Tools (150+ total)
|
|
198
198
|
|
|
199
199
|
### Wallet Management
|
|
200
200
|
| Tool | Description |
|
|
@@ -438,11 +438,13 @@ Or use any SIP-010 token by contract ID: `SP2X...::token-name`
|
|
|
438
438
|
|
|
439
439
|
| Environment Variable | Description | Default |
|
|
440
440
|
|---------------------|-------------|---------|
|
|
441
|
-
| `NETWORK` | `mainnet` or `testnet` | `mainnet` |
|
|
441
|
+
| `NETWORK` | `mainnet` or `testnet` | `mainnet` (installer) / `testnet` (if unset) |
|
|
442
442
|
| `API_URL` | Default x402 API base URL | `https://x402.biwas.xyz` |
|
|
443
443
|
| `CLIENT_MNEMONIC` | (Optional) Pre-configured mnemonic | - |
|
|
444
444
|
| `HIRO_API_KEY` | (Optional) Hiro API key for higher rate limits | - |
|
|
445
445
|
|
|
446
|
+
**Note on `NETWORK`:** The `--install` command writes `NETWORK=mainnet` by default (pass `--testnet` to use testnet). If you omit `NETWORK` from your config entirely, the runtime fallback is `testnet`. Most users should set this explicitly.
|
|
447
|
+
|
|
446
448
|
**Note:** `CLIENT_MNEMONIC` is optional. The recommended approach is to let Claude create its own wallet. `HIRO_API_KEY` is optional but recommended for production use — without it, you may hit Hiro's public rate limits (429 responses). Get a key at [platform.hiro.so](https://platform.hiro.so).
|
|
447
449
|
|
|
448
450
|
## Architecture
|
|
@@ -12,9 +12,9 @@
|
|
|
12
12
|
* - stacks_sign_message: Sign plain text messages with Stacks prefix
|
|
13
13
|
* - stacks_verify_message: Verify message signature and recover signer
|
|
14
14
|
*
|
|
15
|
-
* Bitcoin Message Signing (BIP-137):
|
|
16
|
-
* - btc_sign_message: Sign messages with Bitcoin private key (BIP-137
|
|
17
|
-
* - btc_verify_message: Verify Bitcoin message signatures
|
|
15
|
+
* Bitcoin Message Signing (BIP-137 / BIP-322):
|
|
16
|
+
* - btc_sign_message: Sign messages with Bitcoin private key (BIP-137 for legacy, BIP-322 for bc1q/bc1p)
|
|
17
|
+
* - btc_verify_message: Verify Bitcoin message signatures (auto-detects BIP-137 vs BIP-322)
|
|
18
18
|
*
|
|
19
19
|
* SIP-018 signatures can be verified both off-chain and on-chain by smart contracts.
|
|
20
20
|
* Stacks message signatures are SIWS-compatible for web authentication flows.
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"signing.tools.d.ts","sourceRoot":"","sources":["../../src/tools/signing.tools.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,yCAAyC,CAAC;
|
|
1
|
+
{"version":3,"file":"signing.tools.d.ts","sourceRoot":"","sources":["../../src/tools/signing.tools.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,yCAAyC,CAAC;AAytBpE,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,SAAS,GAAG,IAAI,CAw6B5D"}
|