Printr
Omnichain token launchpad with a dedicated MCP server and white-label API for agent-run token launches.
- Sato Score52
- ChainsBase, Solana +5
Printr is an open-source venue on Base, Solana, BNB Chain and other chains, with last code activity on 2026-07-17 (Quiet). Latest release on 2026-07-17. Sato Score 52/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
See what else you can build on Base →Last commit Jul 17, 2026 · Last release Jul 17, 2026 (sdk-v0.9.0) · ★ 4
Listed from printr.money on 2026-07-19. Install: reproduced by Sato Hub on 2026-07-21. Evidence →
Next step
Watch Printr
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 printrfi/printr-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
Printr is a token launchpad (memecoins and general tokens) live across Solana, Base, BNB Chain, Ethereum, Arbitrum, Avalanche, Mantle, and Monad, using a Proof-of-Belief fee model that routes custom fees to stakers instead of creators. It ships a dedicated MCP server plus plug-and-play token-creation, trading, and cross-chain APIs, aimed at agents that launch or manage tokens programmatically.
Sato Score
52/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 13/35
- Code transparency
- 17/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 8/15
- Independent verification
- 0/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v0.16.1 · 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 printr.money on 2026-07-19. Install: reproduced by Sato Hub on 2026-07-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Base, Solana, BNB Chain, Ethereum, Arbitrum, Avalanche, Monad | self-reported | printrfi.github.io | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | printr.money | as of 2026-10-21 |
| Recent activity | last release 2026-07-17 · last commit 2026-07-17 | observed | github.com/PrintrFi/printr-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 | raw.githubusercontent.com | 2026-07-21 |
| Website answers | did not answer our check | observed | printr.money | 2026-10-21 |
| Daily check record | 51 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 |
| Docs | https://printrfi.github.io/printr-mcp/confidence 0.90 | self-reported | github.com/PrintrFi/printr-mcp | as of 2026-08-01 |
| Sato Score | 52/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 Jul 21, 2026
Runtime: Node.js (via npx) or Bun (via bunx), MCP server
npx -y @printr/mcp@latest
{"mcpServers": {"printr": {"command": "npx", "args": ["-y", "@printr/mcp@latest"]}}}You supply: PRINTR_API_KEY — optional, uses public key by default, OPENROUTER_API_KEY — optional, enables image generation, EVM_WALLET_PRIVATE_KEY — optional, for autonomous EVM signing; wallet private key, high-risk if exposed, SVM_WALLET_PRIVATE_KEY — optional, for Solana signing; wallet private key, high-risk if exposed, PRINTR_DEPLOYMENT_PASSWORD — required for printr_fund_deployment_wallet
claude mcp add satohub-printr -- npx -y @printr/mcp@latest
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-07-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 51
- Failed
- 40
- Their error
- 0
- Unattributed
- 40
State changed on 2026-09-12 (responding → 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. 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
- Base, Solana, BNB Chain, Ethereum, Arbitrum, Avalanche, Monad
- Agent types
- MCP server / launchpad API
- 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.
Recent Activity
All news →Releases and posts from Printr, pulled from its GitHub and X.
Listing History
Recorded changes to Printr's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 26, 2026Edited: entity class, resource type
- Aug 17, 2026Sato Score tier: High → MediumScore 74 → 64.
- Aug 1, 2026Auto-enriched: docs url
- Aug 1, 2026Sato Score tier: Medium → HighScore 66 → 74.
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 21, 2026Verified: deploy spec
- 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 Printr
- Is Printr open source?
- Yes. Printr is open source under the Apache-2.0 license; the repository is https://github.com/PrintrFi/printr-mcp. Checked as of 2026-10-21.
- Which chains does Printr support?
- Printr lists support for Base, Solana, BNB Chain, Ethereum, Arbitrum, Avalanche, Monad as of 2026-10-21.
- Is Printr still maintained?
- The most recent code activity Sato Hub observed was on 2026-07-17 (last commit 2026-07-17, last release 2026-07-17), 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 Printr?
- Node.js (via npx) or Bun (via bunx), MCP server. Install: npx -y @printr/mcp@latest. Entry: {"mcpServers": {"printr": {"command": "npx", "args": ["-y", "@printr/mcp@latest"]}}}. Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx -y @printr/mcp@latest (stdio)).
- Is Printr verified on Sato Hub?
- Sato Hub holds one earned check for Printr: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 52 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. "Printr — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/printrData 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.