Safe Wallet MCP (safer)
CLI and MCP client for querying Safe{Wallet} multisig transactions and owner/threshold details.
- Sato Score54
- ChainsEthereum, Base +2
Safe Wallet MCP (safer) is an open-source wallet infrastructure on Ethereum, Base, Polygon and other chains, with last code activity on 2025-03-28 (Dormant). Sato Score 54/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 Safe Wallet MCP (safer) →Last commit Mar 28, 2025 · ★ 3
Listed from github.com/safer-sh/safer on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-14. Evidence →
Next step
Watch Safe Wallet MCP (safer)
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 safer-sh/safer 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
safer is a minimal open-source client for Safe{Wallet} multisig contracts, offering both a CLI and an MCP interface that reads transaction and multisig details via the Safe Transaction API. An agent builder uses it to let an agent inspect pending transactions, owners, and thresholds without holding private keys in production; the project explicitly warns it is early-stage and not intended for managing significant funds.
Sato Score
54/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 17/20
- Interface verifiability
- 8/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 6/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v0.1.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 github.com/safer-sh/safer on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-14.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum, Base, Polygon, Arbitrum | self-reported | github.com/safer-sh/safer | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | github.com/safer-sh/safer | as of 2026-10-21 |
| Recent activity | last commit 2025-03-28 | observed | github.com/safer-sh/safer | 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/safer-sh/safer | 2026-09-14 |
| Website answers | answered (HTTP 200) | observed | github.com/safer-sh/safer | 2026-10-21 |
| Daily check record | 90 of 90 daily checks since 2026-07-23 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 | 54/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/yarn)
npm install -g @safer-sh/cli npx @safer-sh/mcp git clone https://github.com/safer-sh/safer.git cd safer yarn install yarn build safer config --set-rpc-url "https://your-rpc-endpoint" safer config --set-chain "sepolia" safer config --set-safe "0xYourSafeAddress" CLI: safer command (after global install); MCP: npx @safer-sh/mcp
You supply: RPC endpoint URL — required for blockchain interaction, set via safer config --set-rpc-url, Documented risk: README states private keys are stored in plaintext in local configuration files — explicit dev-only warning against managing large fund amounts; hardware wallet (Ledger) integration recommended for production use instead
claude mcp add satohub-safer-safe-wallet-mcp -- npx @safer-sh/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
- 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. 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
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
- Ethereum, Base, Polygon, Arbitrum
- Agent types
- CLI + MCP client
- Open source
- Yes
- Pricing
- Free
- 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 Safe Wallet MCP (safer) fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to Safe Wallet MCP (safer)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 14, 2026Verified: deploy spec
- 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 Safe Wallet MCP (safer)
- Is Safe Wallet MCP (safer) open source?
- Yes. Safe Wallet MCP (safer) is open source under the MIT license; the repository is https://github.com/safer-sh/safer. Checked as of 2026-10-21.
- Which chains does Safe Wallet MCP (safer) support?
- Safe Wallet MCP (safer) lists support for Ethereum, Base, Polygon, Arbitrum as of 2026-10-21.
- Is Safe Wallet MCP (safer) still maintained?
- The most recent code activity Sato Hub observed was on 2025-03-28 (last commit 2025-03-28), which Sato Hub labels "Dormant". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Safe Wallet MCP (safer)?
- Node.js (npm/yarn). Install: npm install -g @safer-sh/cli && npx @safer-sh/mcp && git clone https://github.com/safer-sh/safer.git && cd safer && yarn install && yarn build && safer config --set-rpc-url "https://your-rpc-endpoint" && safer config --set-chain "sepolia" && safer config --set-safe "0xYourSafeAddress". Entry: CLI: safer command (after global install); MCP: npx @safer-sh/mcp. Sato Hub reproduced this install in a container on 2026-09-14. It runs as an MCP server (npx @safer-sh/mcp (stdio, for Cursor/Claude/Windsurf)).
- Is Safe Wallet MCP (safer) verified on Sato Hub?
- Sato Hub holds one earned check for Safe Wallet MCP (safer): Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 54 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. "Safe Wallet MCP (safer) — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/safer-safe-wallet-mcpData 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.