RARE Protocol
CLI toolkit for deploying NFT collections, minting, and running SuperRare-integrated auctions.
- Sato Score75
- ChainsEthereum, Base
RARE Protocol is an open-source developer tool on Ethereum and Base, with last code activity on 2026-10-20 (Active). Latest release on 2026-07-08. Sato Score 75/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 RARE Protocol →Last commit Oct 20, 2026 · Last release Jul 8, 2026
Listed from rare.xyz on 2026-07-19. Install: reproduced by Sato Hub on 2026-10-19. Evidence →
Next step
Watch RARE Protocol
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 superrare/rare-cli 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
RARE Protocol is a command-line toolkit for deploying ERC-721 collections, minting NFTs with IPFS media uploads, and creating/bidding/settling auctions from the terminal, built to be usable by both humans and agents. It ships an open-source npm package and deployed contracts (SovereignBatchMintFactory, SovereignBatchMint, SuperRareBazaar) on Ethereum mainnet, Base, and their testnets.
Sato Score
75/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 16/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 7/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v2.0.0 · as of 2026-09-29- Does it take your key?
- Asks for 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 rare.xyz on 2026-07-19. Install: reproduced by Sato Hub on 2026-10-19.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum, Base | self-reported | rare.xyz | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | rare.xyz | as of 2026-10-21 |
| Recent activity | last release 2026-07-08 · last commit 2026-10-20 | observed | github.com/superrare/rare-cli | 2026-10-21 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | raw.githubusercontent.com | 2026-10-19 |
| Website answers | answered (HTTP 200) | observed | rare.xyz | 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 | asks for a private key or seed phrase | declared | satohub.ai | as of 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 | 75/100 (High)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 Oct 19, 2026
Runtime: Node.js >=22 (global npm package)
npm install -g @rareprotocol/rare-cli rare (CLI); SDK imports @rareprotocol/rare-cli/client, /contracts, /utils; MCP: rare mcp serve
You supply: PRIVATE_KEY — wallet private key for SDK client usage, stored in plaintext at ~/.rare/config.json per the docs' own warning; high-risk if exposed (docs recommend --private-key-ref via 1Password instead), RPC_URL — RPC endpoint for SDK client usage, RARE_API_BASE_URL — optional, defaults to https://api.superrare.com
MCP invocation: rare mcp serve (stdio; optional --allow-writes flag)
Read from the project’s own docs as of 2026-10-19. 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
- Agent types
- CLI / SDK
- 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.
Listing History
Recorded changes to RARE Protocol's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 20, 2026Sato Score tier: Medium → HighScore 67 → 75.
- Oct 19, 2026Verified: deploy spec
- Sep 26, 2026Edited: entity class, resource type
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 19, 2026Edited: github url
- 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.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Trust Wallet Agent Kit (TWAK)
ActiveNon-custodial toolkit from Trust Wallet (MCP server, CLI, and SDK) that lets AI agents read and transact across 25+ chains within user-defined rules.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about RARE Protocol
- Is RARE Protocol open source?
- Yes. RARE Protocol is open source under the MIT license; the repository is https://github.com/superrare/rare-cli. Checked as of 2026-10-21.
- Which chains does RARE Protocol support?
- RARE Protocol lists support for Ethereum, Base as of 2026-10-21.
- Is RARE Protocol still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-20 (last commit 2026-10-20, last release 2026-07-08), 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 RARE Protocol?
- Node.js >=22 (global npm package). Install: npm install -g @rareprotocol/rare-cli. Entry: rare (CLI); SDK imports @rareprotocol/rare-cli/client, /contracts, /utils; MCP: rare mcp serve. Sato Hub reproduced this install in a container on 2026-10-19. It runs as an MCP server (rare mcp serve (stdio; optional --allow-writes flag)).
- Is RARE Protocol verified on Sato Hub?
- Sato Hub holds one earned check for RARE Protocol: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 75 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. "RARE Protocol — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/rare-protocolData 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.