Openfort
Wallet infrastructure with agentic backend wallets bound by signing policies, a Node SDK, a CLI, and MCP servers for its docs and CLI.
- Sato Score70
- ChainsMultichain
Openfort is a partly open-source wallet infrastructure by Openfort, with last code activity on 2026-11-18 (Active). Latest release on 2026-11-04. Sato Score 70/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-22. How the score works →
Check what an install would ask of your keys, before you run it →Last commit Nov 18, 2026 · Last release Nov 4, 2026 (v0.14.0) · ★ 10
Listed from openfort.io on 2026-10-08. Install: not attempted — no install path on record. Evidence →
Next step
Watch Openfort
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 openfort-xyz/openfort-node 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
Openfort's docs describe agentic wallets: a backend wallet for an AI agent, limited by signing policies, with recipes for paying HTTP services over MPP on Tempo and for delegating Hyperliquid trading to time-limited agent wallets. Server access is through the openfort-node SDK (npm @openfort/openfort-node), a CLI (@openfort/cli) for wallets, policies and transactions, and, per its AI docs page, MCP servers and a docs skill. A hosted service with open-source components; check which parts you can self-host before relying on them.
Sato Score
70/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 14/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from openfort.io on 2026-10-08. Install: not attempted — no install path on record.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | openfort.io | as of 2026-11-22 |
| Verification status | Unverified — not independently reviewed | self-reported | openfort.io | as of 2026-11-22 |
| Recent activity | last release 2026-11-04 · last commit 2026-11-18 | observed | github.com/openfort-xyz/openfort-node | 2026-11-22 |
| Website answers | answered (HTTP 200) | observed | openfort.io | 2026-11-22 |
| Daily check record | 44 of 44 daily checks since 2026-10-09 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-11-21 |
| Tags | agent-wallet, agentic-wallet, signing-policies, backend-wallet, mpp, cli, mcp, …confidence 0.80 | self-reported | github.com/openfort-xyz/openfort-node | as of 2026-10-11 |
| X account | https://x.com/openfort_hqconfidence 0.95 | self-reported | github.com/openfort-xyz/openfort-node | as of 2026-10-11 |
| Sato Score | 70/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-11-22 |
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.
Observed record — 45 daily checks since 2026-10-09
- Succeeded
- 45
- 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.
Last 30 days — to 2026-11-22, 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
- Wallet, Agent Wallet
- Open source
- Partial
- Deploys as
- npm, cli
- Last checked
- 2026-11-22
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 Openfort fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?
Recent Activity
All news →Releases and posts from Openfort, pulled from its GitHub and X.
openfort-node v0.14.0
Minor Changes #167 59ff34a Thanks @jamalavedra ! - Upgrade the zod dependency from 3.x to 4.6.7 to pick up the zod security fix, along with patched transitive dependencies (axios, follow-redirects, undici, fast-uri, esbuild). The exported policy schemas ( CreatePolicyBodySchema , RuleSchema and the criterion schemas) are now zod 4 schemas. Code that only calls .parse() / .safeParse() on them needs
openfort-node v0.13.3
Patch Changes #163 366e802 Thanks @jamalavedra ! - Fix requests failing on Cloudflare Workers with axios 1.20 ("Unsupported cache mode: default"), and bump @openfort/shield-js to ^0.2.2, which has the same fix.
openfort-node v0.13.2
Patch Changes #161 317e3cc Thanks @jamalavedra ! - Bump @openfort/shield-js to ^0.2.1 , which depends on axios 1.20.0. Earlier 0.1.x releases pinned axios 1.18.1, so installs of this SDK pulled a vulnerable axios even though the SDK's own axios range already allowed 1.20.0.
Listing History
Recorded changes to Openfort's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Nov 4, 2026New release published
- Oct 23, 2026New release published
- Oct 22, 20263 releases trackedShowing the 2 most recent. Full release history is retained in the listing record.
- Oct 11, 2026Auto-enriched: x url, has pricing, tags
- Oct 9, 2026Sato Hub began tracking this listing
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.
ElizaOS
ActiveOpen-source TypeScript framework for building crypto-native multi-agent systems.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Openfort
- Is Openfort open source?
- Partly. Some of Openfort is published as source (https://github.com/openfort-xyz/openfort-node) and some is not. Checked as of 2026-11-22.
- Which chains does Openfort support?
- Openfort lists support for Multichain as of 2026-11-22.
- Is Openfort still maintained?
- The most recent code activity Sato Hub observed was on 2026-11-18 (last commit 2026-11-18, last release 2026-11-04), 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 Openfort?
- Sato Hub has no deploy spec for Openfort; follow the project's own documentation at https://www.openfort.io/docs/products/server/workflows/agentic-wallets.
- Is Openfort verified on Sato Hub?
- No independent verification is on record for Openfort; its verification status is "Unverified" and its Sato Score is 70 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Openfort — Sato Hub." Sato Hub, updated 2026-11-22, accessed 2026-11-22. https://satohub.ai/resources/openfortData last refreshed 2026-11-22; 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.