Purple Flea Wallet
Non-custodial HD wallet MCP server for AI agents with cross-chain swaps via the Wagyu aggregator.
- Sato Score42
- ChainsMultichain
Purple Flea Wallet is an open-source wallet infrastructure, with last code activity on 2026-02-26 (Quiet). Sato Score 42/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 Purple Flea Wallet →Last commit Feb 26, 2026
Listed from purpleflea.com on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-14. Evidence →
Next step
Watch Purple Flea Wallet
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 purple-flea/wallet-mcp 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
Purple Flea Wallet is an MCP server and REST API that generates BIP-39 HD wallets for an AI agent across multiple chains (Ethereum, Base, Solana, Bitcoin, Tron, Monero, and others) from one mnemonic, and exposes balance checks, sending, and cross-chain swaps routed through the Wagyu aggregator. An agent builder uses it to give an agent a self-custodied wallet and swap execution without a third-party custodian.
Sato Score
42/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 5/35
- Code transparency
- 16/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 7/15
- Independent verification
- 0/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v1.0.2 · as of 2026-09-29- Does it take your key?
- No key read found
- 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 purpleflea.com on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-14.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | wallet.purpleflea.com | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | purpleflea.com | as of 2026-10-21 |
| Recent activity | last commit 2026-02-26 | observed | github.com/purple-flea/wallet-mcp | 2026-10-21 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/purple-flea/wallet-mcp | 2026-09-14 |
| Website answers | did not answer our check | observed | purpleflea.com | 2026-10-21 |
| Daily check record | 0 of 50 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-09-29 |
| 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-09-29 |
| Sato Score | 42/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-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 Sep 14, 2026
Runtime: Node.js (npm/npx package)
npx -y @purpleflea/wallet-mcp
{"mcpServers": {"purple-flea-wallet": {"command": "npx", "args": ["-y", "@purpleflea/wallet-mcp"], "env": {"WALLET_API_URL": "https://wallet.purpleflea.com"}}}}You supply: WALLET_API_URL — optional, defaults to https://wallet.purpleflea.com, No local private-key env var documented in the README; the connected wallet API states mnemonics/private keys are agent-managed and never stored server-side — vendor claim, not independently verified
claude mcp add satohub-purple-flea-wallet -- npx -y @purpleflea/wallet-mcp
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-14. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 30
- Failed
- 61
- Their error
- 0
- Unattributed
- 61
State changed on 2026-08-22 (responding → unclear), 2026-09-01 (unclear → unreachable from our probe).
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. The rate above leaves those checks out; the counts include them.
Last 30 days — to 2026-10-21, 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
- Multichain
- Agent types
- MCP server
- Open source
- Yes
- 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.
Where Purple Flea Wallet fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to Purple Flea Wallet's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 15, 2026Sato Score tier: Low → MediumScore 34 → 42.
- Sep 14, 2026Verified: deploy spec
- Aug 26, 2026Sato Score tier: Medium → LowScore 42 → 34.
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
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 Purple Flea Wallet
- Is Purple Flea Wallet open source?
- Yes. Purple Flea Wallet is open source under the MIT license; the repository is https://github.com/purple-flea/wallet-mcp. Checked as of 2026-10-21.
- Which chains does Purple Flea Wallet support?
- Purple Flea Wallet lists support for Multichain as of 2026-10-21.
- Is Purple Flea Wallet still maintained?
- The most recent code activity Sato Hub observed was on 2026-02-26 (last commit 2026-02-26), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Purple Flea Wallet?
- Node.js (npm/npx package). Install: npx -y @purpleflea/wallet-mcp. Entry: {"mcpServers": {"purple-flea-wallet": {"command": "npx", "args": ["-y", "@purpleflea/wallet-mcp"], "env": {"WALLET_API_URL": "https://wallet.purpleflea.com"}}}}. Sato Hub reproduced this install in a container on 2026-09-14. It runs as an MCP server (npx -y @purpleflea/wallet-mcp (stdio, via Claude Desktop config)).
- Is Purple Flea Wallet verified on Sato Hub?
- Sato Hub holds one earned check for Purple Flea Wallet: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 42 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. "Purple Flea Wallet — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/purple-flea-walletData 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.