AIBTC MCP Server
Bitcoin-native MCP server: BTC/STX wallets, L1 reads and transfers, Stacks, sBTC, and x402 payments.
- Sato Score82
- ChainsBitcoin
AIBTC MCP Server is an open-source MCP server by AIBTC on Bitcoin, with last code activity on 2026-10-14 (Active). Latest release on 2026-10-14. Sato Score 82/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install AIBTC MCP Server →Last commit Oct 14, 2026 · Last release Oct 14, 2026 (mcp-server-v1.76.0) · ★ 10
Listed from github.com/aibtcdev/aibtc-mcp-server on 2026-07-13. Install: reproduced by Sato Hub on 2026-09-21. Evidence →
Next step
Watch AIBTC MCP Server
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on aibtcdev/aibtc-mcp-server before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
The AIBTC MCP server gives agents a Bitcoin-native toolset: wallet creation and mnemonic handling, Bitcoin L1 reads and transfers, Stacks L2 interactions, sBTC, NFTs, DeFi yield tools, and x402 payments. An agent builder plugs it in to run an agent that holds and moves BTC and Stacks assets without writing wallet plumbing. Key custody is local to the server host, so treat wallet tools with the usual key-handling care.
Sato Score
82/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 18/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v1.76.0 · as of 2026-10-15- Does it take your key?
- Reads a key
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from github.com/aibtcdev/aibtc-mcp-server on 2026-07-13. Install: reproduced by Sato Hub on 2026-09-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Bitcoin | self-reported | github.com/aibtcdev/aibtc-mcp-server | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | github.com/aibtcdev/aibtc-mcp-server | as of 2026-10-15 |
| Recent activity | last release 2026-10-14 · last commit 2026-10-14 | observed | github.com/aibtcdev/aibtc-mcp-server | 2026-10-15 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/aibtcdev/aibtc-mcp-server | 2026-09-21 |
| Website answers | answered (HTTP 200) | observed | github.com/aibtcdev/aibtc-mcp-server | 2026-10-15 |
| Daily check record | 90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Takes your key | reads private-key material | traced | satohub.ai | 2026-10-15 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-10-15 |
| Deploys as | npxconfidence 0.85 | self-reported | github.com/aibtcdev/aibtc-mcp-server | as of 2026-07-14 |
| Works with | Claude Code, Claude Desktop, Cursor, Windsurfconfidence 0.85 | self-reported | github.com/aibtcdev/aibtc-mcp-server | as of 2026-07-14 |
| Sato Score | 82/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Sep 21, 2026
Runtime: node
npx @aibtc/mcp-server@latest --install npx @aibtc/mcp-server@latest --install (auto-configures Claude Code; --desktop/--cursor/--windsurf/--gemini/--codex/--vscode for other clients)
You supply: agent wallet is auto-generated and AES-256-GCM encrypted locally on first use — this server moves real BTC/STX funds once connected
claude mcp add satohub-aibtc-mcp -- npx @aibtc/mcp-server@latest --install
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-09-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Bitcoin
- Agent types
- MCP Server, Wallet, Payments
- Open source
- Yes
- Deploys as
- npx
- Works with
- Claude Code, Claude Desktop, Cursor, Windsurf
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where AIBTC MCP Server fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Recent Activity
All news →Releases and posts from AIBTC MCP Server, pulled from its GitHub and X.
aibtc-mcp-server mcp-server: v1.76.0
1.76.0 (2026-10-14) Features x402: sign sponsored payments when the endpoint offers gas sponsorship ( #715 ) ( c7fb05b ) Bug Fixes inbox: sign self-paid inbox payments with the sbtc_transfer fee clamp ( #708 ) ( e48e30d ), closes #700 sbtc_transfer uses its own fee tier; At Stake legions join the legion group ( #707 ) ( b74f575 ), closes #704 #695 spend-limit: book spends before signing so the dai
aibtc-mcp-server mcp-server: v1.75.0
1.75.0 (2026-10-05) Features x402: write extra.payment_id as the payment memo, cut to 34 bytes ( #705 ) ( 0ff0d79 )
aibtc-mcp-server mcp-server: v1.74.0
1.74.0 (2026-10-02) Features inbox: gasless send when the inbox advertises a fee payer; meter sBTC ( #701 ) ( 279fff1 )
aibtc-mcp-server mcp-server: v1.73.1
1.73.1 (2026-10-01) Bug Fixes fee: cap plain sBTC transfer fees at 0.003 STX ( #697 ) ( 05f472d )
aibtc-mcp-server mcp-server: v1.73.0
1.73.0 (2026-09-28) Features spend-limit: meter every signed spend, default 50 STX / 50k sats ( #693 ) ( 4e7f021 )
aibtc-mcp-server mcp-server: v1.72.1
1.72.1 (2026-09-27) Bug Fixes config: stop loading .env from the working directory ( #691 ) ( 7ab2608 )
Listing History
Recorded changes to AIBTC MCP Server's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 14, 2026New release published
- Oct 5, 2026New release published
- Sep 21, 2026Verified: deploy spec
- Jul 20, 202613 releases trackedShowing the 2 most recent. Full release history is retained in the listing record.
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Auto-enriched: deployment options, supported integrations
- Jul 14, 2026Listed on Sato Hub
Compared with
Appears in
- x402-ready tools, scored →
- MCP servers with a verified install, scored →
- Npm-installable crypto agent tools, scored →
- Payment tools for agents, scored →
- What crypto MCP servers do with your keys: dated Sato Check readings →
- x402 endpoints checked for a payment-required answer →
- x402 facilitators on Base →
- x402: agent payments over HTTP →
- MCP: the tool interface for agents →
- Onchain agents on Bitcoin →
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about AIBTC MCP Server
- Is AIBTC MCP Server open source?
- Yes. AIBTC MCP Server is open source under the MIT license; the repository is https://github.com/aibtcdev/aibtc-mcp-server. Checked as of 2026-10-15.
- Which chains does AIBTC MCP Server support?
- AIBTC MCP Server lists support for Bitcoin as of 2026-10-15.
- Is AIBTC MCP Server still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-14 (last commit 2026-10-14, last release 2026-10-14), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run AIBTC MCP Server?
- node. Install: npx @aibtc/mcp-server@latest --install. Entry: npx @aibtc/mcp-server@latest --install (auto-configures Claude Code; --desktop/--cursor/--windsurf/--gemini/--codex/--vscode for other clients). Sato Hub reproduced this install in a container on 2026-09-21. It runs as an MCP server (npx @aibtc/mcp-server@latest --install).
- Is AIBTC MCP Server verified on Sato Hub?
- Sato Hub holds one earned check for AIBTC MCP Server: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 82 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "AIBTC MCP Server — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/aibtc-mcpData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.