The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the FibX listing page.
A command-line tool and MCP server for DeFi operations on Base, HyperEVM, and Monad, powered by Fibrous aggregation. Sign with your own wallet over WalletConnect, with a Privy server wallet, or with an imported key — every path bounded by a signing policy that lives on your machine.
open_fibx shows the wallet, balances, signing policy and a swap form with the Fibrous route inline — the model opens it, and you press Simulate and Swap--simulate previews write operations without broadcasting; gas estimates are included where available--json flag for scripting and pipelinesnpx fibx runs near-instantly| Chain | Native Token | Aave V3 |
|---|---|---|
| Base | ETH | ✅ |
| HyperEVM | HYPE | — |
| Monad | MON | — |
Run directly with npx (no install needed):
Or install globally:
Try FibX instantly — no sign-up, no wallet, no keys:
Option A — Email Login (Privy Server Wallet, no keys to manage):
Option B — Import Private Key (use an existing wallet):
That's it. Three steps from zero to first swap.
Run fibx auth setup and it will ask. The three paths differ on one thing:
| Path | Key held by | Runs while you are away | Bounded by |
|---|---|---|---|
auth connect | your own wallet | no | you, on your phone |
auth login | Privy | yes | Privy's signing policy |
auth import | this machine | yes | the local policy you set |
Keeping your own wallet and having FibX act unattended needs ERC-7715, which
wallets do not yet expose over WalletConnect. fibx auth setup explains the
closest options.
Security: When using
auth import, your private key is encrypted at rest with AES-256-GCM. The encryption key is auto-generated per machine and stored in the OS config directory (e.g.~/.config/fibx-nodejs/encryption-keyon Linux). You can also set theFIBX_SESSION_SECRETenvironment variable for CI/Docker environments.
Pairs FibX with a wallet you already have — MetaMask, Rabby, Rainbow, Phantom — over WalletConnect. A QR code appears in the terminal; scan it with your phone. Every transaction is then approved in your wallet, so the keys never leave it.
The chain you trade on must already be in your wallet, and it is approved when
you pair. If you try to sign on a chain the session does not carry, FibX stops
before contacting the wallet and names the chain: add it in your wallet, then run
npx fibx auth connect again so the new chain is included.
With --json, output is NDJSON — one JSON document per line, not one document
for the whole run: the pairing URI prints first as {"uri":"wc:..."} so a
script can act on it while it waits, then the result prints as its own compact
JSON line once the wallet approves.
npx fibx auth logout ends the connection on both sides: it tells your wallet to
drop the session, so FibX stops appearing in its connected-apps list, and removes
the pairing keys from disk along with the session.
A shared WalletConnect project id ships in the published bundle, so this works
with no setup. It is public by necessity — a CLI has no origin to allowlist — so
its only real exposure is quota consumed by third parties. If pairing starts
failing on quota, create a free project at
cloud.reown.com and set FIBX_WC_PROJECT_ID to your
own id.
auth login (email OTP) and auth import (private key) are unchanged and remain
available.
fibx policy bounds what FibX is allowed to sign, on top of whichever path
from the table above holds the key — a client-side cap evaluated before every
local-key, Privy, or WalletConnect transaction:
A local policy guarding a local key is advisory: anything that can read the key can edit the policy, so this is worth nothing against malware. What it does bound is the agent — a model that misbehaves, or a prompt injection telling it to.
Know what each rule bounds, because they are not the same:
maxValue caps the native value of a single transaction — ETH on Base,
HYPE on HyperEVM, MON on Monad. It does not bound tokens. An ERC-20 transfer
reaches the policy as a call to the token's contract carrying value: 0, so
the amount is invisible to it: base.maxValue 0.05 places no limit on
fibx send 50000 USDC 0xsomewhere, on the token side of a trade, or on an
Aave borrow. A token-value cap needs decimals and a token registry, and is
not in this release.allowedDestinations is the rule that bounds tokens, by bounding where
anything may go. It is the one to set if the worry is an agent moving your
holdings somewhere. Note that allowlisting a token's contract so a trade can
approve it also permits transfers of that token.allowedChains and expiry do exactly what they say. A lapsed or
unparseable policy refuses everything rather than permitting it.| Option | Description | Default |
|---|---|---|
-c, --chain <name> | Target chain (base, hyperevm, monad) | base |
--json | Output results as JSON | false |
Consolidated cross-chain portfolio view with USD valuations:
Shows all token holdings across Base, HyperEVM, and Monad with USD values. Includes DeFi positions (Aave V3 collateral/debt) and total portfolio net worth. Token prices are sourced live from Fibrous.
Get swap prices without authentication:
No wallet or authentication required. Use
quoteto explore prices, thentradeto execute.
Options: --slippage <n> (default: 0.5%), --approve-max, --simulate, --json
Note: The
tradecommand automatically detects Wrap (Native -> Wrapped) and Unwrap (Wrapped -> Native) operations and executes them directly via contract calls, bypassing aggregator routing to save gas.
Note:
supply,repay, andwithdrawsupport automatic ETH <-> WETH wrapping/unwrapping on Base.
Set custom RPC URLs to avoid rate limits on public endpoints:
Hot-reload: Config changes are picked up automatically — no need to restart the CLI or MCP server.
fibx includes a built-in MCP server for AI editors like Cursor, Claude Desktop, and Antigravity. See MCP.md for setup and available tools.
The MCP server exposes 19 tools: the FibX app (open_fibx, list_tokens), read-only queries, three transactional tools, and session and policy management. All write operations support a simulate=true preview that does not broadcast; gas estimates are returned only where available.
In a host that renders MCP Apps UI — Claude Desktop today — open_fibx is the entry point: ask about your wallet, a balance, a price or a swap and the whole app opens inline, pre-filled from the conversation. It executes nothing on its own; Simulate and Swap are buttons you press. In a text-only host the same call returns a JSON snapshot the model can summarise, and the headless tools do the rest.
For prompt-based agent integration (Claude Code, Cursor, etc.), see the fibx-skills repository.
Letting an AI agent operate a wallet requires controls outside the model. fibx combines signing-layer policies, server-side validation, client hints, and explicit previews. These controls reduce risk, but the server credentials, MCP client configuration, and deployment policy remain part of the trust boundary:
| Layer | What it does |
|---|---|
| Privy signing policy | The default policy allowlists configured chains, caps each transaction's native-token value, and denies key export. Privy evaluates the policy at signing time; fibx-server credentials and any custom policy remain critical trust boundaries. |
| fibx-server schemas | /sign/* accepts only the exact transaction shape the CLI produces — unknown fields, contract creation, and unserved chains are rejected before reaching Privy. |
| MCP tool annotations | Every transactional tool advertises destructiveHint: true; compatible clients may use that hint to request confirmation, depending on client behavior and configuration. |
| Simulation | --simulate previews write operations without broadcasting. Some paths also return a gas estimate; others return operation metadata only. |
| Local key storage | Imported private keys are encrypted at rest with AES-256-GCM using a per-machine key stored 0600 in the OS config directory. |
Wallet policy limits are configured per deployment — see the fibx-server wallet policy docs.
Note: policies are attached when a wallet is created. Wallets provisioned before policies were introduced keep signing without them until migrated.
This repository is the CLI and MCP server. Three sibling repositories complete the stack:
| Repository | Role |
|---|---|
| fibx (this repo) | CLI + stdio MCP server, shipped as a single dependency-free bundle |
| fibx-server | Hono backend that proxies Privy — holds the app secret so the CLI never does, and owns the wallet signing policy |
| fibx-skills | Prompt-based Agent Skills for Claude Code, Cursor, and other skill-aware agents |
| fibx-telegram-bot | Telegram bot that drives this CLI over MCP, with one process and separate config paths per active user |
The widget is built by Vite into a single HTML document and embedded in
dist/index.js by tsup, so the published package is still one file with no
runtime dependencies.
pnpm dev:ui:bridge runs the same host against the real MCP server; a Swap
there is a real swap.
finance.fibrous/fibx