Sato Hub
Wallet Infrastructure

BotWallet MCP

Non-custodial wallet MCP for AI agents to invoice, get paid, and spend on other agents/APIs, with human-set limits.

  • Sato Score72
  • ChainsSolana
EarlyUnverifiedActive · 16d ago

BotWallet MCP is a partly open-source wallet infrastructure on Solana, with last code activity on 2026-10-05 (Active). Latest release on 2026-10-05. Sato Score 72/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install BotWallet MCP →

Last commit Oct 5, 2026 · Last release Oct 5, 2026 (v0.4.1) · ★ 4

Listed from botwallet.co on 2026-07-19. Install: reproduced by Sato Hub on 2026-10-15. Evidence →

Next step

Watch BotWallet MCP

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/mcp
Run Sato Hub Preflight on botwallet-co/mcp before I use it.
Full setup: Claude Code, Cursor, others →

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

BotWallet gives an agent a Solana/USDC wallet it can use to send invoices, receive payment, and pay other agents or APIs, while keeping private keys on the human operator's machine and enforcing spending limits and approval gates. It uses FROST 2-of-2 threshold signing so no single party holds a complete key, and ships an open-source CLI and MCP server.

Sato Score

72/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
13/20
Interface verifiability
8/10
Docs & demo
6/10
Listing transparency & provenance
10/15
Independent verification
0/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

Sato Check

v0.4.1 · as of 2026-10-05
Does it take your key?
No key read found
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

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 botwallet.co on 2026-07-19. Install: reproduced by Sato Hub on 2026-10-15.

ClaimValueEvidenceSourceChecked
Chains supportedSolanaself-reporteddocs.botwallet.coas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedbotwallet.coas of 2026-10-21
Recent activitylast release 2026-10-05 · last commit 2026-10-05observedgithub.com/botwallet-co/mcp2026-10-21
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedgithub.com/botwallet-co/mcp2026-10-15
Website answersanswered (HTTP 200)observedbotwallet.co2026-10-21
Daily check record82 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-10-05
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-10-05
Works withClaude Desktop, Cursor, Windsurf, Cline, x402 protocolconfidence 0.80self-reportedgithub.com/botwallet-co/mcpas of 2026-08-06
Docshttps://docs.botwallet.coconfidence 0.90self-reportedgithub.com/botwallet-co/mcpas of 2026-08-06
Sato Score72/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-21

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 Oct 15, 2026

Runtime: Node.js (npm package)

npm install -g @botwallet/mcp
{"mcpServers":{"botwallet":{"command":"npx","args":["-y","@botwallet/mcp"]}}}

You supply: BOTWALLET_API_KEY (optional), BOTWALLET_WALLET (optional — selects wallet if multiple), BOTWALLET_BASE_URL (optional, default https://api.botwallet.co/v1), Note: FROST 2-of-2 key shares are stored locally in ~/.botwallet/seeds/ — custody risk if that directory is exposed

MCP invocation: npx -y @botwallet/mcp (stdio); `botwallet-mcp` after global install

Read from the project’s own docs as of 2026-10-15. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-23

91.2%of 91 checks since 2026-07-23 succeeded
Currently responding for 38 days
Succeeded
83
Failed
8
Their error
0
Unattributed
8

State changed on 2026-09-06 (responding → unreachable from our probe), 2026-09-14 (unreachable from our probe → responding).

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. 40 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-21, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
72
as snapshotted that day · 29/30 days

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
Solana
Agent types
Wallet infrastructure (MCP server)
Open source
Partial
Works with
Claude Desktop, Cursor, Windsurf, Cline, x402 protocol
Last checked
2026-10-21

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.

#mcp#wallet#agent-payments#threshold-signing#usdc

Where BotWallet MCP fits

Related concepts: How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from BotWallet MCP, pulled from its GitHub and X.

Listing History

Recorded changes to BotWallet MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Oct 16, 2026
    Sato Score tier: Medium → High
    Score 64 → 72.
  2. Oct 15, 2026
    Verified: deploy spec
  3. Oct 5, 2026
    Active again — shipped after a quiet spell
  4. Aug 6, 2026
    Auto-enriched: docs url, supported integrations
  5. Aug 6, 2026
    Sato Score tier: Low → Medium
    Score 39 → 49.
  6. Jul 24, 2026
    Sato Hub began tracking this listing
  7. Jul 19, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about BotWallet MCP

Is BotWallet MCP open source?
Partly. Some of BotWallet MCP is published as source (https://github.com/botwallet-co/mcp) and some is not. Checked as of 2026-10-21.
Which chains does BotWallet MCP support?
BotWallet MCP lists support for Solana as of 2026-10-21.
Is BotWallet MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-10-05 (last commit 2026-10-05, last release 2026-10-05), 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 BotWallet MCP?
Node.js (npm package). Install: npm install -g @botwallet/mcp. Entry: {"mcpServers":{"botwallet":{"command":"npx","args":["-y","@botwallet/mcp"]}}}. Sato Hub reproduced this install in a container on 2026-10-15. It runs as an MCP server (npx -y @botwallet/mcp (stdio); `botwallet-mcp` after global install).
Is BotWallet MCP verified on Sato Hub?
Sato Hub holds one earned check for BotWallet MCP: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 72 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "BotWallet MCP — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/botwallet-mcp

Data last refreshed 2026-10-21; 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.