Sato Hub
Wallet Infrastructure

Openfort

Wallet infrastructure with agentic backend wallets bound by signing policies, a Node SDK, a CLI, and MCP servers for its docs and CLI.

  • ChainsMultichain
ActiveUnverified

No code activity tracked

Listed from openfort.io on 2026-10-08. Install: not attempted — no install path on record. Not checked by Sato Hub yet: every row below is as listed. 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/mcp
Run Sato Hub Preflight on openfort-xyz/openfort-node before I use it.
Full setup: Claude Code, Cursor, others →

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.

Evidence — listed vs checked · what the words mean

Listed from openfort.io on 2026-10-08. Install: not attempted — no install path on record. Not checked by Sato Hub yet: every row below is as listed.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reportedopenfort.ioas of 2026-10-08
Verification statusUnverified — not independently reviewedself-reportedopenfort.ioas of 2026-10-08

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.

Details

Chains
Multichain
Agent types
Wallet, Agent Wallet
Open source
Partial
Deploys as
npm, cli
Last checked
2026-10-08

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.

#agent-wallet#agentic-wallet#signing-policies#backend-wallet#mpp#cli#mcp#sdk
See something inaccurate or outdated?Submit a correction →

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

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-10-08.
Which chains does Openfort support?
Openfort lists support for Multichain as of 2026-10-08.
Is Openfort still maintained?
Sato Hub tracks no commit or release for Openfort; it cannot say whether it is maintained.
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". Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Openfort — Sato Hub." Sato Hub, updated 2026-10-08, accessed 2026-10-08. https://satohub.ai/resources/openfort

Data last refreshed 2026-10-08; 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.